OmegaOS
Privacy draft

Data Retention

Explains retention periods and deletion posture for website, account, customer, support, evidence, and billing records.

Status
Counsel review required
Owner
Privacy + Security + Mnemosyne + Aureus
Last updated
July 1, 2026

Required coverage

  • Website and consent logs.
  • Account and authentication records.
  • Customer content, memory, source, workflow, and evidence records.
  • Billing, tax, accounting, invoice, payment, and revenue-recognition records.
  • Support, security, incident, audit, and legal hold records.
  • Deletion, anonymization, export, and exception handling.

Retention principles

  • Retain data only as long as needed for service delivery, customer instructions, legal obligations, security, billing, tax, accounting, dispute, audit, backup, and legitimate business purposes.
  • Define retention by data category, workspace, package, customer instruction, legal hold, and product behavior.
  • Minimize personal data in logs, prompts, telemetry, memory, analytics, and support records where practical.
  • Separate deletion from anonymization, aggregation, backup expiration, and legal hold exceptions.

Deletion and export

Final implementation must define customer export, workspace deletion, account deletion, memory deletion, backup expiration, retained legal records, and processor assistance obligations under the DPA.

Legal holds and exceptions

Omega may need to retain information where required for legal, tax, accounting, security, fraud, dispute, audit, contractual, regulatory, or backup reasons. Legal hold process and owner must be documented before enterprise launch.

Draft disclaimer

This page is a structural legal/trust draft for Omega website preparation. It is not legal advice, not a final customer commitment, and not a substitute for counsel, privacy, security, compliance, and Agora claim review before publication.