---
title: "Process GDPR right to erasure for an email address"
method: POST
path: "/v2/email/gdpr/erasure"
tags: ["email-gdpr-v2"]
---

# Process GDPR right to erasure for an email address

`POST /v2/email/gdpr/erasure`

## Request

- Base URL: `https://api.tracklysms.com/api`
- URL: `https://api.tracklysms.com/api/v2/email/gdpr/erasure`
- Auth: API key in header `X-Api-Key`

Performs 6 actions:
1. Delete from ListContact (email list memberships)
2. Delete from ContactEngagement (engagement history)
3. Delete from SendTimeProfile (send-time optimization data)
4. Redact EmailMessage to_email field (replace with hash)
5. Retain hash in suppression list (prevent future sends)
6. Retain ConsentRecord with erasure timestamp
7. Log in DataProcessingLog
8. Propagate to sub-processors (via Kafka event)

## Request body

- EmailGDPRErasureRequest
  - `email` string, required: Email address to erase

## Response `200`

Erasure processed

- EmailGDPRErasureResponse
  - `actions` object: Summary of erasure actions taken
  - `emailHash` string: SHA-256 hash of the erased email
  - `processedAt` string, date-time: Timestamp of processing
  - `success` boolean: Whether erasure was processed

## Other responses

- `400`: Validation error
- `401`: Authentication error
- `429`: Rate limit exceeded

---

[API](https://skmtc.dev/tracklysms/apis/trackly-sms-api.md) · [All operations](https://skmtc.dev/tracklysms/apis/trackly-sms-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tracklysms/apis/trackly-sms-api/revisions/ac1ad22cb2a9?raw)