# Entea data-retention and deletion policy

Last updated: 18 September 2026  
Status: Interim operating policy; pending legal review

This policy describes current product behavior and operating intent. It is not a substitute for an executed customer agreement. Signed contractual terms take precedence.

## Retention schedule

| Record | Current handling | Control |
| --- | --- | --- |
| Audit history | Configurable from 30 to 3,650 days | Organization administrator |
| Control-plane backups | Configurable from 1 to 365 days | Organization administrator |
| Production application database backups | 30-day default | Application policy |
| Non-production application database backups | 7-day default | Application policy |
| Temporary application databases | Seven-day default expiry unless renewed or promoted | System lifecycle |
| Active or archived application source | Retained until the organization requests deletion | Customer lifecycle action |
| Account, billing, and support records | Retained only as needed to operate the service and satisfy agreed legal obligations | Contract and legal requirements |

## Application deletion

Deleting an application requires the exact application name. If Entea manages an isolated application database, the operator must explicitly choose to delete application data or archive the application instead. External customer-managed databases are not overwritten by Entea’s restore control and remain governed by the customer.

A deletion can remove application-scoped source directories, preview processes, containers, routes, managed provider secrets, database containers or volumes, and owned database tables. Shared organization runtime infrastructure is preserved when one application is deleted.

## Organization and account deletion

Until a self-service organization-deletion workflow is published, an authorized organization administrator must send a deletion request through the public support form. Entea will verify authority, identify legal holds or billing obligations, confirm the scope, and provide a deletion plan before destructive work begins.

The final completion window for organization deletion is pending legal approval and must be defined in the signed agreement. Entea does not currently publish an unqualified deletion-time guarantee.

## Backups

Expired backup artifacts are removed according to the configured policy. A record may remain temporarily in operational logs to show that deletion occurred, but the expired backup payload must not remain available for restoration.

## Legal holds and exceptions

Data may be retained beyond the normal window when required by applicable law, a binding legal request, fraud prevention, security investigation, dispute preservation, or an executed agreement. Access must remain restricted to the purpose of the hold.

## Requests

Send access, correction, export, or deletion requests through https://entea.in/support. Do not send credentials or sensitive customer data in the initial request.