OmegaOS
Data governance

Data Retention Policy

How Omega sets retention periods, handles customer content, backups, logs, legal holds, export, and deletion.

Status
Published policy
Owner
Omega Privacy, Security, and Records Governance
Effective
July 21, 2026
Last updated
July 21, 2026
Internal review posture

Published following operator-authorized Omega privacy, security, claims, and operational review. External counsel review is not recorded.

External counsel posture
External counsel review recommended

Data Retention Policy is operator-authorized for public publication. External counsel approval is not recorded and remains recommended before material commercial or regulatory reliance.

Retention principles

Omega retains information only for a defined service, security, evidence, commercial, legal, or customer purpose. Retention is based on data type, sensitivity, customer configuration, active relationship, contractual commitments, legal obligations, and deletion feasibility.

Accounts and relationship records

Account, administrator, entitlement, support, and relationship records are kept while the account or business relationship is active and afterward for a limited period needed for reactivation, dispute handling, fraud prevention, and legal obligations.

Customer Content

Customer Content is retained while needed to provide the configured service and according to the controlling agreement, workspace settings, and customer instructions. Customer-selected memory, evidence, or replay features may intentionally retain records longer than transient processing.

Security and operational logs

Logs are retained for risk-based periods needed to detect abuse, investigate incidents, maintain service integrity, prove release or workflow events, and meet contractual or legal requirements. Not every component uses the same period.

Commercial and financial records

Orders, invoices, payment references, usage records, credits, refunds, tax records, and accounting evidence are retained for the period required by applicable commercial, tax, audit, and financial-record laws.

Cookies and public analytics

The first-party cookie preference record may remain for up to one year unless the visitor deletes or replaces it. Optional public analytics events are recorded only when the consent contract allows them and are retained according to the campaign, security, and analytics purpose.

Backups

Backups expire through managed rotation and may not support immediate record-level deletion. Deleted production data can remain in protected backups until the relevant backup expires or is overwritten. Backup data is restored only for recovery and remains subject to access controls.

Deletion and export

Customers should request export before termination. Omega deletes or returns Customer Content as the agreement requires, subject to technical limits, backups, legal obligations, unresolved disputes, security evidence, and legal holds. Deletion from active systems does not require alteration of immutable financial or security records that must be preserved.

Questions and requests

Privacy requests can be submitted through Privacy Choices or privacy@omeganeural.com. Contract customers should identify the workspace, data category, requested action, and controlling agreement.

Related policies

Read this page with the related policy, trust, and service information that applies to your use of Omega.

Contact Omega