Data Retention Policy
CrowdSafeData uses defined retention periods so operational data is not kept indefinitely or deleted without an accountable rule.
Effective August 16, 2026 · Version 1.11. Principles
We minimize data, apply a documented purpose, separate source objects from metadata, restrict access and delete or de-identify data when the purpose ends. Customers should upload only information needed for the requested analysis.
2. Standard schedule
Target deletion within 30 days after delivery, unless a written order, active engagement, legal hold or verified retention entitlement requires longer.
90 days after delivery by default, unless exported, deleted sooner or retained under a written order.
12 months after delivery by default so accountable follow-through can be reviewed, unless a written order specifies another period.
Seven days, or earlier when accepted or revoked. Only token hashes are stored.
35 days under the operational backup schedule, with access restricted to authorized recovery workflows.
24 months after closure, except security or contractual cases requiring longer retention.
Normally 90 days; longer only for investigation, abuse prevention or legal requirements.
Seven years, or the period required by applicable financial and tax law.
Seven years for attributable commercial and analytical governance, unless a shorter period is contractually approved and legally permitted.
3. Contracted retention
Longer source availability, portfolio history and compliance archives require a documented purpose, approved duration and written commercial arrangement. A verified billing entitlement may remain visible in older subscription workspaces; the applicable order controls if it differs from the default schedule.
4. Holds and exceptions
Deletion may be paused for a documented legal hold, security investigation, dispute, fraud prevention or contractual obligation. When the exception ends, the ordinary schedule resumes. Deletion from active systems may precede expiration from protected backups.
5. Customer controls
Organization owners and administrators select retention through Billing. A longer period becomes effective only after the related payment-provider event is verified. Requests to shorten a period, export data or delete an organization should be submitted through Support and will be verified before action.
6. Disposal and evidence
Expired source objects are deleted through controlled retention workflows. Records needed to prove deletion, access decisions, billing or analytical governance may be retained separately with reduced content and restricted access.