Know what happens to information over time.

1. Lifecycle scope

This disclosure covers account information, organization records, governance content, evidence metadata, activity history, support communications, billing references, security records, and information submitted through the public website.

Different information follows different retention and deletion requirements according to its purpose, customer instructions, workspace configuration, security needs, signed agreements, and applicable law.

2. Collection and minimization

• Collect information needed to create accounts, operate workspaces, deliver governance workflows, secure the service, administer billing, and respond to business communications.
• Use organization and role boundaries to limit access to customer content.
• Avoid collecting complete payment-card credentials by using Stripe-hosted payment entry.
• Ask customers not to submit credentials, classified information, or specially regulated information without confirmed safeguards and written terms.
• Review product and support workflows for unnecessary personal or sensitive information.

3. Active use and storage

Customer content remains associated with the applicable organization and authorized users while the workspace is active. Audit, evidence, billing, and security records may be retained to preserve integrity, investigate incidents, resolve disputes, and satisfy contractual or legal obligations.

Civerent does not currently train a general-purpose AI model using customer governance content.

4. Access and export

Customers can use supported reports and exports for available governance records. The precise export coverage depends on the product area and plan. Requests for additional access or portability may require verification of identity, workspace authority, scope, and applicable exceptions.

An export is not a complete independent backup unless it contains every record the customer needs and the customer stores and validates it separately.

5. Account closure and deletion

Cancellation stops future subscription renewals according to the Billing & Refunds policy but does not necessarily cause immediate deletion of every record. Workspace closure, legal retention, security investigation, unresolved billing, audit history, and backup processing may affect timing.

Authorized customers may request deletion through support. Civerent will evaluate the request, verify authority, identify applicable restrictions, and communicate the available process. No public page promises instantaneous or universal deletion.

6. Backups and residual copies

Information deleted from active systems may remain temporarily in protected backups, provider systems, logs, or legally retained records until the applicable retention cycle ends. Residual copies are not intended for ordinary business use after deletion.

Civerent does not currently publish a single fixed backup-deletion period that applies to every provider and data category. Customer-specific requirements must be confirmed contractually before deployment.

7. Requests and regulated workloads

Contact support before submitting health, biometric, criminal-justice, export-controlled, classified, or similarly restricted information. Civerent should not be assumed suitable for those workloads without written confirmation of the environment and terms.