PUBLIC INFORMATION
Data-retention plan
Proposed private-MVP retention periods and the safeguards still required before launch.
Principles
- Collect only data required to operate a team workspace.
- Keep secrets encrypted and gateway-only.
- Keep location-sensitive and high-volume data for the shortest practical period.
- Keep security audit records longer than ordinary activity history.
- Never sell stored Rust, Steam, Discord, chat, or location data.
Proposed defaults
Completed player sessions and inactive player profiles now have a daily 30-day cleanup. The remaining targets are not yet guaranteed by automated deletion and should not be treated as a final contractual schedule.
| Data | Target period |
|---|---|
| Team positions and trails | 7 days |
| Player presence and completed sessions | 30 days |
| Mirrored team/clan chat | 30 days |
| Device state samples | 90 days |
| Command decisions | 90 days |
| Alerts and delivery attempts | 180 days |
| Audit log | 365 days |
| Rust update events | 365 days |
| Shared wipe plans and assignments | Until the organization is deleted; active plans can be archived |
| Active configuration | Until changed or the organization is deleted |
Revoking a credential is intended to remove its encrypted secret immediately while preserving only the minimum security audit record. Backups expire through their rotation schedule rather than selective editing.
Export and deletion
Secret-excluding personal and owner-authorized team exports are available from System Health. Self-service account and team deletion require a fresh sign-in plus two-factor authentication, use exact confirmation text, create an audit record, and block deletion when a sole owner must transfer ownership first.
Deletion removes active application records. Independently rotated backups expire on their normal schedule rather than being selectively edited.
Engineering still in progress
- Daily, idempotent cleanup enforcement for the remaining time-limited activity data.
- Bounded organization retention settings.
- Backup expiry, restore, cascade, isolation, and interrupted-cleanup tests.
- Operator and legal approval of this proposed schedule before public launch.