Data retention
Draft — pending legal review
This page is a draft. It has not been reviewed by a lawyer and is not yet part of the legal terms. Items marked [to be filled] are not decided yet.
This page says how long data stays in the hosted service and what happens when you export or delete it. Contact for requests: [to be filled: contact email].
Export your data
An organization Owner can export the organization's data at any time, on every plan.
- One export every 24 hours. A second request inside that time is refused.
- The export is a ZIP file: organization, members, invitations, projects (with who can see each private project: login and whether they are a project admin), tracker settings (without tokens), resource lists and version metadata (without package content), Guardrails policies, the audit log, a billing summary and device-token metadata (without token values). It also holds Ryoma data: projects, task copies, weekly Flow and AI cost, and work sessions (login, time, cost, model, task key). It has no prompt content. A
manifest.jsonlists a SHA-256 for each file. - The file is kept for 7 days, then deleted automatically. You get an email with a link to the Portal, not a direct download link.
- Every export request and download is written to the audit log.
Delete an organization
Only an Owner can delete an organization. The owner types the organization slug to confirm.
- Grace period: 30 days by default (the operator can change it with
TARA_ORG_DELETION_GRACE; the hosted service value is[to be filled]). The organization moves to "pending deletion". The Paddle subscription is cancelled at the end of the billing period. Organization APIs refuse requests, except reading the deletion status, cancelling the deletion and exporting data. Service and device tokens stop working. The Owner can cancel the deletion in this time. - Purge. When the grace period ends, an hourly job removes the organization's data in this order:
- Ryoma: projects, task copies and all metrics, in PostgreSQL and in the analytics store (ClickHouse).
- Bandum in server mode, where it is configured: the organization's data.
- The organization's private packages and export files in the artifact store.
- Every row that belongs to the organization in Tara's database.
- One platform-level audit line that holds only a hash of the slug and the number of rows deleted.
- If a step fails, the job stops and tries again. A script,
verify-org-purge.sh, counts what is left and reports0 rows leftwhen the purge is complete.
Bandum on a developer's machine is not part of this: it keeps its data on that machine and we cannot reach it.
Delete your account
A person can delete their own account in the Portal or the CLI.
- It is blocked if you are the only Owner of an organization that still has other members. Transfer ownership or delete the organization first. If you are the only member of an organization, that organization goes into the same pending deletion as above.
- Deleted: your sessions, personal tokens, sign-in links to providers, tracker identities, project and organization memberships, and invitations sent to your email addresses.
- Your user record stays as a tombstone named
deleted-<hash>(the first 8 characters of a hash of your user id), with your name, email, avatar and GitHub identity cleared. Other records that point at you, such as who created a project or approved a version, now show this name. - Private personal resources are deleted. Personal resources you made public move to an anonymous owner (
deleted-<hash>), so people who use them are not broken. - Audit log. Old audit rows are kept, but the actor becomes
deleted-<hash>and your login and email are removed from the details. - Device tokens and SCIM tokens you created for an organization keep working with no creator, so a managed machine does not lose its policy and the identity provider keeps syncing.
- Ryoma replaces your login with
deleted-<hash>in its databases and clears your name and email in its user directory. It keeps organization totals. This call is queued and repeated until Ryoma confirms.
Audit log
The audit log has no automatic deletion. What changes by plan is how far back you can view and export it:
| Plan | View and export window |
|---|---|
| Free | 90 days |
| Team | 1 year |
| Enterprise | 3 years |
Audit export (a signed CSV or JSON file) is on Team and Enterprise. Free can view the last 90 days on screen.
Other data
- Email sign-in link records are deleted when a new link is created more than one day after the record. Sign-in codes are deleted one hour after they expire. Billing idempotency keys are deleted after 24 hours. Invitations expire after 7 days unless the inviter sets another time (90 days at most). Browser sessions last 7 days and Phillip sessions 12 hours by default.
- Ryoma raw telemetry is kept for the period the operator sets in
RYOMA_RAW_TTL; the default0skeeps it until the organization is deleted. The hosted service value is[to be filled]. - Invoices and records that the law requires us to keep:
[to be filled]. Paddle keeps its own records under its own policy.
Backups
The hosting runs a daily backup. It keeps 7 daily and 4 weekly copies and removes older ones.
When you delete data, the purge above does not edit past backups. Deleted data can stay in a backup until that backup is removed. The longest this takes is about 4 weeks (28 days), the age of the oldest weekly copy. Backups are for restoring the service after a failure. [to be filled: where backups are stored and whether they are encrypted].
See also the Subprocessors and the Data Processing Agreement.