Help
Retention
How long each kind of data is kept, how it is removed, and which periods are our proposals and not legal findings.
Every period below is our proposal. A lawyer has not reviewed it. Yaqeen can change any period to match your agreement or your counsel's advice.
| Data | Period | How it is removed |
|---|---|---|
| Owner and store records | Life of the contract, then a period you agree with us (off by default) | Listed by the daily sweep. Erased only when an admin starts the erasure. |
| Assistant chats | 90 days after the last message | Daily sweep |
| Assistant confirm cards | 90 days after the card was used, cancelled or expired | Daily sweep |
| Finished webhook deliveries | 30 days | Daily sweep |
| Error records | 90 days | Daily sweep |
| Sessions | 14 days | Cleared daily |
| Unconfirmed appeal uploads | 1 day | Cleared daily |
| Sign-in codes for Claude and Codex | Work for 10 minutes and once. The row goes 1 day after it ends | Daily sweep |
| Access and refresh tokens for Claude and Codex | Access 60 minutes, refresh 30 days. The row goes 30 days after the refresh token ends or is revoked | Daily sweep |
| Apps registered by Claude or Codex | Kept while they have a code or token. An app with none for 90 days is deleted | Daily sweep |
| Audit log | Kept | Never. It is append-only |
| Backups | 14 daily copies | The oldest copy is deleted after a new one is checked |
A period of 0 turns that purge off. A legal hold, an open hold, an open appeal or an open dispute stops erasure of an owner's data.
Tokens for Claude and Codex#
Yaqeen stores only hashes of sign-in codes, access tokens and refresh tokens, never the values. A code ends after 10 minutes or its first use. An access token ends after 60 minutes and a refresh token after 30 days. A refresh token also ends when it is used, because each one works once, and when the person disconnects the app or an old one is shown again. After that the row is dead. The daily sweep deletes it after the period in the table above. The row holds the hashes, the app name, the person, the times and when the token was last used. When a person is erased, their codes and tokens are deleted at once. Each sign-in is also written to the audit log as oauth.granted, each new app as oauth.client_registered, each disconnect as oauth.revoked, a reused refresh token as oauth.replay_revoked and each tool call as mcp.call. The audit log is kept.