What erasure is for
A person asks you to delete what you hold about them. Erasure deletes it from Synap’s live systems in one operation, run against a number you have both agreed on.How to request it
Erasure is not a self-service button. Email [email protected] with the instance and theuser_id or customer_id to erase, and the reason. Synap runs it, and it appears in your own Activity tab the same day with the email address of the person who ran it.
It is a support-operated action for one reason: a preview that says four things and an erasure that removes nine hundred is a conversation nobody should have to have. The two-step flow below is what prevents that, and it is run by a named person against a number you have both agreed on.
The two steps
1
Preview
The preview counts what would go using the same conditions the erasure itself runs, so the number it shows is the number of protected values and memory records that will be deleted.It reports:
- How many protected values would be deleted, broken down by field type
- How many memory records would be deleted
- How many values would be kept, because they are shared with other people
- A plain-language summary of all of the above
2
Erase
The erasure carries the number the preview showed. If the real total has moved since you looked, because new data arrived, the erasure stops rather than deleting a different amount than the one that was agreed.An audit entry is written before anything is deleted. An erasure that succeeded with no record of who ordered it would be worse than one that failed.
What is deleted
Every protected value held under that person’s own scope is deleted, along with their memory records and everything Synap built from them for search. Afterwards:- Every placeholder belonging to them stops resolving. Your application receives the placeholder rather than a value, and so do we.
- A reveal on one of those placeholders returns nothing, for anyone, including Synap staff.
- Backups taken before the erasure still contain these values and records until they expire.
Erasure does not touch the documents and conversations you sent, the conversation history Synap keeps, the person’s profile, customer-level knowledge, or saved request logs. If those must go too, say so in your request; they are handled as a separate job.
What is deliberately kept
Some values are shared by construction. Two people give you the same phone number. One company address appears in a thousand memories. Deleting a shared value while erasing one person would silently break every other person’s memories that reference it, and that failure looks like the product forgetting rather than like a deletion. So Synap erases the values held under that person’s own scope, and leaves values that are shared more widely. The preview counts them and says so plainly, in the form: “N value(s) will be kept, because they are shared with other people. Deleting them would break other people’s memories.” Whether a given shared value should also go has a real answer, and it is different per client. If it should, say so in your request and it is handled as a separate decision.Erasing an entire client
Removing a whole account makes every protected value it owns unreadable in Synap’s live systems, with nothing to search for. Backups taken earlier still hold the data until they expire. The memory text itself is left as sentences, with the placeholders in place.What this does not cover
- Deleting a whole person is not an SDK or CLI call. Request it through [email protected] as described above.
- Data ingested before you approved a policy is plain text. It was never protected, so there is no key whose removal makes it unreadable. Erasure cannot reach back and change that. If you need old data cleaned up, that is a re-processing job; ask us and we will scope it.
- Field types you never protected are plain text, for the same reason. Erasure protects what was protected.
- A person you cannot name cannot be erased. The operation works from a
user_idor acustomer_id. If your application does not pass a stable id, there is nothing to match on. - Copies the SDK keeps on your own machines. Erasure in Synap does not reach them; you remove them.
- Turns and tool results (Python 0.5.11 and later):
turns.db, withturns.db-walandturns.db-shmbeside it, in the SDK’s cache directory (~/.synap/{client}/{instance}/by default, or under yourstorage_path). It holds every conversation the agent has seen, not one person’s. From Python 0.6.3,sdk.cache.clear()empties them; on earlier versions, stop the agent and delete all three files. There is no call that removes one person’s turns. The SDK drops a conversation that has been idle for 7 days while it keeps writing. The JavaScript SDK (0.5.9 and later) keeps turns in memory only, and so does Python withcache_backend=None. - The stream outbox (both SDKs):
outbox/{instance_id}.jsonlunder yourstorage_path(Python only; elseSYNAP_STORAGE_PATH, else~/.synap). It keeps the text of events sent over the stream, delivered ones included, until the file is compacted. Delete it while the agent is stopped.
- Turns and tool results (Python 0.5.11 and later):
The paper trail
Every erasure writes one entry to your Activity tab, before it runs, recording who ordered it, what reason they gave, how many things it covered, and when. Your own staff and Synap’s appear in the same list with a column saying which is which. Entries are kept for at least one year and can be exported as a CSV file for an audit. A Synap staff member operating an impersonated session cannot run an erasure at all: impersonation exists so we can see what you see, and destroying data has to be done in a named person’s own name.Next steps
Aliases
What a placeholder is, and what stops resolving after an erasure.
Security and Trust
Deletion guarantees, encryption, and the limits we state plainly.
Sensitive Data Protection
What gets protected in the first place, and how you decide.
Sensitive data FAQ
Common questions from engineering and from security reviewers.