503 Erasure is not configured

The server cannot write a tamper-resistant suppression tombstone, so it refuses to erase rather than erase weakly.

Retry only after changing the request

What causes it

• `ERASURE_EMAIL_HASH_SECRET` is unset or shorter than 32 characters on the server.

How to fix it

• This is a server configuration issue, not a client one. Contact your administrator: the fix is setting ERASURE_EMAIL_HASH_SECRET, after which the identical request succeeds.
• Erasure is irreversible, so a weak tombstone could never be upgraded afterwards and the opt-out would stay recoverable by dictionary attack. That is why the operation fails closed rather than proceeding.

Example response

HTTP/1.1 503
Content-Type: application/problem+json

{
  "type": "https://sealdeal.ai/errors/erasure-unavailable",
  "title": "Erasure is not configured",
  "status": 503,
  "detail": "..."
}

`type` is stable and safe to branch on in code. `detail` is specific to your request and is the field to read for the particulars; its wording may change.