Psyche is a tool for self-reflection and self-discovery — not a clinical or diagnostic assessment. Insights are estimates that grow and change as you do.
Controls
withdraw a consent, restrict a purpose, file a rights request, and record a complaint
The consent controls below are read from the controls themselves and can be withdrawn from here. Withdrawing stops new processing; it does not erase what already exists, and every row says what it does not cover. Export, rectification and deletion already run at Data & AI, and imports at Imports. Restriction and objection are recorded below, with the sink each one refuses, and a rights request can be filed below the same section: it stays in this browser and is followed with two dates and the evidence this device can check. A complaint about how your data was handled has its own door below that: one date, a progress log, and a sealed receipt, and nothing on this page sends it anywhere. The list at the bottom says exactly which half of each is absent.
What this hub can do today: see what is held and what AI touches; export your data as one file, with a receipt this device keeps; correct a record, where this app has an editor for it; delete a section, read back, and keep the receipt." On this page: withdraw a consent, and find where it is turned back on and where its copies can be cleared — or why they cannot; restrict or object to a purpose, and see which sinks refuse; file a rights request and follow its dates; record a complaint about your data, and keep its dates and receipt on this device.
Consent controls
Every consent this app asks you for, with the state read from the control itself — not from a summary kept here. Withdrawing stops new processing; it does not delete what already exists, and each control says what remains.
Each row also names the surface where that control is turned back on, and where the copies it already made can be cleared — or says exactly why one of those has no address, or that there is nothing to clear. This page itself cannot turn a control on: a grant needs the notice its own feature shows.
7 of these choices are also recorded against your account; this page shows this device's copy of that record. A choice made on another device appears here after this device reads your account, and a row with no local record says Unknown rather than guessing. A control this device already reads as off has no second withdrawal to send — the surface it links is where its state can be changed.
Reading the consent controls on this device…
Restriction and objection
A restriction (GDPR Art. 18) stops processing while a question about your data is open; an objection (Art. 21) stops it because you said so. Unlike a consent control, these are instructions: the rows below say which sink each one actually refuses, and whether a test proves it. The record lives in this browser, and every row says what it cannot reach.
An objection to direct marketing is absolute: Sending you product news. The registered purpose is pa-newsletter: subscribing puts your email on a list our servers hold, and leaving it is an email to the address the form names. An objection here is against the marketing act itself — the subscription press — not against a separate practice outside the registry. Nothing on this page lets any other state override it — only you can lift it.
A record is filed under the identity signed in when you make it. One made while signed out stays in the signed-out partition and does not apply after sign-in — when that happens, this page names that record for the different identity rather than silently reporting no instruction.
Reading the restriction record on this device…
Rights requests
A request below is a record in this browser: it names the right, how far it reaches, who it is attributed to and when you filed it. Its status is worked out on every read from evidence on this device — it is never stored — so a lifted instruction or a new receipt changes what you see.
The controller’s published commitment is quoted, not paraphrased: “We respond within 30 days (45 where the law allows an extension).” — /legal/privacy See the privacy policy and the published address privacy@poly.inc.
A request is a record in this browser. This page cannot deliver it anywhere, and it cannot show that anyone else has seen it.
The record above carries no seal and no status. A receipt is a separate file you can download: it records that this device filed the request, at that time, and not the answer — nothing in it claims anyone else has seen the request.
Every date here comes from this device's clock. The response period runs from the controller's receipt of a request, which this page cannot see.
No identity document, one-time code or email round trip is offered here: this page has no receiver, no sender and no reader for them.
A request filed inside an organisation is stamped with that organisation as a routing label. It is not passed to it, and the stamp is not a permission: signing out of the organisation never orphans it.
Open a request
Access
The export manifest declares 40 sections: 19 are included in the file and 21 are omitted with the class that says why.
The account export builds one file whose manifest names every section it includes and every one it omits, with the reason for each omission. Open itWhat it does not reach: 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. (Account data settings)What it does not reach: 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. Open itWhat it does not reach: There is no ticket, queue or reply time behind that address on this page, and this app cannot read the mailbox.
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.
A stored export receipt, when this device holds one, shows what one file carried and what it named as missing — part of this request and never the account — so at best a request for everything stays partly covered.
Correction
Of 40 sections this app knows by name, 10 have a correction path here and 30 have none, so they become a mailbox matter.
Some records can be corrected at Data & AI, and each correction reads the new value back before it is recorded. Open itWhat it does not reach: 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. Open itWhat it does not reach: This page cannot see that mailbox, so it cannot show a request there moving.
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.
A section with no path here keeps this open, and its row says why.
Erasure
Of 40 sections this app knows by name, 13 can be erased outright, 11 are partly covered, 13 have no delete path and 3 are kept on purpose.
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. Open itWhat it does not reach: 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. (Settings → Account)What it does not reach: 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. Open itWhat it does not reach: The mailbox is the only other route, and this page cannot see it or promise anything from it.
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.
The account arm is never performed by this app, so a request for everything stays open.
Restriction
A record on this device can refuse a declared sink for 8 of 21 purposes; the other 13 say "not enumerated" with the reason.
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. (Restriction and objection (the section above on this page))What it does not reach: 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. Open itWhat it does not reach: The mailbox reaches an operator outside this app; nothing on this page can show what happens there.
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.
Most purposes have no refusal this app can prove, so a request for all of them stays partly covered.
Objection
A record on this device can refuse a declared sink for 8 of 21 purposes; the other 13 say "not enumerated" with the reason.
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. (Restriction and objection (the section above on this page))What it does not reach: 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. Open itWhat it does not reach: This page cannot see the mailbox, so it cannot report an outcome from it.
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.
Most purposes have no refusal this app can prove, so a request for all of them stays partly covered.
Portability
The export manifest declares 40 sections: 19 are included in the file and 21 are omitted with the class that says why.
The account export returns one file, and its manifest names each section the file carries and each one it leaves out. Open itWhat it does not reach: 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. (Account data settings)What it does not reach: 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. Open itWhat it does not reach: No response time is promised from that address on this page, and this app cannot read it.
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.
A stored export receipt, when this device holds one, shows what one file carried and what it named as missing — part of this request and never the account — so at best a request for everything stays partly covered.
Your requests
Reading the request record on this device…
The receipt for your requests
Filing a request, or recording an extension notice, makes one sealed file you can keep: it records what happened on this device, at that time, with the two dates the clock computed. It does not record an answer, a status or a stage, and nothing in it says a controller has seen the request. Keeping the file and checking it later is how the record outlives this browser: this device keeps at most 5 of them, newest first, and the oldest falls outside that bound.
Reading the receipt record on this device…
Complaints about your data
A rights request asks us to do something with your data. A complaint says how it was handled — the remedy is an answer, not an action on the data — so the two are recorded separately here.
Not sent. A complaint written below is a record in this browser and nothing else. It is not delivered anywhere: you send it yourself to privacy@poly.inc, or you write to that address instead of using this form. It can be made by form and by other means: privacy@poly.inc is the other means, and a complaint sent there is a complaint whether or not this page was used. The date beside a complaint is the earliest it could be due, if this reaches privacy@poly.inc the day you filed it — no one has promised a reply date here, and this page does not claim a complaint has reached anyone. This page records complaints; the privacy policy covers rights requests.
A complaint written on this page is a record in this browser. It is not sent anywhere: you send it yourself, or you use the published address instead.
The date is the earliest an acknowledgement could be due, counted from the day you filed. The period itself runs from when a complaint is received, which this page cannot see.
No reply date is promised here. The record shows how long it has been since anything was added, because a record that has been silent for a year should say a year.
This page counts nothing for anyone else. It keeps no figure that could be read as a report about how many complaints were made or how they ended.
A question recorded here is a fact about the record. It does not stop, pause or extend any date, and nothing on this page treats it as one.
Clearing this site's data in your browser deletes the record and its receipts, and nothing restores them. A downloaded receipt outlives the browser; nothing else here does.
Record a complaint
Your complaint records
Reading the complaint records on this device…
The receipt for your complaints
Filing a complaint, or recording an outcome you read, makes one sealed file you can keep: it records what happened on this device, at that time, with the one date the clock computed. It records no delivery, no status and no stage. This device keeps at most 5 of them, newest first, and the oldest falls outside that bound; clearing this site’s data deletes them and nothing restores them, so download the file if you want a copy that outlives the browser.
Reading the receipt record on this device…
Consent history
What you decided at each control, recorded on this device. This is a record of your decisions; it never decides anything itself.
Reading the ledger on this device…
Activity
What happened to your data — never your content. Five categories, each with what is recorded and what is not.
This record stays collapsed until you press the button. Pressing it checks that your session is still live. That check is not a new sign-in: this app cannot ask you to re-authenticate to view a page yet, because a passkey step-up for reading does not exist — so nothing here is protected by a second factor.
The fix is a `ledger.view` purpose in the step-up service. It does not exist yet, so this is a shoulder-surfing guard, not a second factor.
Administrator access
Not recorded here. Our servers keep a record of administrative actions — bans, plan changes, support changes to an account — but it is readable only by administrators and is not returned for your account yet. Nothing here can show it, and nothing here invents a row in its place.
Hidden until you reveal this record.
Consent changes
Recorded. Two records answer this: the decisions this device kept (with the wording you agreed to) and the change log your account returns, which carries no wording.
Hidden until you reveal this record.
Exports
Recorded. Each time a copy of your account is requested, your account's security event log records it. This list shows the last 100 account events.
Hidden until you reveal this record.
Deletions
Partly recorded. Your account's current deletion request is readable here — its state, not its history. Deleting a single item (a memory row, a conversation, a file) writes no record anywhere yet, so those deletions are not shown.
Hidden until you reveal this record.
Connector reads
Partly recorded. What left this device toward an AI or speech service is recorded on this device. Reads by accounts you connect in Settings keep no per-read log, so those are not shown.
Hidden until you reveal this record.
What will live here
A pause control for an import that is already running: no control suspends a live run where it stands and picks it up again later in the same pass.
Rectification of records this app has no editor for: each section without one says so on its row instead of implying an edit, and no correction is propagated to a copy this app does not hold.
Withdrawing a control again on this page when this device already reads it as off: there is no second press for a control already off here, so a grant made on another device can stand until you change it from the surface this row links.
What does not exist yet
Export is one request that returns a file whose manifest names what it includes and what it omits. It is not yet a job you can pause or resume. Data in this browser is in the file for 6 sections — the research workspace, psychology data, journal entries, the conversation list, the provenance records, and data you imported — and the browser's other 6 are named in the omissions list, each with its reason: the journal archive, finance data, the research session backups, the Studio library, reading and learning data, and the browser's cookie choice.
Deletion runs at /user/data and ships with its receipt: it lists what each section holds, deletes what this app can delete, reads every store back before calling a row gone, and counts the result by outcome. It does not erase your account — every receipt's account arm says so — and a section with no delete path says "not deleted" with its reason rather than being implied away.
Restriction and objection are recorded per purpose above and refuse the sinks this app owns — proved by a drill, cited on the row. Every purpose this app cannot refuse a sink for says "not enumerated" with its reason, and the record is device-local: it cannot bind a server, the sync service or the newsletter list.
Consent history on this device is shown above. Your account returns a change log of the same decisions, without the wording you agreed to — the wording and its hash appear in the device record. The 7 controls that reach your account (the 6 psyche choices and the analytics cookie) are recorded there; the local-copy control is a device preference with no account record. A decision made while browsing in incognito or private mode is not recorded anywhere, so it appears in neither list. Changes made before this device kept a record are missing from the device list; the account's change log covers them, but it carries no notice text.
No rights request filed here is delivered to an organisation. A request stamped with an organisation is a routing label only, the card says so, and the organisation's members list is the door that exists.
No identity document, one-time code or email round trip is offered for a request. This page has no receiver for them, and the strongest check it makes is the account this browser held when you filed.
No response date is promised by this page. Both dates on a request are the earliest it could be due if the request reached the controller the day you filed it, and the controller's own commitment is quoted from the privacy policy rather than restated.
Turning a control on is not offered from this page itself: of the 12 controls, 10 rows link the surface where the control is granted and 2 rows name the window that has no address — Account data settings, one window for 2 rows. The clear direction is a link for 7 of the 12 and says why it cannot be one for the other 5. A grant needs the notice each feature's own surface shows, and the journal theme control also needs this device's backlog choice.
A withdrawal does not delete copies already made, and it cannot reach a server this app does not own. Each control's exclusions say what remains.
A complaint recorded on this page is a record in this browser and is not sent anywhere: you send it yourself to privacy@poly.inc, or you write to that address instead. Nothing here can show that a complaint reached anyone, and the page says so before the press that records it.
No reply date is promised for a complaint. The one date shown is the earliest an acknowledgement could be due, counted from your filing day, with the caveat that the period itself runs from a receipt this page cannot see. A question recorded on the record changes no date on it, and a record silent for a year says a year.
Recording a complaint on this page does not replace email: privacy@poly.inc is an equal route, and a complaint sent there is a complaint whether or not this page was used. A complaint can be made by form and by other means, and nothing on this page escalates one anywhere.
Available today
Export runs at Data & AI and from the account menu's Account data settings window (that window has no address of its own, so it is named, not linked); deletion runs at Data & AI; closing your account lives in Settings → Account; imports, with their provenance and undo, run at Imports; psychology data has its own controls in Psyche data & privacy; and the egress ledger and cookie choice live in Settings → Privacy & Safety.