GDPR
The GDPR page sets what happens to customer data in external services when a profile is erased at the customer's request or the whole project is deleted. Open it from Settings → GDPR in the menu. The settings can be changed by the Owner and Admin roles.

Deletion in external services
The list shows every connected audience export: ad accounts (Meta, Google Ads, Yandex Audiences, VK Ads), webhook and S3; see Audience exports. Each service has its own checkbox. All of them are off by default: data in external services is left untouched.
A service that is turned on:
- Removes erased profiles. When a profile is deleted with Erase permanently on its card (see Profiles), it leaves the service's audiences. For this the profile's identifiers are kept before the deletion, for no longer than 30 days, and the service's exports run right away. A webhook receives the member removal; in S3 the profile goes to the removed list of the next file.
- Deletes audiences when the project is deleted. Audiences created by exports in ad accounts are deleted from the accounts. Audiences you chose yourself in the export settings stay. If a deletion fails, the project deletion certificate names those audiences. In a webhook or S3 — your own systems — nothing is deleted when the project is deleted.
Click Save. Changes are recorded in the audit log.
Good to know
- VK Ads accepts changes of 25 contacts or more: an erased profile leaves the list together with other changes.
- If the export is paused or the removal does not go through within 30 days, the profile stays in the ad account — remove it there manually.
- If you turn a service on after a profile was erased, that profile can no longer be removed from the audience: its identifiers are gone.
- CRMs are not in the list: CRM contacts are your own records, and their deletion is set up in the CRM itself.