Subprocessors — who else handles your data, and where

A privacy policy that says data may be shared with "cloud hosting and email delivery providers" tells you nothing you could check. Naming the companies turns that sentence into a disclosure you can verify, take to a security reviewer, and object to.

It also keeps the studio honest. A list that has to be published is a list that has to be true.

A company is on this list when all three of these are true.

Companies you chose, and companies acting on their own account, are dealt with in section 6.

This page covers pixlnova.com — the studio site, the contact form, the guided assistant at /chat, and api.pixlnova.com behind them.

projects.pixlnova.com and freelancer.pixlnova.com are separate products with their own terms. Section 11 says what that means in practice rather than pretending this page governs them.

Each section below opens with one non-binding sentence in ordinary language. Those sentences are a reading aid. Where they and the clauses differ, the clauses are what applies.

A vendor that never stores your enquiry but carries it across its network still handles it. Cloudflare and Vercel are on this list for that reason, even though the enquiry comes to rest in the database rather than with them.

Where a company is incorporated is not where your data is. The location column describes the region the processing actually runs in, which is why the entry for the database names a region rather than a country of registration.

For three entries — Resend, Sentry and Upstash — the processing region is determined by the vendor's own infrastructure or by an account-level setting, and no single region has been verified for them. Their cells say so instead of naming a country.

That is deliberate. A confident-looking country name that turns out to be wrong is worse than an honest gap, and this is the kind of cell a reviewer checks. Each of the three is re-checked at every review of this page, and named here as soon as it is confirmed.

It does not cover how long data is kept, what the lawful basis is, or how to have data corrected or erased. Those are in the Privacy Policy. This page answers one question only: who else touches it.

Apart from the vendors above, and apart from disclosures required by law or made with your instruction, no third party receives personal data collected through pixlnova.com. On the PixlNova side, one person has access: the proprietor.

Two gaps are known and are recorded here rather than left for a reviewer to find.

Enquiries, CRM records and analytics events rest in a single managed PostgreSQL database in AWS ap-southeast-2, which is Sydney, Australia. There is no copy in India.

If you are in India and you submit the contact form, your personal data leaves the country at that moment. That is the plain fact, and it is repeated wherever it matters rather than mentioned once.

The transfer is treated as necessary for performing the service you asked for — answering an enquiry and running an engagement — and is made on the footing that the receiving infrastructure maintains a comparable level of protection to that required in India.

That is a position the studio asserts, not one a regulator has confirmed. It is one of the things a lawyer should check when this document leaves draft.

Data reaching PixlNova from the EU, the EEA or the UK leaves that territory: the store is in Australia and the studio operates from India. The transfer relies on the vendors' own published transfer terms and on the necessity of the processing for the service requested.

Whether an Article 27 representative has been appointed is recorded in the identity block below, along with the reasoning, so it is a decision on the record rather than a silence.

Moving the database to a different region, or adding a second region, counts as a material change and follows the notice in 8.1 like any new vendor would.

There is no Google Analytics tag, no advertising pixel and no third-party session-tracking script on this site. Analytics is first-party: the page writes its own cookies, posts events to api.pixlnova.com, and they are stored in the database named in section 3.

Those cookies are pxnv_anon_id and pxnv_session_id, scoped to .pixlnova.com so they are shared across the three properties, alongside a pxnv_first_touch entry in local storage. The Cookie Notice describes them in full. If your browser sends navigator.doNotTrack as "1", none of it runs.

No data collected here is sold, rented, traded, or passed to a data broker, an enrichment service or a lead marketplace. There is no arrangement under which another company markets to you because you contacted PixlNova.

The assistant at /chat is a guided interface over content already published on this site. It is not a language model, and what you type there is not sent to one. A brief submitted through it goes down the same contact pipeline as the form, to the same vendors.

Model providers appear in client projects where an AI feature is part of the scope. Those run in the client's own accounts under the client's own agreements, and are covered by section 6 rather than by this table.

A vendor missing from section 3 is not an oversight to be resolved by adding it quietly later. Adding one is a change, and changes follow section 8.

Client work is pushed to your repository from the first commit, and hosting, database and domains sit in accounts you own and pay for directly, at cost. The vendors behind those accounts are yours: your contracts, your regions, your subprocessor list.

PixlNova holds access you granted and that you can revoke. It does not hold the account. That is the deliberate consequence of the studio never putting your product on a studio machine.

Occasional specialist help — a video edit, a motion sequence — is brought in for work outside one engineer's range, and you are told before it happens rather than after.

If a collaborator would need access to personal data held by PixlNova, they become a subprocessor and are added to section 3 before that access is granted. None are listed today because none hold that access today.

Your bank, the card networks and the tax authorities act on their own account and under their own obligations, not on PixlNova's instructions. They are not subprocessors and are not listed as such.

Payment instrument details are collected by Razorpay or Stripe on their own pages. PixlNova never sees, receives or stores a card number, a UPI handle or bank credentials.

What is stored on the PixlNova side is the gateway's order and payment identifiers, the amount, the currency, the status, and the name and email needed to raise the invoice.

Clients in India are invoiced in INR through Razorpay, which processes in India. Clients outside India are invoiced in USD through Stripe. The currency rule is not a preference and is explained in the Payments, Cancellation and Refunds page.

The studio's tax registration status determines the title of the document you receive, and it is stated below rather than described here, so there is exactly one place it can be wrong.

The 30-day notice applies to a change that alters who handles your data or where. Specifically: a new vendor, a new category of data reaching an existing vendor, or a change in the country or region a vendor processes in.

It does not apply to a clarification that changes nothing operational — a vendor renaming itself, a corrected description, a typo. Those take effect on publication and still get a history line.

If a vendor fails, is withdrawn, or has to be replaced because of a security problem, the switch may happen before the notice period runs. In that case this page is updated and affected clients are emailed as soon as practicable, and no later than five working days after the change.

This exception covers keeping the service running and safe. It is not a route around the notice for an ordinary change.

Email hello@pixlnova.com and ask to be notified of subprocessor changes. There is no subscription widget; the request adds you to a list that is checked before any change is published. Clients with an active engagement are on it automatically.

Each review re-reads the running configuration — the environment, the payment and email integrations, the monitoring setup — and reconciles it against the table. The date of the last review is printed at the head of this page, so an abandoned document is visible rather than merely suspected.

A client with an active or proposed engagement, and any person whose personal data is held here. You do not need to be a paying client to raise it.

Email hello@pixlnova.com within the 30-day notice period. Name the vendor and say what the concern is — a region, a sector restriction, an internal policy. A reason makes an alternative findable; an objection without one usually cannot be answered with anything better than no.

The objection is handled on the same clock as any other grievance, which is published rather than left to discretion:

In the third case you may stop at the current milestone boundary under the engagement terms. You keep everything delivered and paid for, and nothing further is billed.

It is not a refund route for milestones already accepted. Settlement on cancellation follows the Payments, Cancellation and Refunds page, which applies the same way whatever the reason for stopping.

PixlNova relies on the data processing terms each vendor publishes and applies to all of its customers. No bespoke terms have been negotiated with any of them, and none would be available at this scale. Their terms are public and can be read alongside this page.

A client-provided DPA will be reviewed and, where it is workable, signed — the same way NDAs are handled. Review is done by the proprietor rather than by counsel, so allow a few days and expect edits where a clause assumes a company with departments.

PixlNova holds no SOC 2 report, no ISO 27001 certificate and no third-party penetration test report, and does not claim to. Security review and threat modelling are offered as work inside a project; the certificate at the end of an audit is not, and that exclusion is already stated on the pricing page.

There is also no uptime commitment on this website or on the studio's own systems, and no plan includes one.

A store for downloadable academic project packages. It has its own terms, licence and refund policy, and its own account, order and download records. Read those there; do not assume this page describes them.

A talent marketplace with escrow. Escrow, payouts and identity verification bring in obligations and providers that this page does not list, and marketplace rules that do not apply to a studio engagement. It publishes its own terms.

The analytics cookies are scoped to .pixlnova.com, so a visit to any of the three properties is recorded against the same anonymous identifier. Those events go to the vendors in section 3 and nowhere else.

If you would rather they did not, the Cookie Notice sets out how to switch it off, and a browser sending navigator.doNotTrack as "1" switches it off already.