Rights
What you can do with the data the platform holds, which surface owns each action, and the limit of every mechanism. The actions live in Data & AI; this page is the record section's map of them.
Export
One file with a manifest naming what it includes and what it omits.
Receipts
The stored record of each export: its sections, status and resumability line.
Ask a person
privacy@poly.inc — anything a mechanism cannot reach.
The account export builds one file whose manifest names every section it includes and every one it omits, with the reason for each omission.
The file is built per request and handed to you in that request. Its receipt is kept on this device (up to five) and this page reads it, so the export itself can be shown — it shows what one file carried, not that the whole account was answered.
The same export is offered from the account menu's data settings, beside account closure.
That window has no address of its own, so this page can name it and cannot link to it.
Anything the export leaves out can be asked for at privacy@poly.inc.
There is no ticket, queue or reply time behind that address on this page, and this app cannot read the mailbox.
What is not reached: An export receipt records the sections one file carried and the ones it named as missing; it does not cover the account, so an access request for everything stays partly covered here.
Some records can be corrected at Data & AI, and each correction reads the new value back before it is recorded.
Only the fields each row names can change. A section with no edit path says so with its reason, and copies on other devices or in another system are not reached.
A record with no correction path can be raised at privacy@poly.inc.
This page cannot see that mailbox, so it cannot show a request there moving.
What is not reached: Sections with no edit path have no correction this app can perform, so a request that names them stays open with that row's reason.
The deletion run at Data & AI deletes each section it can, reads every store back before calling a row gone, and mints a receipt that counts the result by outcome.
A section with no delete path is kept with its reason, exemptions are kept on purpose, and the receipt's account arm says the account itself was not erased.
We record your deletion request and close your account. Permanent deletion of the data on our servers is not available today: nothing is erased when you ask. We will act on recorded requests when erasure is available.
Closing the account is a different act from this request: it records a closure marker, and this page cannot observe either act's outcome.
The account-level part can be raised at privacy@poly.inc.
The mailbox is the only other route, and this page cannot see it or promise anything from it.
What is not reached: The account arm is never performed by this app, and sections with no delete path are kept, so a request for everything stays open and a scoped one is only finished where its row says deleted.
A request scoped to one purpose records the instruction through the same writer the restriction section uses, and keeps that record's id with the request.
A record in this browser cannot refuse a request a server route has already accepted, and a purpose with no declared sink cannot be refused at all. A request that names every purpose records no single instruction.
A purpose this app cannot refuse a sink for can be raised at privacy@poly.inc.
The mailbox reaches an operator outside this app; nothing on this page can show what happens there.
What is not reached: Most purposes have no refusal this app can prove, and a record here binds only this browser, so a request that names every purpose stays partly covered with the not-enumerated reason on each row.
A request scoped to one purpose records the objection through the same writer the restriction section uses, and keeps that record's id with the request.
An objection is refused by the same declared sinks a restriction is; the marketing objection is the one this app can refuse and never override, every other purpose keeps its not-enumerated reason, and a request that names every purpose records no single instruction.
Anything the objection cannot refuse here can be raised at privacy@poly.inc.
This page cannot see the mailbox, so it cannot report an outcome from it.
What is not reached: Only purposes with a declared sink can be refused, so an objection that names the rest stays partly covered and says why on the row.
The account export returns one file, and its manifest names each section the file carries and each one it leaves out.
The receipt names the sections the file carried and the ones it left out. It does not promise a machine-readable format for every section, and this page repeats no format the receipt does not state.
The account menu's data settings offers the same file.
That window has no address of its own, so it is named here and not linked.
A format the manifest does not cover can be asked about at privacy@poly.inc.
No response time is promised from that address on this page, and this app cannot read it.
What is not reached: A portability request is answered by the file itself: the stored receipt proves which file was produced and what it left out, not that every section is in a portable format.