Admin HQ includes Privacy Ops for internal review of public privacy requests. Operators can see request references, request types, statuses, verification state, secure delivery readiness, destructive-action approvals, and workflow evidence.
Open Privacy Ops
From Admin HQ, open Privacy Ops or go to /admin/privacy. This surface is for internal Cendaro operators with Admin HQ access.
Use the public Privacy Policy link from the page when you need to confirm what customers and requesters can see before submitting or checking a request.
What the list shows
- Request reference.
- Request type, such as access, correction, export, deletion review, consent withdrawal, marketing opt-out, or other privacy request.
- Workflow status, such as Received, triaged, in review, waiting on requester, completed, or closed.
- Requester contact information and workspace or subject context when provided.
- Verification status and whether secure delivery is ready.
- Destructive-action status for requests that could delete, anonymize, or otherwise change sensitive records.
Triage before acting
Treat every request as unverified until the workflow shows the right verification state for the action being taken. Do not disclose request details, exports, subject data, or account-specific information just because someone knows a request reference.
- 1Confirm the request type and requester email.
- 2Check whether the request belongs to Cendaro directly or to a workspace owner acting as the customer-data controller.
- 3Review workspace hints, subject email, subject phone, and any subject auth user id carefully.
- 4Add internal triage notes that explain scope and verification without over-logging sensitive data.
- 5Update customer-visible status only with safe, minimal language.
Secure delivery and export requests
For access or export work, use secure delivery readiness instead of sending personal information through ordinary email or SMS. Export links should have a clear lifetime and should be tracked as workflow evidence.
Deletion and destructive actions
Deletion review requires extra caution. Confirm identity, scope, workspace ownership, backup and restore readiness, legal or support holds, and any required approval artifact before executing destructive actions.
When destructive actions are completed, keep the execution evidence and avoid adding unnecessary personal details to audit notes.
Retention and workflow evidence
- Privacy request workflow events help show what happened and when.
- Retention review may be required before redacting terminal request metadata or removing old export payloads.
- Legal signoff should be recorded before changing long-lived privacy request evidence handling.
Was this article helpful?
Your answer helps Cendaro improve launch documentation.