GDPR: export, erasure & retention

GDPR requests have legal deadlines. These endpoints turn "a week of database archaeology" into minutes.

Right of access — export

curl "https://api.wezend.com/v1/gdpr/export?contact_id=c_123" -H "X-API-Key: $WEZEND_API_KEY"

Returns everything the platform holds on the contact as structured JSON: profile fields, consent history, events, messages (content and delivery metadata), list/segment memberships, form submissions and scores. Hand it to the data subject as-is or reformat it — the completeness is the platform's job, and it covers every module, including ones added later.

Right to erasure — anonymise

curl -X POST https://api.wezend.com/v1/gdpr/anonymise \
  -H "X-API-Key: $WEZEND_API_KEY" -H "Content-Type: application/json" \
  -d '{ "contact_id": "c_123" }'

Anonymisation (rather than row deletion) is deliberate: identifiers and free-text content are irreversibly scrubbed across all modules, while anonymous statistical rows survive so your historical campaign metrics don't silently change. The email/phone also lands on an internal blocklist so a later import can't resurrect the profile.

Retention policies

Under Settings → Data retention you set how long each data class lives — e.g. events 24 months, message bodies 12 months, inactive profiles 36 months. A scheduled job enforces the policy continuously. This is GDPR's storage-limitation principle turned into configuration instead of quarterly cleanup projects.

Audit log

Every export, anonymisation and retention run is recorded (GET /v1/gdpr/audit-log) — who requested it, when, and what was touched. When the regulator asks, the paper trail already exists.

For deleting an entire customer account, see your account manager or the Super Admin flow (DELETE /v1/gdpr/account/:customerId).