Guides · Concepts
Retention and deletion
What is kept, for how long, what triggers a purge, and what a deletion leaves behind.
Journals#
| Journal | Kept | Purged |
|---|---|---|
| Request log of a project | 30 days and at most 5 000 entries | when an entry is written — a project with no traffic keeps its last entries longer than 30 days |
| SQL history of a project | the last 50 statements, at most 30 days — the statement text, never its results | when a statement is written |
| Function request entries | the same request log, under the function's key ids | with it |
| Site history (deployments, removals, refused attempts) | 24 months — it is part of the account audit journal | every hour, by the control plane; never triggered by traffic |
| Account audit journal (key created or revoked, destructive SQL confirmed, project deleted, GitHub events) | 24 months | every hour, by the control plane; never triggered by traffic |
| Payment events received from the payment provider | 90 days after they were processed; an event that could not be processed is kept until it is resolved | every hour, by the control plane |
The request log and the SQL history are not attributed to a person: no column names a user, so no deletion of a user reaches them, and their only bound is time. The SQL history keeps the text of statements, including the literals of INSERT and UPDATE — an e-mail address written by SQL stays there until the history rolls over.
Bearers and tokens#
| Lives | |
|---|---|
| Invitation link | 7 days, single-use |
| Password-reset link | 1 hour, single-use |
| Confirmation token | 5 minutes, single-use |
| Idempotency key | 24 hours; the record is removed within 25 hours |
| End-user session | 30 rolling days, 90 at most |
| Dashboard session | a one-hour token, renewed while the dashboard is open; no absolute limit and no inactivity limit today — signing out ends it |
| Remote connector tokens | code 10 minutes · access 8 hours · refresh 30 rolling days; a connector client that never completed its setup, 48 hours |
Deleting an end user#
When a person is deleted — by themselves, or by the account owner from the Users screen — what goes: their rows on prive and journal tables, every file they uploaded (public files included, because a public link has no expiry), their sessions, their space memberships, their seat. What stays: their rows on every other preset, kept so that a collective app keeps its history, with a frozen owner_id — nobody can edit them any more, they can only be deleted. The text of past SQL statements and the entries of the request log stay as they are.
Deleting a project#
Everything the project holds goes: tables and rows, end users, spaces, files and every link to them, keys, edge functions and their secrets, the site, the GitHub link. The account's audit journal keeps its entries about the project.
Deleting a file#
Every link to the file stops working immediately, public links included. It is the only way to take a public link back.
Deleting an account#
Deleting the account is not a gesture the API or the dashboard offer today: write to contact@manybases.com from the e-mail address of the account, and the account and everything it holds are deleted within 30 days — see the Privacy Policy, which also says what a deletion leaves behind and for how long.