> For the complete documentation index, see [llms.txt](https://docs.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icustomer.ai/security-and-compliance/gdpr-ccpa-dsar.md). # GDPR, CCPA and DSAR How iCustomer Platform supports GDPR and CCPA compliance, and how data subject requests are handled. The platform is built to operate inside privacy regulation, not around it. ## What that means in practice * **Opt-outs are honored.** Consent and suppression flags travel with records and are enforced before any activation reaches a destination. * **PII is protected at ingestion.** Hash, mask, encrypt, or exclude sensitive fields per your policy. See the [Security model](/security-and-compliance/security-model.md). * **Deletion and access requests are supported.** When a data subject exercises their rights, the corresponding records can be exported or removed across the platform. ## Data subject requests (DSARs) Route data subject requests through your own privacy process as the controller. As a processor, iCustomer supports fulfillment: locating the subject's records, exporting them, and deleting them on instruction. Contact your iCustomer administrator or reach us through the [Privacy Policy](https://www.icustomer.ai/privacy-policy) channels to initiate a request. ## Documentation Our sub-processor list, Data Processing Agreement, and data-handling policies are available on request from your iCustomer contact. Deletion requests propagate at the OneSource ID level, which is what keeps provenance clean across every source that contributed to a record. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.icustomer.ai/security-and-compliance/gdpr-ccpa-dsar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.