Request Statuses Explained

Every data subject request — a request from an individual to exercise their rights over the personal data you hold about them — carries a status that tells you whether it's waiting on the data subject, on your connected systems, or on you. You'll find it in the Status column on the Requests page, and you can filter your queue by it.

Statuses at a glance

Before processing starts

Unverified

A request submitted through your Privacy Center arrives as Unverified. MineOS emails the data subject a link to confirm their identity, and nothing is queried, copied, or deleted until they use it. Both the GDPR and the CCPA/CPRA expect you to establish that a requester is who they claim to be before acting on their data, so this status protects you as much as it protects them.

Once the data subject verifies, the request moves forward on its own. See Verification for how to configure this step.

Edit

Requests that reach you through email forwarding arrive as Edit. A forwarded email rarely contains everything MineOS needs — which privacy right the person is exercising, which brand the request belongs to, and who they are. Open the request, fill in the missing details, and it moves into processing.

Pending

Pending means Autopilot has taken the request but hasn't started work on it yet. It's sitting in the waiting period you set for that privacy right, counted from the moment the data subject verified — a window that gives them a chance to withdraw before anything is acted on.

You don't have to wait it out. You can begin processing the request yourself, or cancel the Autopilot run and handle it manually. See Configuring Autopilot Waiting Period.

While the request is being worked

Process

Process means the request's actions are underway across your connected systems — some running automatically, some waiting on a teammate to confirm they've done their part, depending on how each source is set up in DSR handling type.

A request stays in Process until every task resolves. Tasks that run into a problem appear as Needs Action and flag the request as Requires attention in your queue, so it won't quietly stall. See Completing a Request.

Reply

Reply means the work is done and the request is waiting on you to respond to the data subject — sending a copy report, confirming a deletion, or explaining a rejection. Sending that response closes the request. If something turns out to be unfinished, you can move the request back to Process.

After the request is closed

Closed

Closed means the request has been resolved and its outcome recorded. The regulatory clock stops here. If new information arrives, you can reopen it and pick up where you left off.

Redacting

A closed request shows Redacting once it's queued to have the data subject's personal data stripped from the request record — either automatically after your retention period, or because you chose Redact this request. Reopening a request at this point cancels the pending redaction.

Redacted

Redacted means the personal data is gone from the request record while the audit trail of what was done remains, so you can still demonstrate compliance. This is the end of the line: a redacted request can't be reopened. See Redacting Closed Requests Automatically.

Closed is a status; the outcome is separate

Every closed request also carries a reason that records how it ended:

• Completed — the request was fulfilled.
• Rejected — the request was declined, and the data subject was told why.
• Canceled — the request is no longer to be fulfilled, for example because the data subject withdrew it. See Canceling a Request.
  Two requests can both show Closed and have ended very differently, so check the reason when you're reviewing your queue or reporting on it.

What isn't a status

Three things sit next to status in the Requests page filters and are easy to mistake for one:

• Requires attention and the unread filters live under For review. They flag requests that need a look, whatever status they're in.
• Overdue is a due-date filter, tied to your response deadline rather than to where the request sits.
• Autopilot is an assignment, not a status. An Autopilot-run request still moves through Pending, Process, Reply, and Closed like any other.