BreachSpiderBREACHSPIDER
Research Intel Features Docs About Sign In Sign Up Free

Data Retention

Data Retention Schedule, version 1.0, November 8, 2026. CITED Relevance LLC, operator of BreachSpider.

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

RecordKeptRemoved by
Account, team members, devices, sites, records, findings, acknowledgements, notes, maintenance workWhile the organization existsOrganization or device deletion
Saved reports and the evidence in them3 years from creation; a report you delete is removed 30 days later (Undo works until then)Daily retention job
Device check history and change events3 yearsDaily retention job
Bulk action and export records, Undo history3 yearsDaily retention job
Assistant action records and administrator audit records3 yearsDaily retention job
Daily progress snapshots3 yearsDaily retention job
Account audit logWhile the organization exists. How far back you can view or export depends on the plan.Organization deletion
Assistant conversationsUntil the user deletes themThe user, or organization deletion
Batch job inputs and results (API)30 days, or the period set for the API keyDaily retention job
Stateless device and Windows checks (API)Not saved; a usage record (key, path, status, count, time taken) is kept while the organization existsOrganization deletion
Connected app (hosted MCP) grants and tokens30 days after the connection ends; sign-in requests one day after they expire; registered apps never used, 7 daysDaily retention job
SessionsExpire after 30 days or at sign-outOrganization deletion
Sign-up acceptance records (document versions, time, IP address, browser)While the account existsOrganization deletion
Sign-in link send records (email address and time, used to limit sends)No automatic removal todayOrganization deletion, for members' addresses
Vault filesUntil a vault admin deletes a version; the seal and digests are kept after deletion so the history stays verifiableVault admin
Web server logs (IP address, address requested, browser)60 daysDaily log rotation
Application logsAbout 4 weeksWeekly log rotation
Encrypted database backups2 days on the server; about 30 days off the serverBackup job; storage lifecycle rule
Encrypted server file backups (no database files)7 daily, 4 weekly and 6 monthly snapshotsBackup job
Daily integrity anchors (signed chain heads, no customer content)At least 400 days (Object Lock)Storage retention

Deleting an organization

  1. The account owner deletes the organization in Settings. Sign-in stops at once.
  2. 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.
  3. 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.