Skip to content
MapleGatherMapleGather Help

Deny a deletion request with a reason

Use Reject to deny a deletion request and record the reason the member can see when deciding whether to appeal.

Who can do this: Admins allowed to view the case and make a data-request decision for that member. Viewing the queue alone does not grant permission to reject a deletion. If DSR queue is missing, ask an Org Owner about your access.

Before you start

Section titled “Before you start”
  • A reason is required. The member sees the reason you select as the basis for an appeal. Your organization may add or change the available reasons.
  • The optional audit note is for administrators; it is not shown to the member as the denial reason.
  • This action is for deletion requests only. Exports are automatic and status-only in the admin queue.

Steps

Section titled “Steps”
  1. Go to DSR queue (the Data requests page, at /admin/admin-security/privacy/dsr).
  2. Select Review on an open deletion request. On a finished request, View shows the audit but offers no new decision.
  3. Select Reject.
  4. Choose a live organization reason from Reason for denial. This is required.
  5. If needed, enter an optional note in Add a note for the audit trail.
  6. Select Confirm denial to submit the decision.

Only if that submission asks you to sign in again, follow these steps. If the request is Rejected, stop here.

  1. Complete the sign-in challenge. The earlier submission was refused.
  2. On return, reopen the request and check its latest status. The trip to sign-in may have cleared the form.
  3. If rejection is still available, choose a current Reason for denial again.
  4. Re-enter any optional audit note you want to keep.
  5. Select Confirm denial to submit a new decision. Completing the challenge alone does not reject the request.

Verify

Section titled “Verify”

You’ll know it worked when the deletion request’s status changes to Rejected. The member can see the selected reason on their own request list as the basis for appeal. Their data was not anonymized by this decision.

If something goes wrong

Section titled “If something goes wrong”
  • “We couldn’t load the denial reasons — try again.” — select Try again. If the list still fails or comes back empty, Confirm denial stays unavailable; the form does not substitute a fixed list.
  • Confirm denial stays unavailable — choose a reason from Reason for denial after it loads.
  • “This request was already resolved — refresh to see the latest status” — refresh the page before attempting another action.
  • A direct link or action gives 403 or 404 — a 403 may mean this member is outside your viewing or decision access; a 404 means the request was not found or belongs to another organization. Ask an Org Owner about your access if needed. Your own member-request access is separate from admin access.
  • The organization is read-only — authorized deletion decisions are still available. The review-policy setting and legal-hold controls remain paused.
Section titled “Related”