Retention
Core Data Retention
This beta retention guide explains how workspace content, files, generated outputs, connected data, logs, and support records should be handled.
Last updated: June 26, 2026
Workspace content
Chats, project files, generated artifacts, hosted apps, data tools, media jobs, library outputs, commerce dashboards, and connected spreadsheet metadata are retained while the workspace remains active unless an authorized admin deletes the content or requests account deletion.
Operational records
Audit events, billing events, invite records, worker health, provider failure metadata, usage summaries, and support records may be retained for security, billing, troubleshooting, and support history. These records help verify tenant isolation and investigate incidents.
Backups and restores
Production backups should include both the database and object storage. Restore drills should validate login, membership, chat history, library artifacts, object downloads, worker health, and deletion tombstone replay before a backup process is considered proven.
Deletion requests
Workspace owners can request deletion or export assistance through support@epicglobalinc.com. Some billing, security, legal, audit, or incident records may be retained where required for compliance, accounting, fraud prevention, or incident response.
Connected provider data
Connected platform data is limited by provider permissions, retention windows, and workspace configuration. Multi-year commerce history should not be promised unless provider retention and legal review have been completed for that data source.