Updated October 7, 2026
Data retention
This is the configured retention behavior of deep.navy. Different records have different lifetimes. A cache age or a backup recovery window is not a promise that every copy is deleted at that time.
Completed run result payloads and delivered-match deduplication records become eligible for removal after 30 days. Cleanup runs hourly. Pending matches are retained. Run summaries and webhook delivery metadata do not have an automatic age cutoff.
Saved searches, destinations and secrets remain until the monitor is deleted. Deleting a monitor removes its configuration, runs, matches and delivery records from the active database. Copies may remain in backups.
Daily tool-call, webhook-delivery and active-monitor summaries are retained for 13 calendar months, with hourly cleanup. This is separate from detailed billing records.
Archived pages and previous versions currently have no automatic expiry. Moving a version to a lower-cost storage tier after 30 days does not delete it. Search indexes and public-source datasets have no uniform automatic deletion period.
Detailed tenant/key usage events, admission reservations and reconciliation records have no automatic age-based expiry configured. They are separate from the 13-month daily summaries.
Account records, key metadata, billing events, invoices and current invoice PDFs have no automatic age-based expiry. Revocation prevents further use of a key but does not erase its usage history. Previous versions of billing files become eligible for permanent removal after 90 days.
There is no uniform guaranteed retention period. Central application and gateway logs have no explicit automatic expiry configured. Trace storage is temporary and may disappear on restart. Do not use operational logs as your billing ledger.
The database backup service targets a 30-day recovery window. Versioned backup storage can retain older object versions beyond that window, so 30 days is not a guarantee of physical erasure. Backups are for disaster recovery and are not a customer archive.
Deletion and downstream copies
For an account, content or profile deletion request, contact privacy@deep.navy. We verify the request and identify active records, archived versions and backup copies. Records needed for billing, security or legal obligations may require separate handling. We do not promise immediate removal from every backup.
Deleting a monitor or account does not recall content already sent to your agents, webhook receivers or other downstream systems. You control retention there. Source providers also maintain their own records under their own policies.
See the privacy policy for the information we process and your choices.