Skip to main content
A retention period states how long a data category should remain available. Treat that policy separately from the mechanism that performs and verifies deletion.
Automatic retention enforcement and scheduled cleanup are not implemented. Saving the fields below does not start a deletion job or establish a retention deadline.
The workspace settings contract accepts those workspace preferences. They are not proof of a working cleanup process.
1

Define the scope

Specify the data category, intended period, policy owner, and whether existing records are included. Avoid using one transcript setting as a policy for every copy.
2

Save intent for review

Review the agent’s full privacy configuration in an agent draft. Read it back and record enforcement as pending.
3

Handle explicit removals separately

Use Delete conversation only for an identified, authorized record. Keep external exports and connected-service copies in your removal checklist.
No. It records intent without an implemented historical cleanup job.
No. A released scheduler, deletion scope, and verification process are required before making that guarantee.