Retention principles

• Keep data only for the service, security, audit, contractual, or legal purpose for which it is needed.
• Apply tenant-configured schedules where supported and restrict access throughout the retention period.
• Do not describe a deletion as complete while active replicas, queued work, or applicable backup windows still contain the record.

Deletion workflow

A validated deletion request is authorized, scoped, recorded, and propagated to applicable active systems and integrations. Exports and derived artifacts are included when identified by the agreed scope. Completion evidence records what was deleted, exceptions, and the remaining backup-expiry window without exposing deleted content.

Backups, logs, and legal holds

Immutable or disaster-recovery backups expire according to the contracted backup lifecycle and are not restored for ordinary product access. Security and audit logs may have a separate documented retention period. Legal holds, fraud prevention, disputes, and statutory duties can pause deletion for narrowly scoped records.

Termination and requests

Data return and deletion at termination follow the executed agreement and DPA. Customer administrators should use approved in-product or support workflows. Privacy requests for Lawie-controlled data can be sent to privacy@lawielabs.com without attaching sensitive workspace content.