Skip to content

Using Privacy Center

This guide is for staff who handle privacy requests and owners setting the policy. Every step uses the labels you see on screen. Follow your organisation’s legal process alongside these steps.

  1. Go to Privacy center > Privacy requests.
  2. Open the request, check its type, due date, and workflow details, then verify who is asking with Mark verified.
  3. The request moves to processing. Complete the required operational work and retain any evidence in the request’s workflow details.
  4. For a verified Delete request with a resolvable subject, Mark fulfilled performs the configured anonymization and erasure work. For an access or export request, prepare and deliver the export through your approved process before marking it fulfilled.
  5. Use Reject with a reason if the request cannot proceed.

An operator triages access, export, and deletion requests from a single compliance queue.

How to export or erase a customer’s data

Section titled “How to export or erase a customer’s data”
  1. Open the verified request and check that it is in processing.
  2. For access or export requests, use your approved export process; the admin screen records workflow state but does not provide an Export button.
  3. For delete requests, confirm the request has a resolvable subject, then use Mark fulfilled to run configured anonymization and erasure contributors.
  4. Keep the workflow evidence and confirm the fulfilled status updates.

An operator verifies and completes a data-subject request with audited actions.

  1. Open the Retention rules list.
  2. Each rule shows the data domain, record type, retention days, action, and whether it is active.
  3. Use Dry run to see the affected records before using Run now.
  4. Active rules are also handled by the scheduled retention job. Adjust a rule if its window or action no longer matches your policy.

An operator reviews automated data minimisation rules and their retention windows.

  1. Open Consent records.
  2. Review who granted consent, to which policy version, and when.
  3. Use this if a customer or regulator asks for proof.
  1. Open Privacy center > Consent policies.
  2. Create or edit the policy record with a key, version, title, and Cookie policy type, then set its effective and published dates as appropriate.
  3. The public preference centre records visitors’ choices for the built-in cookie categories. Category definitions and banner behaviour are application configuration, not an admin settings form.
  • Consent records and the cookie preference centre. Capture consent correctly before you need to prove it.
NeedEnable
Handle formal data requestsThe Privacy requests workflow
Show consent historyConsent records
  • Don’t action data requests without your verification and legal process agreed first. Privacy steps must follow policy.
RoleFirst useful screen
Privacy / support staffPrivacy center > Privacy requests
Site ownerConsent policies and Retention rules
What you seeWhat it meansWhat to do
A request can’t be fulfilledIt must be verified and in processingUse Mark verified first; for deletion, also confirm the request has a resolvable subject
I can’t prove a consentThe consent record wasn’t capturedCheck Consent records; ensure consent is recorded going forward
The cookie banner shows the wrong optionsCookie categories or banner behaviour need application configurationAsk your developer to update the privacy-centre configuration; policy records do not change the categories