How we process your data
Registry updated: 2026-11-06
This page renders a declared registry generated from our code. Each purpose below is one row of that registry: the data it involves, why we do it, how long it is kept, who receives it, and the transfer position we declare. The registry is not proof of completeness: a storage census now probes the codebase for browser storage names and found none unregistered at its last run, but it cannot see HttpOnly cookies, vendor keys, orphan or retired names, or keys computed at write time. No probe can find a model call, a provider or a purpose that no row names.
What you are looking at is one record of what we do with your data and what you can do about it — not a certification, not a claim that it is complete, not a statement that we meet any legal standard, and not a substitute for the legal documents at /legal.
Where a retention period is written down but no code enforces it, the row says stated, not enforced. Where we have not decided a lawful basis, the row says so instead of naming one.
Impact assessment
Impact assessment. A data protection impact assessment for this surface was recorded on 2026-11-01. It records 15 risks, of which 1 remains High: R-03 is erasure, which cannot be closed from this repository. It is not a conformity assessment and no authority has reviewed it, and no sign-off has been obtained. Next review: 2027-05-01.
Recorded 2026-11-01 · review due 2027-05-01 · 15 risks recorded, 1 with a High residual · measured at 6253d04206
Not performed, and therefore not claimed: AI-system completeness; Storage completeness beyond the scanner's reach; Controller identity; Processor enumeration; Advice from a data protection officer; The views of data subjects; Counsel review of the lawful bases; Verification of residency and transfers.
The dated record is not published as a web page — this site does not serve repository documents — so the assessment exists in the repository and this section is rendered from the same single source the record's own tables are generated from.
Chat, answered by a cloud model
pa-chat-inference-cloud · version 1 · reviewed 2026-10-31 · Conditional
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Answering the messages you send in Chat with a cloud model, and keeping the conversation in your account.
| Why we do it | Performing our contract with you Answering a request you made is the service itself. |
|---|---|
| Data | Messages you send; Files and images you attach |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | AI model providers; Hosting and storage; DeepSeek; OpenRouter; Anthropic; OpenAI; Alibaba Cloud (DashScope) |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
| Gate | One path in this purpose runs only where DASHSCOPE_API_KEY is configured. |
Chat, answered by a model on your own machine
pa-chat-inference-local · version 1 · reviewed 2026-10-31 · Conditional
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Sending your message to the Ollama or OMM runtime you configured, when you pick a local model; the request passes through our server.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Messages you send |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | None outside Poly. |
| Transfers | None declared — no recipient outside Poly. |
| Gate | One path in this purpose runs only where OLLAMA_BASE_URL is configured. |
Keeping a reminder you asked for
pa-chat-followups · version 1 · reviewed 2026-11-02 · Live
No earlier version
This row has said this since it was written on 2026-11-02. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Saving the text of a follow-up you asked to be reminded about in your account, so your other signed-in devices show the same pending reminder. With the control off, a new reminder stays on the device that armed it and nothing about it is sent.
| Why we do it | Your consent The reminder still fires on this device when consent is withdrawn; only the account copy stops. |
|---|---|
| Data | Messages you send; Account identity |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | Hosting and storage |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Research retrieval
pa-research-retrieval · version 1 · reviewed 2026-10-31 · Conditional
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Searching the web and your sources for a research brief, then drafting it with a model; the configured search provider is queried for web results.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Research sessions and notes; Files and images you attach |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | AI model providers; Data sources; Hosting and storage; Perplexity; DeepSeek |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
| Gate | One path in this purpose runs only where PERPLEXITY_API_KEY is configured. |
Reading the files and images you attach
pa-document-extraction · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Reading text out of a document or image you attach, so Chat and the editors can use it.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Files and images you attach; Messages you send |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | AI model providers; OpenRouter; Z.AI |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Generating images and video
pa-media-generation · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Generating images and video from a prompt and any source media you provide, and keeping what you save in your library.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Media you generate; Files and images you attach |
| Kept for | Generated images you keep: you choose (7–90 days) — You choose 7, 30 or 90 days, or keep these images until you delete them. Enforced by code. |
| Who receives it | Media generation; AI model providers; Hosting and storage; Replicate |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Speech to text and text to speech
pa-speech · version 1 · reviewed 2026-10-31 · Conditional
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Turning your speech into text and text into speech; uploaded call and meeting recordings are transcribed by the provider we have configured.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Messages you send; Files and images you attach |
| Kept for | Transcript artifacts: 90 days — Transcript artifacts are pruned after 90 days and capped at 200 per person when written. Enforced by code. |
| Who receives it | AI model providers; Media generation; OpenAI; ElevenLabs; Z.AI; Deepgram |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
| Gate | One path in this purpose runs only where DEEPGRAM_API_KEY is configured. |
Agents and tools
pa-agents-tools · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Running an agent you start and the tools it calls, including a local run capture you opt into.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Messages you send; Files and images you attach |
| Kept for | Chat-agent run journal: 7 days — Run records older than 7 days are deleted by a server sweep. Enforced by code. |
| Who receives it | AI model providers; Hosting and storage; DeepSeek; Anthropic; OpenAI |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Showing your own records in one place
pa-hub-aggregate-view · version 1 · reviewed 2026-11-01 · Live
No earlier version
This row has said this since it was written on 2026-11-01. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Reading your own records from the sections that hold them — chat, research, office and studio — and showing them together on /user so you can find and understand what you have.
| Why we do it | Performing our contract with you A compatible use of records you already have: the hub reads what the sections hold, shows it to the same account, and stores nothing of its own. |
|---|---|
| Data | Account identity; Messages you send; Files and images you attach; Media you generate; Research sessions and notes; Office documents |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | Hosting and storage |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Remembered facts
pa-memory-recall · version 2 · reviewed 2026-11-01 · Live
Version 1 is not kept
Version 1 stopped being shown on 2026-11-01. We did not keep its text, so we cannot show what it said. Every version from 2 onward is kept.
No fingerprint was taken before this ticket, so the exact sentence is not something this product can show; a comment that paraphrases it, or a commit that still holds it, is evidence about the past — not the text, and not something this page can prove was what it said.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Keeping facts from the features you use — a saved conversation snapshot, a research run, an agent outcome, or a fact you ask us to remember — and returning them when they are relevant to a later request.
| Why we do it | Performing our contract with you A row is kept because a feature wrote it or a request asked for it to be kept; deleting a row is how you withdraw it. |
|---|---|
| Data | Remembered facts (memory rows) |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | AI model providers; Hosting and storage; DeepSeek; OpenRouter; Anthropic; OpenAI; Z.AI |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Psyche records
pa-psyche · version 2 · reviewed 2026-10-31 · Live
Version 1 is not kept
Version 1 stopped being shown on 2026-10-31. We did not keep its text, so we cannot show what it said. Every version from 2 onward is kept.
No fingerprint was taken before this ticket, so the exact sentence is not something this product can show; a comment that paraphrases it, or a commit that still holds it, is evidence about the past — not the text, and not something this page can prove was what it said.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Scoring assessments, keeping your journal and talking to a therapy companion; your records stay on your device unless you turn on sync.
| Why we do it | Your consent Sync is turned on by you, saved against your account, and withdrawable at any time; the control's copy and its reader are declared in lib/user/governance/consent-controls.ts. |
|---|---|
| Data | Psyche records (health, mood and journal) |
| Kept for | Browser storage: no limit — Browser stores that no scoped device family names stay until you clear site data; the identity purge clears only its own families. Stated, not enforced. |
| Who receives it | AI model providers; Hosting and storage; DeepSeek; OpenAI |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Finance records and wallet state
pa-finance-records · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Keeping the portfolios, ledgers and wallet vaults you use in Finance, and syncing trading-agent state between your devices when you sign in.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Finance records and wallets |
| Kept for | Browser storage: no limit — Browser stores that no scoped device family names stay until you clear site data; the identity purge clears only its own families. Stated, not enforced. |
| Who receives it | Hosting and storage; Data sources |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Office documents
pa-office-documents · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Saving the documents you write in Office to your account and this device, with a trash you can restore from.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Office documents |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | Hosting and storage |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Connected services and imports
pa-connectors-import · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Fetching what you ask for from a service you connected, and importing a file you choose, for the run you started.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Payloads from connected services; Files and images you attach |
| Kept for | Connected-service payloads: no period stated — Connected-service payloads are used for the run you start; no retention period is enforced in this codebase. Stated, not enforced. |
| Who receives it | Data sources; Operational infrastructure; Hosting and storage |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Keeping what you imported
pa-import-archive · version 2 · reviewed 2026-11-02 · Live
Earlier wording (1 version, kept)
Version 1 · shown until 2026-11-03
This is what this notice said until 2026-11-03. It is shown for context: it is not the wording of any decision on this device.
Holding the conversations and messages you imported from another service in this browser, so you can read them, see where each came from, and delete any import you choose.
| Why we do it | Performing our contract with you You started the import and choose what stays; deleting an import removes exactly the rows it created. |
|---|---|
| Data | Messages you send; Files and images you attach |
| Kept for | Browser storage: no limit — Browser stores that no scoped device family names stay until you clear site data; the identity purge clears only its own families. Stated, not enforced. |
| Who receives it | None outside Poly. |
| Transfers | None declared — no recipient outside Poly. |
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Holding the conversations, messages and other records you imported from another service in this browser, so you can read them, see where each came from, and delete any import you choose.
| Why we do it | Performing our contract with you You started the import and choose what stays; deleting an import removes exactly the rows it created. |
|---|---|
| Data | Messages you send; Files and images you attach |
| Kept for | Browser storage: no limit — Browser stores that no scoped device family names stay until you clear site data; the identity purge clears only its own families. Stated, not enforced. |
| Who receives it | None outside Poly. |
| Transfers | None declared — no recipient outside Poly. |
Accounts and signing in
pa-account-auth · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Creating your account, signing you in, and keeping your session on this device.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Account identity; Sign-in metadata |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | Hosting and storage; Operational infrastructure |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Usage counters and telemetry
pa-telemetry · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Counting how features are used — on this device and, for a few instruments, in batches sent to our servers — so we can decide what to build and keep the service running.
| Why we do it | Our legitimate interests Notice plus working opt-outs for engagement events and usage counters; billing metering is disclosed and always on, not toggled (OD-11). |
|---|---|
| Data | Usage counters and telemetry; Account identity |
| Kept for | Server-side telemetry: no period stated — Usage events are batched to our servers; no retention period is enforced in this codebase. Stated, not enforced. |
| Who receives it | Analytics; Hosting and storage |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Plans, credits and payments
pa-billing · version 2 · reviewed 2026-11-04 · Live
Earlier wording (1 version, kept)
Version 1 · shown until 2026-11-04
This is what this notice said until 2026-11-04. It is shown for context: it is not the wording of any decision on this device.
Taking payment for a plan or a credit top-up, and keeping the record of what you bought.
| Why we do it | Performing our contract with you Payment records are also kept where tax and accounting law requires them. |
|---|---|
| Data | Account identity; Finance records and wallets |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | Payments; Hosting and storage |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Taking payment for a plan or a credit top-up, and keeping the record of what you bought.
| Why we do it | Performing our contract with you Payment records are also kept where tax and accounting law requires them. |
|---|---|
| Data | Account identity; Finance records and wallets |
| Kept for | Financial and billing records: typically seven years — the published retention sentence applies (see the Privacy Policy). Stated, not enforced. |
| Who receives it | Payments; Hosting and storage |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Support and account email
pa-support-email · version 1 · reviewed 2026-10-31 · Live
No earlier version
This row has said this since it was written on 2026-10-31. We keep the text from now on, so a future change will be readable here.
A fingerprint shows that a text was not edited. It does not show what the text said, and it is not a legal record.
Sending you sign-in, billing and support email, and keeping the correspondence.
| Why we do it | Performing our contract with you |
|---|---|
| Data | Account identity |
| Kept for | Account data: while your account exists — Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. Stated, not enforced. |
| Who receives it | Operational infrastructure |
| Transfers | Declared by Poly as controller This is Poly's role in this purpose, not a transfer mechanism: whether one is documented for each recipient is stated in the residency statement. |
Residency and transfers
Statement updated: 2026-11-01
A declared statement of where each class of your data is stored and processed, and of what nobody has established: our own server locations are unmeasured from this repository, and no transfer mechanism is documented for any recipient named here.
0 of 12 classes have a complete answer; 9 have at least one evidenced cell and 3 have none. 0 of 18 recipients have a documented transfer mechanism. Those numbers are counted from the rows below, not typed into this sentence.
No authority has reviewed this statement, and it does not claim that any transfer rests on a documented instrument or that any recipient protects data to a particular standard. Where we do not know something, the row says what is missing and why it stays missing.
There is no per-person or per-organisation placement, no region to choose and no switch: the answer is the same for every account.
Account identity
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers hold the cached profile and tokens is unmeasured, and the hosting and operations categories that receive them record no location. |
Messages you send
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep the conversation is unmeasured, several of the providers that can receive it state no location we could read, and no transfer mechanism is documented with any of them. |
Files and images you attach
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep the extracted text is unmeasured, several of the providers that can receive it state no location, and no transfer mechanism is documented with any of them. |
Media you generate
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep a generated file is unmeasured, and Replicate states no location we could read. |
Research sessions and notes
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep the session is unmeasured, and Perplexity's policy could not be read, so it has stated no location we can repeat. |
Remembered facts (memory rows)
| On this device | not held on this device: this class lives on our servers |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | These rows live only on our servers, and where those servers run is unmeasured. |
Psyche records (health, mood and journal)
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep the rows sync sends them is unmeasured, and OpenAI states no location we could read. |
Finance records and wallets
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep these records is unmeasured, and the data-source category that receives them records no location. |
Office documents
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep a document is unmeasured, and the hosting category that receives it records no location. |
Payloads from connected services
| On this device | not held on this device: this class lives on our servers |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | These payloads live only on our servers, where they run is unmeasured, and the categories that receive them record no location. |
Usage counters and telemetry
| On this device | this device (your browser) |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | Where our servers keep the counters is unmeasured, and the analytics vendor records no storage location. |
Sign-in metadata
| On this device | not held on this device: this class lives on our servers |
|---|---|
| On our servers | we cannot establish this from code: no module in this repository records where our backend, its database, its object store, its queue or its backups run; our Privacy Policy states where we store data (§14) |
| Processed by |
|
| The gap | These rows live only on our servers, and where those servers run is unmeasured. |
Recipients outside Poly, and their transfer mechanisms
Every recipient below is one row. The mechanism column reads none documented for all 18 today: that is a measured absence, not a missing value.
Poly is run from the United States, and our service providers process data in other countries too, including the United States and the People's Republic of China: DeepSeek, our default chat model, says it stores data there, and Alibaba Cloud's DashScope, which some chat, research and agent features use where we have configured it, stores requests in its Beijing region. We have not yet put in place a documented transfer mechanism, such as Standard Contractual Clauses, with these providers. Ask legal@poly.inc for details.
We do not have counter-signed Standard Contractual Clauses in place with you, and we have not completed a transfer impact assessment. This is the largest gap in this document and it is stated here rather than buried: if you are exporting EEA or UK personal data and need a documented Chapter V transfer mechanism, we cannot yet give you one. Write to legal@poly.inc before you rely on Poly for that processing.
Both sentences above are rendered from the module the Privacy Policy and the DPA use; nothing on this page retypes or paraphrases them.
| Recipient | Where it says it processes | Transfer mechanism | Why |
|---|---|---|---|
| DeepSeek | the People's Republic of China, per its privacy policy | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| OpenRouter | the United States and other countries, per its privacy policy | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| Anthropic | the provider has not stated a location we could read | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| OpenAI | this provider's policy could not be read, so it has stated no location we can repeat | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| Z.AI | Singapore, per its privacy policy | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| ElevenLabs | the provider has not stated a location we could read | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| Replicate | the provider has not stated a location we could read | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| Alibaba Cloud (DashScope) | the People's Republic of China (its Beijing region), per its Model Studio documentation | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| Deepgram | the United States, per its privacy policy | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| Perplexity | this provider's policy could not be read, so it has stated no location we can repeat | none documented | No documented mechanism is recorded for this provider: Poly's transfer statement says none is in place, and no signed instrument is recorded in this repository. |
| AI model providers | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
| Media generation | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
| Payments | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
| Hosting and storage | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
| Operational infrastructure | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
| Analytics | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
| Data sources | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
| Messaging | no location is recorded for this category — it is named by category, not by vendor | none documented | No documented mechanism is recorded for this category: it is named by category, with no vendor contract or location recorded in this repository. |
The twelve dimensions we checked
Every dimension renders, including the ones with nothing to show. A dimension that is missing cannot be inferred from the rest, so an omission here would be a silent claim.
- Primary storage and replicas — gap: The backend database is reached through a URL this repository holds; no module anywhere records the region it runs in, and nothing records a replica.
- Backups and point-in-time recovery — gap: One published sentence describes a rolling cycle; it states no period and no place, and no code configures either.
- Object storage and CDN — gap: Our own media store is the browser's (OPFS and IndexedDB); no chat-repo code path names a bucket or a region, and the backend's sample environment's region default is a placeholder, not a measurement.
- Search and vector indexes — gap: The vector extension lives in the same database as everything else, so it inherits that database's unknown region.
- Queues and streams — gap: The rate-limit and cache store is configured by a URL and a token; the region is chosen in the vendor's console and is recorded nowhere here.
- Application, access and audit logs — gap: The DPA states that audit logging exists and names no location; the error buffer and the event ledger this repository owns are local-only.
- Metrics, traces, APM and error tracking — partial: A real negative: no third-party monitoring SDK is in the manifest, so no APM vendor receives anything. Where our own logs are shipped remains unknown.
- Support access (staff, tooling, attachments) — gap: Nothing in this repository describes staff tooling or the access it has.
- Break-glass access — gap: Nothing in this repository describes an emergency access path.
- Product telemetry — partial: One analytics vendor is named and consent-gated, and it records no storage location; our own usage sinks are stored in the same unlocated backend database.
- Model inference, including provider-side monitoring logs — partial: Five of ten providers state a location, five do not, and two policy pages could not be read at all; how long a provider keeps abuse-monitoring logs is recorded nowhere — the nearest sentence delegates it to the provider's own terms.
- Sub-processors, disaster recovery, key custody and deletion propagation — partial: Sub-processors are listed by category rather than by name or place, no disaster-recovery region is recorded, key custody is known as a posture rather than a location, and deletion propagation is across devices, not across regions.
What we cannot answer
Each gap says what is missing, why this repository cannot close it, and who could.
- Where our servers run — the database, its replicas, object store, queue and logs — why it stays open: This repository records a URL, never a region; a code probe cannot see a hosting console. Who could close it: The backend and infrastructure owner, through a facts file in that repository or an owner-attested fact.
- Where backups are kept and for how long — why it stays open: No period and no place are stated in either repository. Who could close it: The owner.
- How long providers keep abuse-monitoring and request logs — why it stays open: The providers' own terms are the only source, and nothing here records them — our training sentence delegates retention to those terms. Who could close it: A legal or owner read of each provider's terms, recorded with the read's date.
- A stated location for the five providers that give none — why it stays open: Two of those policy pages refused the fetch, so no location was read; the other three state none that we could find. Who could close it: The owner: re-read the policies, and keep 'unstated' until one states a place.
- A documented transfer mechanism, with any recipient, on either side — why it stays open: The product's own transfer sentences say none is in place, and the changelog records the earlier claim's retraction. Who could close it: The owner and counsel — a documented instrument or a recorded derogation. This statement cannot create one and does not imply one..
- Sub-processor names and places, not just categories — why it stays open: The published list is by category, and the DPA calls that a real limitation. Who could close it: The owner.
- Support access, break-glass access and staff tooling — why it stays open: Nothing in this repository describes staff access of any kind. Who could close it: The owner.
- A disaster-recovery region — why it stays open: Nothing anywhere records one. Who could close it: The backend and infrastructure owner.
- A place, rather than a posture, for client-side keys — why it stays open: The custody sentence says we never receive them and the vault is encrypted in the browser; the device is the place, and a device has no jurisdiction. Who could close it: Closed by design: rendered as 'this device', never as a jurisdiction.
- Code evidence for the Privacy Policy's 'in the United States' summary — why it stays open: It is a company statement with no measurement behind it in this repository; correcting or re-sourcing it moves a dated legal page. Who could close it: The owner and counsel, as a separate dated correction.