Subprocessors and third parties.

Two kinds of third party receive data here, and they are listed separately because they are different in kind: the infrastructure that keeps the product running, and the provider your agent specifically chose to call.

Each of these receives only what its job requires, and none of them is a party you chose; they run the product for every customer, the same way.

Where these actually run is not uniform. Hetzner Online GmbH is a German company, and the production server that stores your account, run history, ledger and API keys is confirmed running in Hetzner's Nuremberg, Germany datacenter; that data lives in the EU, not the US, regardless of where you are. Brevo (formerly Sendinblue) is a French company. Stripe and Vercel are both US companies, and the services listed above (card processing and this site's public marketing pages) run on their US infrastructure.

We have not independently verified every region a provider might further mirror or process data in beyond what is confirmed above: a payment sub-region, a CDN edge, and so on. If you need that confirmed for a specific provider, ask using the contact below.

This is the row that is genuinely different from a normal SaaS subprocessor list, and it is structured to stay true as the catalog grows rather than to be rewritten on the day it does:

Naming a provider here is a separate fact from whether it is synthetic: most are — an invented vendor on a reserved test host that resolves to nothing — but two are not. Our first provider integration is a genuine vendor account, and we ran a small number of real, paid calls to it ourselves during integration and certification, the verification step every real provider passes through before it is ever opened to customer use. Echoco is not a vendor account at all: it is an internal fixture that calls a free public test endpoint solely to prove the pipeline end to end, and nothing about it is for sale. See the data sources and rights notice for what that processing can include. This page describes the mechanism honestly rather than waiting for it to matter: this is the row that applies to any real provider, whether or not it has yet been promoted to live, with no rewrite needed either way.

Unlike the infrastructure providers above, whose primary country of incorporation is confirmed above, country of operation for a tool provider varies: for the first-launch category of tools that source data from a third party rather than from you, that provider is incorporated in Delaware, United States, confirmed against its own public privacy policy, which also discloses separately appointed EU and UK data-protection representatives for that provider — context about that provider's own compliance posture, not a safeguard for our own use of it on your behalf. As noted above, we have not independently verified every region an infrastructure provider might further process data in beyond its primary country either, so this is about primary country of operation specifically, not about residency or processing more broadly. See the data sources and rights notice for the fuller version of this disclosure.

• We do not send a provider anything about you beyond what routing and billing that call requires.
• A provider only ever sees the input for calls made to it: never your workspace balance, your other runs, or any other provider's traffic.
• Fields that look like a credential or a secret are redacted from what we store about the call before it is written to your run history, and are never forwarded to a provider unless they are the actual parameter that call requires.

If we add, remove, or change what an infrastructure provider above receives, we will update this page. A subprocessor list that goes stale the day a vendor changes is worse than no list at all, and we treat it accordingly.

Questions about a specific provider or a specific call go to pixellabsweb3@gmail.com. See also the privacy policy, the terms of service, and the data sources and rights notice.