Policy
Version 1.0 · Last updated: May 20, 2026
Owner: Security Lead and Privacy Lead · Reviewed annually
This policy describes how long Nexma retains data processed through the platform, how data is deleted when retention ends, and how customers can request deletion under applicable privacy law.
It applies to all customer data stored in Nexma production systems, including the Codex, conversation history, audit logs, and operational metadata.
Different categories of data serve different purposes and are retained for different periods:
Unless a customer agreement specifies otherwise, the following default retention periods apply:
| Category | Default retention |
|---|---|
| Project and Codex data | Lifetime of the customer relationship plus 90 days after termination, then deleted. |
| Codex history (snapshots, branches) | Bound to the parent project — deleted with the project after the 90-day post-termination window. |
| Conversation history | 1 year from creation, then deleted. Customers can request earlier deletion. |
| Audit logs | 7 years from creation — required for security investigation and contractual obligations. |
| Support records | 3 years from last activity on the ticket. |
| Marketing and contact data | 2 years from last engagement, then deleted or anonymized. |
| Backups | Encrypted backups retained for up to 30 days, then automatically purged on a rolling schedule. |
When a retention period ends, data is deleted from active systems through automated jobs that run on a defined cadence. Deletion is logged so that the deletion itself is auditable.
Deleted data is removed from production storage and remains in backups only until the backup retention window expires.
Some data — primarily projects — is soft-deleted first, allowing recovery during the 90-day post-termination window. After that window, hard deletion removes the data from active systems entirely. Hard deletion is the default for shorter-retention categories such as conversation history.
Customers can delete projects, Codex files, and conversations from within the Nexma product at any time. These actions trigger the standard deletion process described above.
Where applicable privacy law grants a right to erasure (for example, GDPR Article 17), data subjects may request deletion of their personal data. Where Nexma acts as a processor, requests are routed through the customer (controller); where Nexma acts as a controller, requests are handled directly.
Requests can be sent to legal@nexma.ai.
Backups exist for disaster recovery and are encrypted at rest. Backup retention windows are short and bounded; once an item is deleted from active systems, it is purged from backups on the rolling backup schedule.
Nexma does not restore individual deleted items from backups except as part of a documented disaster-recovery event.
Where Nexma is legally required to preserve data — for example, in response to a valid legal process — the affected data is placed on legal hold and exempted from normal deletion until the hold is released.
Legal holds are recorded and reviewed by counsel. Customers are notified of holds affecting their data unless prohibited by law.
Questions about data retention, or requests to delete personal data, can be sent to the privacy team.
Email: legal@nexma.ai