Privacy Policy

Artaa.Media is a remote creative studio providing video editing, web design and visual identity services. This policy covers the Artaa.Media website at artaa.media and the Artaa.Media Client Portal, which is the signed-in application where clients manage projects, meetings, sample requests, files and approvals.

It applies to three groups of people, and not everything below applies to everyone:

• Visitors who only read the public website. We collect nothing from you beyond what your browser sends to load the pages — unless you accept Marketing in the privacy preferences, in which case the Meta Pixel described in section 9 also runs on the public marketing pages.
• People who contact us — a project enquiry, a meeting booking or a sample request — whether or not they ever create an account.
• Clients with a Client Portal account.

Artaa.Media is responsible for the information described here. How to reach us is in section 15.

We collect the information you type into our forms, and nothing more from them. Depending on the form, that is:

• Project enquiry and meeting booking: your name, email address, company name if you give one, country, timezone, the service you are interested in, a description of your project, a preferred start date, a budget range if you choose one, and any reference link you provide.
• Sample request: your name, email address, company name if you give one, country, the service and the deliverable you want, a description of your project, a target deadline if you set one, and any reference or material links you provide.
• Meeting booking additionally records the time slot you choose and the timezone it was chosen in, so the meeting appears correctly for both of us.

Each of these forms records that you agreed to be contacted about your enquiry, and when. We keep that record because it is the basis on which we reply to you.

Optional fields are genuinely optional. A form will tell you which fields it needs.

If you create a Client Portal account, we store your display name, your email address, the organization name you choose, your preferred language, and the status of your account.

Some things are deliberately never stored as you gave them:

• Your password is never stored. What we store is a scrypt digest of it, which cannot be turned back into your password. We cannot tell you what your password is, and neither can anyone who obtains a copy of our database.
• Session tokens, email verification links and password reset links are never stored either. We store a keyed digest of each one, so a copy of the database taken without the key is not a set of usable credentials.
• Your IP address is never stored in readable form. Where we need to recognise repeated requests — to apply rate limits and to detect abuse — we store a keyed digest of the address instead of the address.

We keep a record of security-relevant events on your account: registration, email verification, successful and failed sign-ins, sign-outs, password resets, session revocations, connecting or disconnecting a sign-in provider, and profile or photo changes. These records hold the type of event and when it happened. They deliberately do not hold your password, your tokens, your email address or the contents of any change.

You can sign in to the Client Portal with Google instead of a password. If you do, the following is exactly what happens.

We use Google only to confirm who you are. We do not use Google to read, write or access anything else.

Specifically:

• The only permissions we request from Google are openid, email and profile. Nothing else is ever requested.
• We do not request access to Gmail, Google Drive, Google Calendar, Google Contacts, or any other Google service. We could not read your mail or your files even if we wanted to, because we never ask for the permission that would allow it.
• We do not keep Google access tokens, refresh tokens, or the raw identity token Google issues. There is no place in our database for any of them. The identity token is checked when it arrives and then discarded.
• If Google confirms that your email address is verified, that address can be used to create an Artaa.Media account, or to securely connect Google sign-in to an Artaa.Media account that already uses the same address. If Google does not confirm the address as verified, we will not create or connect anything.
• We store the identifier Google uses for your account, because that identifier is what keeps the connection between your Google sign-in and your Artaa.Media account working. We store it together with the email address Google reported, so that the Client Portal can show you which Google account is connected.
• Information from your Google profile never silently overwrites your Artaa.Media profile. Your Google name is used only to fill in the display name of a brand-new account at the moment it is created. It never changes the name on an account that already exists, and you can edit your display name yourself at any time.
• Your Google profile picture is not used as your Artaa.Media profile photo, and we do not copy it. Profile photos in the Client Portal are only ever ones you upload yourself.

Connecting Google is optional. An account created with a password does not need it, and connecting Google does not disable your password — you can continue to sign in either way.

Signing in with Google means Google receives a request from your browser, and Google will handle that under its own privacy policy. We have no control over and no visibility into what Google records about it.

Once you are working with us, the Client Portal holds the information needed to run the work:

• Projects: the title and brief you submit, the versions we deliver, and the approval or change-request decisions you record against them, including any note you write with a decision.
• Meetings: the meetings you have booked, their status, and any reschedule or cancellation.
• Sample requests: the brief you submitted and the material attached to it.
• Your organization: its name, your role in it, and which other records belong to it.

Records belong to your organization, and the server checks that on every single request rather than trusting anything your browser sends. Your browser never tells us which organization you belong to; we resolve that from your session.

If you sent us an enquiry or a sample request before you created an account, and it used the same email address, verifying your email address links those earlier records to your account so you can see them in one place. Records already linked to someone else are never re-linked.

Files you upload — project material, sample-request material, and your profile photo — are treated as confidential and are handled as follows.

• They are stored in private storage on our server, outside any location a web server can reach directly. There is no public URL for an uploaded file.
• Each stored file is given a random identifier as its name, with no file extension. Nothing about a stored file can be guessed from what you called it, and the name you uploaded is kept only as a label to show back to you.
• The type of every upload is decided by inspecting the actual content of the file, not by trusting its name. A file whose name and content disagree is refused.
• Uploads are size-limited, and profile photos are limited separately and much more tightly — they may be JPEG, PNG or WebP, up to 5 MiB.
• A file can only be downloaded through an authorized route, which confirms you are signed in and that the file belongs to your organization before any content is sent. Your profile photo is served only to you.

Replacing your profile photo stores the new one before removing the old one, so a failure part-way through cannot leave you with no photo. Removing it deletes the stored image and returns you to your initials.

We use the information described above to:

• reply to your enquiry and discuss your project;
• schedule, confirm, reschedule and cancel meetings;
• produce, deliver and revise the work you have asked for;
• operate your account, sign you in, and let you recover access;
• show you your own projects, files, meetings and approvals;
• keep the service working and secure — including rate limiting, preventing abuse of forms and uploads, and investigating suspicious activity;
• keep a record of what was agreed and delivered.

We do not sell your information, rent it or trade it, and we do not make automated decisions that produce legal or similarly significant effects about you. The information you give us in forms and in the Client Portal is never used for advertising.

The one advertising use is separate from all of the above and applies only if you accept Marketing in the privacy preferences: the Meta Pixel described in section 9 reports which public marketing pages were viewed so that we can measure our advertising, attribute it to campaigns and, where applicable, reach visitors to our public pages with advertising on Meta platforms. It receives nothing you typed and nothing from your account.

We do not send marketing email. The email we send is transactional: verifying your address, resetting your password, and confirming or updating a meeting you booked.

Information is held in a PostgreSQL database on a private server. The database is not reachable from the public internet. Traffic to the website and the Client Portal is encrypted in transit.

The measures described in sections 3 and 6 are the substance of our security posture: passwords stored only as scrypt digests, credentials stored only as keyed digests, IP addresses stored only as keyed digests, uploaded files kept outside the web root under unguessable names, and authorization checked against the database on every request rather than trusted from a token or a browser.

Sessions are re-checked continuously. If your account is suspended or your password is reset, existing sessions stop working immediately rather than when they happen to expire.

No system is perfectly secure, and we do not claim otherwise. If a breach affects your information, we will tell you.

We do not sell your information. The one advertising-related service we use is described below, and it runs only with your consent.

Three third-party services can receive information, and only for the purposes described:

• Google — only if you choose to sign in with Google. See section 4 for exactly what is and is not involved.
• Resend — our transactional email provider. It receives the email address and message content needed to deliver verification, password reset and booking messages.
• Meta (the Meta Pixel) — only if you accept Marketing in the privacy preferences, and only on the public marketing pages. What it receives is described in the next paragraphs.

The Meta Pixel is a small script provided by Meta Platforms. It is not loaded, and nothing is sent to Meta, until you accept Marketing in the privacy preferences shown on your first visit to a public marketing page; the default is off. Once accepted, it runs on the public marketing pages of artaa.media — the home page, About, Contact, FAQ, the service pages, the portfolio project pages and the legal pages — and reports to Meta that a page was viewed, which service or portfolio project was viewed (by its public identifier), and that you chose to open the project inquiry form (with the page language and which button you used). Meta also receives the technical information any request carries, such as your IP address, browser details and the address of the page, and may set the browser identifiers described in section 12.

We use this information for advertising measurement and campaign attribution — to understand whether our advertising on Meta platforms reaches people who are interested in our work — and, where applicable, to build advertising audiences on Meta from visitors to our public pages. Meta processes it under its own terms and privacy policy, which describe its retention; we do not claim to know or control Meta’s retention periods and do not state them here.

Nothing you type into a form is sent to Meta: not your name, email address, company, message or any other field. No information from the Client Portal, the Talent Portal or Operations is sent to Meta, and the pixel never runs on those pages, on the sign-in and sign-up pages, or on the booking and sample-request pages. We do not send Meta hashed or unhashed contact details of any kind (“advanced matching” is not used), and we do not send events from our server to Meta.

You can refuse Marketing at any time, and you can withdraw it later from the privacy preferences link in the footer of every public page. Withdrawal stops the pixel from sending anything further and removes the Meta identifiers from your browser where we are able to; it does not recall information already transmitted to Meta.

There is no other analytics service, no tag manager and no other third-party tracking script anywhere on this website, in the Client Portal or in the Talent Portal. Fonts are served from our own origin rather than from a third-party font service.

Our server and database are operated on infrastructure provided by a hosting provider, which necessarily stores the data on our behalf.

We may disclose information if we are legally required to, or where it is necessary to establish, exercise or defend a legal claim. If that ever happens we will tell you unless we are prohibited from doing so.

Account information is kept for as long as your account exists.

Enquiries and sample requests carry a recorded retention period: sample requests are recorded with a twelve-month retention class and an expiry date, and project enquiries with a standard twenty-four-month class.

We want to be precise about what that means today, because it would be easy to imply more. Those retention periods are recorded and reportable, but they are not yet enforced automatically — there is no scheduled job that deletes expired records. In practice, deletion happens when you ask us for it, or when we review records. We would rather tell you that than describe an automatic process that does not exist.

Records of completed work, and the security event log described in section 3, may be kept longer where there is a legitimate reason — for example a record of what was delivered and agreed.

You can ask us to do any of the following, and we will:

• tell you what information we hold about you;
• give you a copy of it;
• correct anything that is wrong — your display name and profile photo you can change yourself in the Client Portal at any time;
• delete your information and close your account;
• disconnect Google sign-in from your account, provided you have another way to sign in;
• withdraw Marketing consent — you can do this yourself at any time from the privacy preferences link in the footer of every public page, without writing to us;
• stop contacting you.

Depending on where you live, some of these may also be rights you hold under local law. We honour the requests above regardless of whether the law in your country requires it.

Write to accounts@artaa.media or use the contact page. We may need to confirm that the request comes from you before acting on it, particularly for deletion. We will respond within a reasonable time.

If we cannot fully act on a request — for example where we must keep a record of a completed engagement — we will tell you which part we cannot do and why.

Reading the public website sets no cookies of our own, and no analytics cookies. Your privacy preferences themselves are kept in your browser’s local storage under the key artaa.privacy.preferences.v1 — a record of your choice that is never sent to us or to anyone else, so remembering that you declined tracking does not itself require a tracking cookie.

If you accept Marketing, the Meta Pixel may set advertising-related identifiers in your browser: the first-party cookies _fbp (a browser identifier Meta uses to distinguish visitors) and, when you arrive from a Meta advertisement, _fbc (the click identifier from that advertisement). They are set by Meta’s script under Meta’s terms; withdrawing Marketing removes them where we are able to and stops the pixel setting them again. Without Marketing consent they are never set.

The Client Portal sets cookies that are strictly necessary to sign you in and keep you signed in safely:

• artaa_account_session — your session. It cannot be read by JavaScript, which is what stops a scripting flaw from stealing it.
• artaa_account_csrf — the value our own pages send back to prove a request came from you and not from another site.
• artaa_account_exchange — short-lived, set only while a password reset link is being exchanged.
• artaa_account_oauth — short-lived, set only while a Google sign-in is in progress, and used to confirm that the sign-in finishing is the same one your browser started.

All four are removed or expire on their own. Blocking them will prevent you from signing in, because they are the mechanism by which signing in works.

Sessions expire after a set period and are ended immediately when you sign out, when your password is reset, or when an account is suspended.

Artaa.Media is a remote studio and works with clients internationally. Our server, our database and our email provider are located outside some of the countries our clients are in, so information you give us will be transferred to and processed in a country other than your own.

By using the service or sending us an enquiry, you understand that this transfer is necessary for us to provide it.

This policy is published in English. English is the authoritative version.

We will update this policy when the service changes, and the effective date at the top will change with it. If a change materially affects how we handle your information, we will make that clear rather than quietly revising the text.

Continuing to use the service after a change means the updated policy applies to you.

For any question about this policy, or to make any of the requests in section 11, write to accounts@artaa.media, or use the contact page at artaa.media/en/contact.

We read every message sent to that address.