Sub-processors
Version 2026-08.3 — Effective August 14, 2026
This page lists the third parties that process personal data on Ploid's behalf in order to provide the Ploid platform (the "Services"), together with what each one does and where it does it.
It forms Annex 3 of our Data Processing Agreement and is referenced from Section 7.2 of our Privacy Policy. Each provider acts on Ploid's instructions under a written data-processing agreement, and Ploid remains responsible for its performance.
Notice of changes. Under Section 4.4 of the DPA, Ploid gives at least thirty (30) days' notice before a new sub-processor begins processing Customer Content, by updating this page and notifying customers in the application or by email. Customers may object on reasonable data-protection grounds within that period. Section 7 records every published state of this list, so that a change can be identified and objected to rather than merely noticed.
Reading a row. The Applies to column states which engagement a sub-processor is used for. It is load-bearing: a provider listed for one engagement is not thereby engaged for another, and two rows on this page are reachable only under a setting a workspace has to choose.
1. Infrastructure and platform
| Provider | What it does | Applies to | Location |
|---|---|---|---|
| Amazon Web Services (AWS EMEA SARL) | Hosts the Services end to end: application compute, managed PostgreSQL databases, object storage for datasets, workspaces and results, and the batch compute that executes analysis workflows. Also provides secrets storage and the audited administrative access path to production systems. | Platform and consulting | The AWS region this deployment runs in. Ploid's own multi-tenant service runs in the European Union — Ireland (eu-west-1); a deployment operated for a single customer runs in the region agreed with that customer. |
| Amazon Web Services — Amazon Bedrock | Serves the AI models used by the AI-assisted features. Under either regional data residency — EU or US — this is the only model inference provider that receives Customer Content or Conversations. | Platform | The region matching the workspace's data residency: European Union (EU inference endpoints) or United States (US inference endpoints). |
| Amazon Web Services — Simple Email Service | Delivers transactional email: address verification, password recovery, workspace invitations and account-approval notices. Receives the recipient's email address and the message. | Platform | European Union — Germany (eu-central-1) |
| Cloudflare, Inc. | Authoritative DNS for Ploid's domains. Cloudflare resolves domain names only; it does not proxy or terminate Ploid's application traffic, and therefore does not receive Customer Content, Conversations, or the content of requests. | Platform and consulting | Global anycast network (provider established in the United States) |
2. Payments
| Provider | What it does | Applies to | Location |
|---|---|---|---|
| Stripe Payments Europe, Limited | Processes payments and manages subscriptions for paid plans: hosted checkout, the customer billing portal, card storage, invoicing and dunning. Receives the workspace's billing name and email and the payment details you enter directly with Stripe. Ploid never receives or stores card numbers. | Platform — self-serve billing only | European Union — Ireland, with onward transfer to Stripe, Inc. (United States) under Standard Contractual Clauses |
Stripe processes data only on deployments where paid billing is switched on. On a deployment operating without paid plans, no data reaches Stripe at all.
3. AI model providers reachable only under global data residency
A workspace is created with a regional data residency, under which every model call is served from Amazon Bedrock in that region (Section 1 above). On Ploid's own multi-tenant service that region is the European Union; a deployment may instead offer US data residency, which keeps inference on Amazon Bedrock in the United States. Each deployment offers one regional setting, and the choices available are shown in workspace settings.
Either regional setting keeps the provider below unreachable. A workspace owner or administrator may switch the workspace to global data residency, which permits it to be used; until that switch is made, it receives no data.
| Provider | What it does | Applies to | Location |
|---|---|---|---|
| Anthropic PBC | Serves Anthropic models called directly rather than through Amazon Bedrock. Receives the prompts, Conversations and the portion of Customer Content included in a request. | Platform — workspaces set to global data residency only | United States, under Standard Contractual Clauses |
Ploid selects inference providers whose terms prohibit using data submitted through their API to train their own models, and configures the Services accordingly (Section 5.2 of the DPA).
4. Optional features
| Provider | What it does | Applies to | Location |
|---|---|---|---|
| Brave Software, Inc. | Performs web searches requested by the AI assistant, for the model families that do not carry out search on the provider's own side. Receives the search query the assistant formulates, which may reflect the content of your request. It does not receive your datasets or files. | Platform — agents with web search enabled | United States, under Standard Contractual Clauses |
Which of the two search paths applies follows from the model, not from the data-residency setting. Models served through Amazon Bedrock — that is, both regional residencies — do not search on the provider's side, so their searches go to Brave. Models called directly under global residency perform search themselves and reach Brave not at all. Data residency governs where a model call is processed; it does not keep a search query inside that region. A workspace that must not send queries to a US provider should turn web search off for its agents rather than rely on the residency setting.
5. Correspondence and engagement records
| Provider | What it does | Applies to | Location |
|---|---|---|---|
| Google Ireland Limited — Google Workspace | Ploid's corporate mail and document storage. Receives correspondence you send to a Ploid address — including support and legal mail — and, on a consulting engagement, the documents that make up the engagement record. It receives nothing from a workspace: no datasets, results, Conversations or files held in the Services. | Platform and consulting | European Union — Ireland |
6. What is not on this list, and why
Software Ploid operates itself. The Services include third-party software that Ploid runs inside its own infrastructure — for example the identity and session service, the SAML broker used for enterprise single sign-on, the cache, and the store that records AI-interaction traces for debugging. No third party receives data through these, so they are not sub-processors. Their licenses are listed in our Open-Source Software Notices.
Ploid's own monitoring. Operational logs, metrics and alerts are collected into infrastructure that Ploid itself operates within its own cloud organization. This is Ploid processing its own operational data as controller, not a disclosure to a third party.
Public scientific data sources. When you run an analysis, the code you run may fetch reference data from public scientific resources — sequence and annotation databases, ontologies, and literature sources. Those requests are outbound retrievals initiated by your analysis from a network-restricted environment limited to an explicit allow-list; the resources are not processing personal data on Ploid's behalf and are not sub-processors. The allow-listed sources are described in the Sandbox Software Inventory.
Certificate issuance. TLS certificates for Ploid's domains are issued by a public certificate authority, which receives an operational contact address and the domain names, and no customer data.
Sign in with Google. Where a deployment offers Google as a sign-in option, Google learns that an account is authenticating to Ploid and returns a verified email address and a stable account identifier. Google does that under its own terms as its own controller, not on Ploid's instructions, so it is not a sub-processor — and it receives no Customer Content, Conversations, or anything from a workspace. Registering with an email address and password does not involve Google at all. Section 7.5 of the Privacy Policy says the same from the user's side. Where an organization uses its own single sign-on, the identity provider is that organization's own and is not engaged by Ploid.
7. Change history
Every published state of this list, newest first. This section is what makes the notice and objection right in Section 4.4 of the DPA exercisable: a right to object to a change cannot be used against a page that only ever shows the current state.
| List version | Effective | Change | Sub-processor affected | Notice sent | Objection deadline |
|---|---|---|---|---|---|
| 2026-08.3 | August 14, 2026 | This change history begins, and the Applies to column is added so each row states which engagement it covers. Ploid's corporate mail and document storage is now stated in Section 5. That is a new disclosure, not a new engagement: the provider has held Ploid's correspondence throughout, and it receives nothing from a workspace. | Google Ireland Limited (Google Workspace) | On publication | 30 days from notice |
| 2026-08.2 | August 14, 2026 | US data residency added alongside EU and global. The Bedrock row's location becomes the region matching the workspace's residency rather than the European Union alone, and Section 3 was rewritten so that either regional setting keeps direct model providers unreachable. | Amazon Web Services — Amazon Bedrock | — | — |
| 2026-08 | August 3, 2026 | Initial publication. Amended in place on August 6, 2026 while this identifier was still current: the direct-Gemini inference path was retired from the model catalogue, so the Google row covering it ceased to describe anything and left the table, and Sign in with Google was written up as a non-sub-processor in what is now Section 6. The list changed identity while the version did not; this row puts that on the record. | Google (Gemini inference) | — | — |
Rows before 2026-08.3 carry no notice date because this history did not exist when they took effect. They are recorded so that the state of the list on a given date can still be established. From 2026-08.3 onward, a change is announced under Section 4.4 of the DPA and the objection period runs from that notice.
8. Contact
Questions about this list, or an objection to a change under Section 4.4 of the DPA:
Ploid AI Biotech, S.L. Avenida Diagonal, 612 - P. 1 PTA. 3, 08021 Barcelona, Spain Email: legal@ploid.ai