1. Data Retention Overview
ZeroTrace implements automated data retention policies to ensure that temporary data is not stored indefinitely. Our database cleanup process runs regularly to delete expired data based on predefined retention periods.
This policy outlines the specific retention periods for different types of data stored in our systems. Only data with expiration policies is covered here; data without defined retention periods is maintained according to other operational requirements.
2. Automated Database Cleanup Process
Our database cleanup process is implemented using a systematic approach that evaluates records against their retention criteria. The cleanup routine examines various tables and removes data that has exceeded its retention period.
Technical Implementation:
The cleanup process uses the runAllCleanups function, which executes multiple cleanup operations across different database tables. Each cleanup operation specifies:
- Model - The database table being cleaned
- TimeField - The timestamp field used to determine age (typically
created_atorexpires_at) - OlderThan - The retention period after which data is deleted
- ConditionField/ConditionValue - Additional conditions for deletion (optional)
3. Data Retention Periods by Type
The following data types are automatically deleted according to these retention periods:
Sessions & Tokens
Sessions and Tokens are deleted immediately upon expiration (when expires_at is passed).
Retention: Until expiration timestamp
Desktop Licenses
Desktop License records are deleted 3 hours after creation.
Retention: 3 hours from creation
Atlas Agents & Cooldowns
Atlas Agents and Cooldowns are deleted 14 days after creation.
Retention: 14 days from creation
Webhook Content
WebhookContent records are deleted 30 days after creation.
Retention: 30 days from creation
Notifications
Notifications are deleted under two conditions:
- Immediately when marked as seen/read
- 60 days after creation, regardless of read status
Retention: Until read, or maximum 60 days from creation
Messages & Reactions
Messages and Message Reactions are deleted 90 days after creation.
Retention: 90 days from creation
4. Backup & Recovery Policy
Infrequent Backups
Database backups are performed infrequently and are primarily used as a precautionary measure during server updates, maintenance windows, or infrastructure changes.
Backups are not created on a regular schedule and should not be relied upon for data recovery purposes.
Important: No Data Recovery
Once data is deleted from our database through the automated cleanup process, it cannot be recovered. We do not maintain archives or historical backups that would allow restoration of deleted data.
5. Data Without Expiration Policies
This retention policy covers only data that has defined expiration periods. Other data types stored in our database that do not have automatic deletion policies are not covered by this document.
Data without expiration policies may include:
- User account information
- Product and license ownership records (permanent)
- Transaction history and purchase records
- Administrative and audit logs
- System configuration data
For information about how we handle these types of data, please refer to our Privacy Policy and Data Processing Agreement.
6. User Rights & Data Deletion Requests
While automated retention policies handle temporary data, you maintain rights over your personal information under applicable privacy laws (GDPR, CCPA, etc.).
You have the right to:
- Request access to your personal data
- Request correction of inaccurate data
- Request deletion of your personal data (subject to legal retention requirements)
- Request data portability
- Object to processing of your personal data
To exercise these rights, please contact us at admin@zerotrace.pw.
7. Questions & Contact Information
If you have questions about our data retention practices, backup policies, or would like more information about how we handle your data, please contact us:
ZeroTrace Support
Email: admin@zerotrace.pw
This Data Retention Policy was last updated on November 13, 2025. We reserve the right to modify this policy at any time. Changes will be effective immediately upon posting.