Request deletion without losing the audit trail.

How the workflow works

1. You enter the exact confirmation phrase and acknowledge retention obligations.
2. A versioned, customer-owned request is recorded with an audit event.
3. Optional marketing consent is withdrawn and registered notification endpoints are revoked.
4. Required tax, transaction, fraud, dispute or legal-hold records are assessed.
5. Deletion is marked complete only after worker evidence confirms required processor actions.

What may be retained

A request does not override statutory retention, payment records, invoice integrity, active disputes, fraud prevention or a valid legal hold. Retained data is restricted to the purpose and period that requires it. The status screen distinguishes review, retention and processor state.

Cancellation and external processors

You can cancel while the request remains in the requested state. Cancellation does not automatically re-enable marketing permissions or restore device endpoints. Firebase authentication, payment, communications and delivery processors are not reported as erased until the deletion worker records evidence.