> ## Documentation Index
> Fetch the complete documentation index at: /llms.txt
> Use this file to discover all available pages before exploring further.

# Data privacy

> Erase a customer's personal data when they ask, and handle personal data responsibly.

## Erasing a customer

When a customer asks you to delete their data, call [`DELETE /customers/{customerId}`](/api-reference/customers/erase-a-customer):

```bash
curl -X DELETE https://api.usecerium.com/v1/customers/prt_8271 \
  -H "Authorization: Bearer $CERIUM_API_KEY"
```

This erases the customer's:

* name, email and phone
* devices
* tags and notes
* the **content** of their messages

The conversations themselves stay, without their content, so your history and reports keep their counts.

> [!WARNING]
>
> Erasing **cannot be undone**. Check the id twice. If you may need the data later, export it first.

Requires the `customers:write` scope. Consider using a dedicated key for the job that handles deletion requests.

## What to send, and what not to

* Send only the personal data you need support to have. A name and email are required; a phone number is optional.
* **Do not put secrets in message bodies**: no passwords, full card numbers, or access tokens.
* Do not put sensitive data in `externalId`, tags or attributes. They are visible to your support team.
* Attachment links should point to one file and should not grant access to anything else.

## Your keys

API keys are credentials. See [Keeping keys safe](/authentication.md#keeping-keys-safe).
