Help Center/Governance, RBAC & Security Desk/How to work a privacy request to a decision
Governance, RBAC & Security Desk•Last updated: 2026-10-20•3 min read

How to work a privacy request to a decision

Move a request through RECEIVED, IN_REVIEW, AWAITING_SUBJECT and a decision, recording the legal-retention exception for erasure. No data is deleted by this console.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Start the review

On a RECEIVED row click "Start review". It moves to IN_REVIEW and is assigned to you.

2

Wait for the subject if needed

Pencil icon ("Edit Record"), set "Move request to" AWAITING_SUBJECT and save. When they reply click "Resume review" on the row.

3

Decide

Pencil icon, set "Move request to" COMPLETED, PARTIALLY_COMPLETED or REFUSED and write a "Decision note" of at least 10 characters. For an ERASURE request also fill "Legal-retention exception": which records are kept (ledger, audit, tax, AML) and the legal basis. Save.

4

Or record a withdrawal

If the subject withdrew, click "Record as withdrawn" on a non-closed row.

5

Read the result

The banner says the decision was recorded. For erasure it states plainly that this console deleted no data: ledger and audit records are retained, and removal of other personal data is a separate manual step.

Expected Operational Outcome

The request is closed with its decision note and retention exception, the SLA reads CLOSED, and every step is in the request event trail.

Troubleshooting & Failure Modes

Symptom: "A RECEIVED request can only move to: IN_REVIEW, REFUSED, WITHDRAWN"
Likely Cause: Requests cannot be completed without a review.
Resolution: Start the review first.
Symptom: "An erasure decision must record the legal-retention exception"
Likely Cause: The exception field is empty or too short.
Resolution: State what is retained and why.
Symptom: "Deciding an erasure request needs a super administrator"
Likely Cause: Erasure decisions are restricted.
Resolution: Ask a super administrator.
Symptom: "Someone else changed this request first"
Likely Cause: Two people acted at once.
Resolution: Reload and review its current status.

Was this guide helpful?

Help us refine our platform documentation

Related Ecosystem Documentation