# Get account deletion status

`GET /fapi/v1/me/deletion` · called from the environment's sign-in host

Returns the signed-in user's own pending account deletion, if there is one. `status` is `none` when the account is not being deleted and `scheduled` during the waiting period; then `due_at` is when the deletion becomes final and `cancellable` tells whether `DELETE /fapi/v1/me/deletion` can still cancel it. Requires the authenticated user's `__Host-idp_session` cookie. A first-party app on another origin can instead send its front API access token (`Authorization: DPoP <token>` with a DPoP proof; see [Front API access token](/docs/api/fapi/front-api-token)). Reading does not need a recent sign-in.

While an account is waiting for deletion, its session can only reach this resource and the user's own data exports (`/fapi/v1/me/exports`) among the `/fapi/v1/me` endpoints; the others answer `403 user_not_active`.

## Request

Headers:

| Header | Required | Description |
| --- | --- | --- |
| `Idp-Client` | yes | SDK identifier. |

## Response

`200 OK`:

```json
{"status": "scheduled", "due_at": "2026-11-10T09:30:00Z", "cancellable": true}
```

```json
{"status": "none", "cancellable": false}
```

## Errors

| Status | Code | When |
| --- | --- | --- |
| 401 | `unauthenticated` | No valid session cookie. |
| 404 | `not_found` | The user cannot be found. |
| 503 | `service_unavailable` | The user directory is temporarily unavailable; retry after `Retry-After`. |

## Example

```bash
curl https://example.keenauth.app/fapi/v1/me/deletion \
  -H "Idp-Client: my-app/1.0.0 (node/22.0.0)" \
  -b cookies.txt
```

## Personal data

This endpoint carries personal data: end-user profile. [Personal data in the KeenAuth APIs](/docs/policies/personal-data) describes what is stored, how long it is kept and how it is deleted. Do not send special categories of personal data (health, biometric data, religion, political opinions, sexual orientation) in any field.