> For the complete documentation index, see [llms.txt](https://docs.aloop.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.aloop.icustomer.ai/ireveal/consent.md). # Consent How iReveal respects consent: your banner decides, capture is first-party, and opt-outs travel. iReveal is consent-aware by design, and the design is simple: **your consent banner decides; iReveal obeys.** ## The tag loads on consent The iReveal tag is gated by your consent management platform like any analytics tag: wire it to load only after the visitor consents, using your CMP's consent-granted callback. No banner interaction, no capture. The wiring pattern is the same as the platform pixel's; see [Events and pixels](/integrations/events-and-pixels.md). ## First-party, in your environment Capture is server-side and first-party, under your domain and your policies, and with warehouse deployment it runs inside your own environment, so visitor data does not leave your control to be resolved. ## Opt-outs travel A visitor who opts out stays opted out downstream: suppression and consent flags ride with the record into scoring, audiences, and any activation. Deletion and access requests follow the platform's DSAR support; see [GDPR, CCPA and DSAR](/security-and-compliance/gdpr-ccpa-dsar.md). {% hint style="info" %} Regional rules differ, and your legal team owns the consent policy. iReveal's job is to make the compliant configuration the easy one: one tag, gated by your banner, honored everywhere downstream. {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aloop.icustomer.ai/ireveal/consent.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.