How your data works in Resonae

Nothing leaves you without a deliberate step

The system does not auto-save, does not write anything implicitly, and keeps no “soft delete” that retains data in a hidden state. Anything you keep, and anything you share, happens because you took an explicit action to make it so. What each of those actions does — keeping, sharing — differs by space, and is spelled out below.

The system never interprets you

The system does not analyze your writing across sessions, does not identify recurring themes or patterns over time, and does not build a behavioral profile from how you use the space. There is no recommendation engine, no “based on your previous sessions” feature, and no internal analytics that aggregate your content. What you write is treated as discrete material you authored — never a corpus to be mined.

The AI never learns who you are

When AI is present, requests to the AI provider carry no identity at all — not your email, not your name, not your account identifier, and not a pseudonym or stand-in for any of those either. Nothing in a request lets the provider connect it to you, or even tell that two requests came from the same person. What is sent is the text of the exchange plus the minimal session context a response needs — which posture and pacing you chose, and how long the session has been open. Never a date or clock time, never a session or account identifier, never anything that names you.

One honest caveat: your words are your own. If the text you write contains identifying details, those travel with it — removing identifiers cannot make your own words anonymous.

Every request the system makes to the provider carries an explicit instruction not to store the interaction and not to use any part of it for model training. Logging is also switched off at the account level, so the instruction does not stand alone.

What the provider keeps. We do not have a zero-retention agreement with them, so rather than claim more than we can, here is their policy: inputs and outputs may be securely retained for up to 30 days, to provide the service and to identify abuse, and are removed after that unless they are legally required to keep them. What sits in that window is the text of an exchange attached to nothing — not to you, and not to any other exchange.

Deletion removes everything you hold

When you close your account, the same process runs across your entire history in all three spaces: your reflections and their audio, your Connection cards, books, facets, connections, and canvas contributions, and any live Studio scene — along with your shared snapshots, data export files, and preferences. Every stored file is deleted, not just the database reference that points to it, and your authentication record is removed last. The system verifies the deletion completed before reporting success, so a partial deletion is never reported as done. (Deleting a single reflection works the same way for that entry, its audio, its waveform, and any snapshots made from it.)

What backups can and cannot hold. Recordings, images, and export files live in file storage, which is never part of our database backups — once they are deleted, no backup can bring them back. The database itself is snapshotted once a day, and those snapshots are kept for up to eight days, for disaster recovery only. So text you authored may sit in a snapshot for up to eight days after you delete it, and then rotates out. We keep no continuous record of database changes. Deletions are also recorded outside the backup system, so that if we ever had to restore one, what you deleted is deleted again rather than quietly returning.

Your words never leave in error reports

When the system encounters a technical error, it sends a diagnostic report to the development team — but first it strips out the content of your request: your writing, any audio, any conversation history. The report contains only technical metadata: the type of error, the part of the system involved, and the HTTP status code. Your words never cross the application boundary in an error report.

You can take everything with you

You can request a full data export from your account settings. It spans all three spaces — your saved reflections, your Connection material (cards, books, facets, connections, and your own canvas contributions), any live Studio scene, and your preferences and session history — in a machine-readable format alongside readable copies of your reflections. The export file is available for 24 hours via a secure link, then automatically deleted. (You can also download an individual audio recording from any saved entry at any time, via a short-lived link.)

Reflection — private, and yours to keep

When you open a reflection, your writing exists only in your browser and in temporary server state. At the end you are asked explicitly whether to save or discard; if you discard, the content is removed from the server. A draft exists solely to protect you from accidental loss — a crash or a dropped connection — and a scheduled job clears any draft that exceeds its time-to-live; a draft is never promoted to a saved entry without your action.

A saved reflection is yours: only you can see it, it has no expiry, and it stays until you delete it. Sharing one creates an immutable snapshot — a copy as it existed the moment you shared — and revoking the link deletes that snapshot itself, not merely the link. A shared reflection has no time limit of its own; it stays available until you revoke it.

Studio — a practice space that forgets

A Studio scene is deliberately temporary. Nothing you do in it becomes part of your saved history — there is no entry, no thread, no record that persists. The scene and everything said in it become inaccessible within about a day of when the scene began, and are permanently cleared from storage shortly after.

While a scene is still live, a data export can include your own words from it (only your side — never the simulated character’s lines, and never the discussion layer). Once the scene has cleared, there is simply nothing left to export or to delete.

Connection — shared by design

Connection is the one space where something you make can become visible to another person — always by a deliberate step, and the steps do not all behave the same way.

A card you send is a snapshot fixed at the moment you send it. Its link lapses on its own after 30 days, and you can withdraw it before then. One boundary is worth naming plainly: once a recipient claims a card, it is saved in their account and becomes theirs — you can stop sharing a link, but the system will not reach into someone else’s account to remove what they have kept.

A facet you share becomes visible to the people you share it with. A shared canvas takes both people to open, stays visible to both while it is open, and persists as your shared record — either of you can close it to read-only at any time.