Data Retention
Each period below is enforced by a scheduled job or a database rule, not just stated. Saved reports are kept for 3 years (owner decision, November 2026). Where nothing removes a record automatically, the table says so.
Schedule
| Record | Kept | Removed by |
|---|---|---|
| Account, team members, devices, sites, records, findings, acknowledgements, notes, maintenance work | While the organization exists | Organization or device deletion |
| Saved reports and the evidence in them | 3 years from creation; a report you delete is removed 30 days later (Undo works until then) | Daily retention job |
| Device check history and change events | 3 years | Daily retention job |
| Bulk action and export records, Undo history | 3 years | Daily retention job |
| Assistant action records and administrator audit records | 3 years | Daily retention job |
| Daily progress snapshots | 3 years | Daily retention job |
| Account audit log | While the organization exists. How far back you can view or export depends on the plan. | Organization deletion |
| Assistant conversations | Until the user deletes them | The user, or organization deletion |
| Batch job inputs and results (API) | 30 days, or the period set for the API key | Daily retention job |
| Stateless device and Windows checks (API) | Not saved; a usage record (key, path, status, count, time taken) is kept while the organization exists | Organization deletion |
| Connected app (hosted MCP) grants and tokens | 30 days after the connection ends; sign-in requests one day after they expire; registered apps never used, 7 days | Daily retention job |
| Sessions | Expire after 30 days or at sign-out | Organization deletion |
| Sign-up acceptance records (document versions, time, IP address, browser) | While the account exists | Organization deletion |
| Sign-in link send records (email address and time, used to limit sends) | No automatic removal today | Organization deletion, for members' addresses |
| Vault files | Until a vault admin deletes a version; the seal and digests are kept after deletion so the history stays verifiable | Vault admin |
| Web server logs (IP address, address requested, browser) | 60 days | Daily log rotation |
| Application logs | About 4 weeks | Weekly log rotation |
| Encrypted database backups | 2 days on the server; about 30 days off the server | Backup job; storage lifecycle rule |
| Encrypted server file backups (no database files) | 7 daily, 4 weekly and 6 monthly snapshots | Backup job |
| Daily integrity anchors (signed chain heads, no customer content) | At least 400 days (Object Lock) | Storage retention |
Deleting an organization
- The account owner deletes the organization in Settings. Sign-in stops at once.
- An hourly job permanently deletes the organization 20 to 21 hours later, inside 24 hours: members, sessions, keys, devices, findings, records, reports, conversations and every other row that belongs to it. The job checks that no row in any table still refers to the organization; if one does, it rolls back and the deletion is retried and investigated.
- Copies in encrypted database backups age out within about 30 days. Restores from backup are made only to recover the service, and a deleted organization is not restored.
An organization with MSSP client organizations under it is not deleted automatically; we contact the owner first.
