Deleting data
How to delete one person, one session, a release's source maps, a project or a whole organization from Sypnia, what each deletion removes, how fast, and what stays.
On this page
- What you can delete
- Delete one person
- Stop sending them first, if they must not come back
- Delete
- Check
- Delete one session
- Delete a release’s source maps
- Delete a project
- A single problem
- Delete an organization or your account
- How fast, exactly
- What deleting does not reach
- Engine and Cloud
- Example: the shop is asked to forget a customer
- Related
This page is for whoever must remove something from Sypnia: because a person asked to be forgotten, because a recording caught what it should not, or because a project is over. It applies to the open-source engine Engine and to Sypnia Cloud Cloud. The calls are the same; who may make them differs, and each section says so.
You do not have to delete anything for data to go away. Everything has an age limit, and Sypnia deletes it when it passes that age: see Data location and retention for Sypnia Cloud and Retention for a self-hosted engine. This page is about deleting sooner.
What you can delete
| What | How | Who may | Done |
|---|---|---|---|
| One person and everything tied to them | DELETE /v1/people/{person_id} | An API token with admin. On Sypnia Cloud, also an owner or an admin, in the app. | Lists at once, files within 24 hours |
| One session, with its events, replay and page snapshots | DELETE /v1/sessions/{session} | The same | The same |
| A release’s source maps | DELETE /v1/releases/{version}/sourcemaps | An API token with admin | At once |
| A project and all of its data | Engine: sypnia project delete, with the root token. Sypnia Cloud: in the app, by an owner. | See the section | Ingest stops at once, files within 24 hours |
| An organization, or your account Cloud | In the app | An owner; you, for your own account | See the section |
In the examples, https://api.sypnia.com is Sypnia Cloud. On a self-hosted engine use your own base URL, with the same paths.
Delete one person
Use this to answer a request to be forgotten. A person is whoever your app named with identify(); their id is the one your app chose.
Stop sending them first, if they must not come back
New events with the same id create the person again. If the person also withdrew their agreement to be recorded, make sure your app no longer starts the SDK for them, or no longer calls
identify()with their id. See Privacy and masking.Delete
Terminal curl -X DELETE "https://api.sypnia.com/v1/people/u_0977" \ -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"You should see202 Accepted, with how many sessions will go and the latest moment by which every stored file is gone:JSON { "person_id": "u_0977", "sessions": 3, "status": "deleting", "done_by": "2026-03-13T10:40:00Z" }
What it removes:
- The person’s record: their id, and the name and e-mail your app sent, if any.
- Every session of theirs: the timeline, the replay, the page snapshots.
- Their events inside the stored files. The raw event files and the daily Parquet files that held them are written again without them.
- Their place in the list of people each problem hit. The problem keeps its count.
- A problem’s stored example, when it came from one of their sessions. It is replaced by another occurrence, or left empty when there is none.
What it keeps, because it holds nothing about the person: totals. A problem still says it hit 3 people, a page still has its performance numbers, and the month’s usage counters do not change.
Someone your app never identified has no person record. Delete their visits one by one, as sessions.
Delete one session
Use this when a recording caught something it should not have, or for a visit by someone your app never identified.
curl -X DELETE "https://api.sypnia.com/v1/sessions/c4e1a8f3d7b24c69a0e5d3b1f9c7a5e3" \
-H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"204, with no body. The session leaves lists at once; its files are removed within 24 hours.It removes the session, its events, its replay and its page snapshots. Counts on problems and performance numbers stay as they are.
There is no call that deletes only the replay and keeps the timeline. If a screen shows what it should not, mask it first, so that new sessions are clean, then delete the sessions that were recorded before.
Delete a release’s source maps
Source maps contain your source code. Delete them when a release is retired and you do not want its code kept, without waiting the 90 days after the release was last seen.
curl -X DELETE "https://api.sypnia.com/v1/releases/4f2a91c/sourcemaps" \
-H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"204. Stacks that were already translated stay readable. New failures in that release show the built file names.Delete a project
It deletes the project, its keys and tokens, and all of its data: problems, sessions, replays, numbers, source maps. It cannot be undone.
Engine On a self-hosted engine, with the root token:
sypnia project delete playgroundWith Docker Compose, run it inside the container: docker compose exec sypnia sypnia project delete playground.
The same through the API is DELETE /v1/projects/{project_ref}?confirm=<slug>, with the root token. See the API reference.
Cloud On Sypnia Cloud a project is deleted in the app, in the project’s settings, by an owner of the organization. The API answers 403 cloud_managed.
A single problem
A problem is kept for as long as its project exists, so that Sypnia can say «came back» months later. It holds the sentence, the analysis, the status, the counts for each day and one example of the failure: no session, no replay.
- To stop hearing about it: ignore it. An ignored problem never alerts and never reopens.
- To remove what it holds about a person: delete that person, as above.
- Cloud To delete the problem itself: an owner or an admin can delete it in the app. If the same failure happens again, it is a new problem.
- Engine The engine’s API has no call to delete one problem at launch. Its record goes when the project is deleted.
Delete an organization or your account Cloud
An organization. An owner deletes it in the organization’s settings. This deletes every project in it and all their data, as above, ends the plan, and removes the members’ access. The members’ own accounts are not deleted.
Your account. You delete it in your account’s settings. You leave every organization and your sign-in details are deleted. You cannot delete your account while you are the last owner of an organization: give the ownership to someone else, or delete the organization first.
What Sypnia Cloud keeps after either:
| Kept | For how long | Why |
|---|---|---|
| Invoices and payment records | As long as accounting rules require | We must be able to show what was billed. |
| Database backups that still contain the data | At most 7 days | Backups are not edited. They expire. They are not restored except to recover from a failure of ours. |
| Request logs of our servers, with IP addresses | 30 days | To investigate abuse and failures. |
How fast, exactly
| Moment | What is true |
|---|---|
| The call answers | The person, session or project is gone from every list, search, API answer and MCP tool. |
| Within 24 hours | Every stored file is deleted or written again without the data. For a person, done_by in the answer is that moment. |
| Sypnia Cloud, within 7 more days | The last database backup that contained it has expired. |
On a self-hosted engine the worker does the second step. If it is not running, nothing is removed from the bucket until it runs again.
What deleting does not reach
Sypnia can delete what Sypnia holds. It cannot reach copies that already left:
- Alerts already delivered. An e-mail in someone’s inbox, or the body your webhook receiver stored.
- What the agent sent to the AI provider. It stays with that provider for as long as that provider keeps requests. Replays and typed input are never sent. See Models and what is sent.
- What your coding agent read through MCP, and whatever it wrote into a conversation or a file.
- Pull requests Cloud that Sypnia opened in your repository.
- Your own copies: exports you made through the API, the daily Parquet files you copied elsewhere.
- On a self-hosted engine: your database backups, and old versions of objects if you turned on versioning in the bucket. Both are yours to expire. See Storage layout.
Engine and Cloud
| Sypnia engineOpen source, self-hosted | Sypnia CloudPaid service, with a free tier | |
|---|---|---|
| Who may delete | Whoever holds an API token with the admin scope. A project: whoever holds the root token. | Owners and admins, in the app, and API tokens with admin. A project or the organization: owners only. |
| Who does the deleting | Your worker, in your bucket and your database. | We do. |
| Backups | Yours. Deleted data stays in them until you expire them. | Database backups expire after 7 days. |
| Proof | Look in your own bucket and database. | The API answers 404 at once. We do not issue a certificate of deletion. |
Example: the shop is asked to forget a customer
A customer of the shop writes to ask that their data be removed. The shop identifies people by its own user id, so support finds the id in the shop’s admin: u_0977.
- The shop deletes the customer’s account in its own system, so the app no longer identifies them.
- Someone with an
admintoken runsDELETE /v1/people/u_0977. The answer says 3 sessions, done by tomorrow at 10:40. - At once, searching Sypnia for
u_0977finds nothing. The problem that customer hit last month still says «3 people»; it no longer says who the third was. - The shop answers the customer.
Related
- Everything Sypnia holds, so you know what there is to delete.
- What expires by itself on Sypnia Cloud, and when.
-
Sessions and replays, in the API
The delete calls with every parameter and error.