---
title: Compliance overview
slug: data-platform/api/compliance-overview
docTags: 
createdAt: 2026-06-24T13:31:23.000Z
---

For deletion requests, ODP does the following for the next 30 days after the deletion request:

- ODP finds all identifiers associated with the profile requested for deletion and does not rediscover customers using those identifiers.
- You cannot move or associate identifiers that are linked to a profile requested for deletion to other profiles. Also, you can not add new identifiers to the profile.
- ODP ignores and drops events tied solely to the identifiers of the profile under deletion.
- If an [event](docId\:w0DeSMy7YSyAm7PnwzGqq) includes identifiers from both a profile under deletion and a high-confidence identifier from an active profile, ODP processes the event using the high-confidence identifier and attributes it only to the active profile. ODP ignores identifiers from the profile under deletion.
- If an [event](docId\:w0DeSMy7YSyAm7PnwzGqq) includes identifiers from a profile under deletion along with a new low-confidence identifier, the event is dropped. The low-confidence identifier is neither linked to the deleted profile nor used to create a new one.

For CCPA opt-out requests (opting out of the sale of data), ODP finds the profile associated with the given identifier and indicates the CCPA opt-out status. This is acted upon in marketing situations and can be accessed as part of a qualification (segment) or profile search.

:::hint{type="danger"}
**Warning**
Use the Compliance endpoints for compliance-based changes only.

If you are trying to remove users from a list or a specific channel, or globally revoke marketing consent, do *not* use the Compliance endpoints.

- Use the [Consent API](docId\:tOt0M67TcqxHrHDIRQaT3) for managing typical marketing-based opt outs.
- Use the [Lists API](docId\:jicnnWqhLxjrLLiGlbpO9) to manage list subscriptions.
:::