Skip to main content
The data lifecycle page gives platform administrators a centralized view of privacy-related operations across all tenants — including data export requests, account deletion requests, and legal holds. Use it to approve, reject, or monitor jobs that affect user data.
This is the platform-level privacy administration page. For the consumer-facing privacy center where end users request their own data, see Privacy center.

Overview

The page opens with summary stat cards showing the total number of jobs and their breakdown by status:
StatusMeaning
PendingJob submitted but not yet reviewed or processed
ApprovedJob has been approved and is queued for processing
ProcessingJob is currently being executed
CompletedJob finished successfully
FailedJob encountered an error during execution
RejectedJob was reviewed and denied by a platform administrator

Jobs tab

The jobs tab lists all data lifecycle requests across tenants. Each row shows:
  • Job type — one of EXPORT, ERASE, or PURGE (see table below).
  • Target — the type and ID of the resource the job applies to.
  • Tenant — the tenant that owns the request.
  • Requested by — the user or system that created the job.
  • Status — current processing status.
  • Requires approval — whether the job needs manual approval before execution.
  • Timestamps — creation and last update dates.
Job typeDescription
ExportPackages the targeted user’s data for download
ErasePermanently deletes the targeted user’s personal data while preserving anonymized records
PurgeIrreversibly removes all data — including anonymized records — for the targeted resource

Filtering

Use the toolbar to narrow the job list:
  • Search — filter by tenant name, job ID, or target ID.
  • Status — filter by Pending, Approved, Processing, Completed, or Failed.
  • Type — filter by Export, Erase, or Purge jobs.

Job detail page

Click any job row to open the detail page. The page shows two information cards and a result panel:
  • Job information — job type, target type, target ID, and the reason provided when the request was created.
  • Context — the tenant ID, who requested the job, and (if applicable) who approved it.
  • Result data — once the job completes, this panel displays the raw JSON output. For export jobs this typically includes a download URL; for erase and purge jobs it contains a summary of records removed.

Approving and rejecting jobs

Jobs that require approval show Approve and Reject buttons. When you approve a job, it moves to the processing queue. When you reject it, provide a reason — the requesting user is notified of the rejection.
Approving a deletion job permanently removes the targeted data. This action cannot be undone. Review the job details carefully before approving.
Legal holds prevent data from being deleted or modified, even if a deletion request is submitted. They are used during litigation, regulatory investigations, or compliance audits. Each hold entry shows:
FieldDescription
Scope typeThe type of resource the hold applies to (tenant, user, issuer, etc.)
Scope IDThe specific resource ID under hold
TenantThe tenant the hold belongs to
ReasonWhy the hold was created
Created byThe staff member who placed the hold
ActiveWhether the hold is currently enforced
Expires atOptional expiration date for the hold
While a legal hold is active, any deletion job targeting the held resource is blocked.

Next steps

Privacy center

Consumer-facing privacy tools for data export and account deletion.

Audit log

Query and export audit events including privacy operations.