Data retention and deletion
What remains with your workspace, which evidence expires, and how deletion works.
Processing descriptions reviewed: 9 October 2026
Stored records
Investigation records include collected website evidence, review decisions and assigned work. Retention depends on the record type. Time limits below describe scheduled cleanup; collection or cleanup failures can delay removal.
| Record | Retention and removal |
|---|---|
| Account and monitor settings | Retained for the account or workspace that uses them, subject to deletion and shared ownership. |
| Findings, reviews, cases and corrective work | Retained as workspace evidence and history. Deleting one member does not remove the team's investigation records. |
| Website-investigation screenshots | Available for 30 days from capture. Scheduled cleanup removes older captures, including retained closure screenshots. Extracted evidence and decisions can remain with the investigation. |
| Website beacon observations, referral imports and inspection events | Scheduled cleanup removes observations not seen for 90 days, imports older than 90 days and inspection events older than 90 days. Current findings and review history are separate records. |
| Post-closure monitoring | Runs for the selected 7, 30 or 90 days. Ending checks does not erase the closure reason, comparison baseline or case history. |
| API keys and beacon installations | Revocation stops future use. Prior observations and audit history remain subject to their own retention. |
| Billing records | Retained for accounting and applicable legal obligations; account deletion does not remove required billing records. |
| Database backups | Rolling 30-day retention setting, with expired copies removed during successful backup rotation. |
Account deletion and shared workspaces
Account deletion removes personal account records and access. It does not erase a shared workspace that other members still use, or independently collected public intelligence. Shared investigation records and work history can remain with that workspace. Closing a workspace is a separate operation and can require transferring ownership or resolving its subscription first.
Revoking an API key or pausing a website beacon stops future authorized use; it does not erase evidence already collected. Billing records and records subject to legal retention obligations may remain. Deleted data can remain in backups until the next successful rotation removes the relevant copy.
Use Settings to request account deletion. Access and ownership checks apply before removal. Authentication-provider removal follows the database operation and can fail separately; an unsuccessful request must be investigated rather than treated as complete.
Backups and recovery
Database backups are scheduled daily with a weekly restore check. They are access-controlled recovery copies. Removing data from the live database does not immediately remove it from an existing backup. The rolling retention setting is applied by the backup job during successful rotation.
Providers and processing locations
| Provider | Purpose | Data involved |
|---|---|---|
| Microsoft Azure | Primary application, database and backup hosting in Central US. | Account, workspace and investigation records. |
| Auth0 / Okta | Sign-in and identity management. | Account identity and authentication information. |
| Stripe | Subscriptions and payments. | Billing identity, payment details and invoices. |
| Postmark | Transactional email and configured alerts. | Recipient addresses and message contents. |
| Twilio | SMS delivery when configured. | Recipient phone numbers and message contents. |
| Cloudflare | DNS and edge services. | DNS queries and network/request information for traffic it handles. |
| Anthropic and OpenAI | Automated finding review, investigation assistance and report drafting. | Relevant finding context, public-page content and images where the feature uses them, and investigation prompts. |
| Shodan, AbuseIPDB and Hudson Rock | Exposure, reputation and credential-exposure lookups when used. | Lookup targets such as IP addresses, domains or email addresses, depending on the feature. |
| Public intelligence and registration services | Certificate, DNS, registration, advisory, repository and app-store evidence collection. | The public lookup targets required by the source. |
| Destinations you configure | Delivery to Slack, Teams, webhooks or connected API/MCP tools. | The findings, asset context and messages delivered through that integration. |
Primary application hosting is in Azure Central US. Providers and connected destinations may process data in other locations under their own terms. Feature-specific recipients receive data when that feature runs; this includes scheduled collection and automated review.
Access, correction and privacy requests
You can review your records in the product and use the available exports. For a complete personal-data request, a correction or a deletion that is not available through the interface, contact privacy support. Your rights and the response commitment are described in the privacy notice.