Understand what a data-subject erasure removes
Documentation for Tutela v3.9.0.
A data-subject erasure removes or anonymizes records associated with the selected person. Understand which records are removed and which organizational records remain before requesting the operation.
Prerequisites
- Administrator authorization for the erasure request and the correct subject identity.
- Your organization's approved handling of shared content, retained records and backups.
- A test environment for rehearsing erasure; do not use a real person's account for a demonstration.
What is deleted
The erasure workflow removes the subject's personal data from participating content stores, including conversations, messages, files, usage records and feedback. It also covers supported derived copies of that feedback.
Review the result for each participating service. A deletion certificate is issued only when every required service reports completion. An accepted request or partially completed run is not a completed erasure.
What is anonymized instead
Organizational prompt templates authored by the person can remain while authorship and identifying fields are removed. Billing or cost-ledger records and governance evidence can also retain the record with the subject identifiers severed.
That distinction describes product behavior. Have your organization's privacy owner decide whether the retained content and any separately managed archives meet the requirements of the request. Removing an author field does not, on its own, demonstrate that arbitrary document content contains no personal information.
Check the outcome
- Verify the intended subject and approved scope before starting the erasure workflow.
- Follow the operation result for every participating service. Record any incomplete or failed result and its identifier.
- Review the deletion certificate after completion. If a service has not completed, resolve its reported problem and follow the supported recovery procedure rather than claiming completion.
- Inspect representative retained organizational records for the documented anonymization behavior. Review backup and external-system handling separately with the responsible owner.
Erasure changes stored data. If the wrong subject was selected or an outcome is unclear, stop further changes and contact support. Do not restore an old archive merely to reverse an erasure without an approved privacy and recovery decision.
If deletion is not confirmed
Only an authorized administrator should execute an erasure or its recovery. Access to reports does not, by itself, authorize deletion.
| Result | Meaning | Next step |
|---|---|---|
| Target user could not be verified | Deletion was not started because Tutela could not establish the selected user's directory record and permissions. | Ask an administrator to check the selected account and directory availability. An offboarded account can still be found; a missing account is not confirmation that all of its data was erased. |
| Verification pending | Deletion was started, but Tutela has not confirmed the required results. Some data may already have been removed. | Follow the reported recovery instructions and retry the same request after resolving the reported service problem. Do not create a second request just to obtain a successful result. |
| Original selection unavailable | Tutela cannot recover the original set of identity references used by this operation. Repeating the lookup against partially deleted data could miss records. | Stop and contact your administrator or support with the request identifier. Do not create a replacement request or manually guess the missing identities. |
| A service failed or returned an unreadable result | That service's deletion outcome is not confirmed. A successful connection does not confirm that its work finished. | Have the responsible operator investigate that service before following the supported recovery procedure. Keep the incomplete outcome in the request record. |
A deletion certificate records the participating services' reported results. Its integrity hash does not independently prove that every copy was removed, including separately managed backups or external systems.
For a support handoff, include the request identifier, occurrence time and timezone, affected service, and error code. Do not send the person's records or file contents in a support message.
Validate
- The subject and authorized scope were checked.
- Required services completed and the certificate was reviewed.
- Retained and separately managed data have an explicit owner and disposition.