Retention Summary
Current technical defaults and the limits of deletion claims during beta.
Effective 10 July 2026 · Policy 2026-07-10.v1 · Draft pending counsel review
Approved beta periods
Ended sessions and cron output are retained for up to 30 days, active sessions rotate after at most 90 days, and content-free security events are retained for 180 days. Runtime logs have a 30-day policy, but time-based host-log purge is still pending. Future generated export archives will expire after 24 hours once export is implemented.
Attachments
Inbound attachment caches are directed to an ephemeral in-memory quarantine and removed after processing or rejection, with an expiry sweep at 24 hours. Explicitly saved workspace files follow tenant-data retention and deletion controls.
Deletion
Reset removes active runtime content while keeping beta access and configured connections. Delete removes active runtime content, tenant credentials and connection configuration and cancels queued tenant work. Access/legal records and any bounded backup follow separate retention. Backup expiry has not yet passed production verification, so the beta does not claim that every copy is erased immediately.