> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/forms/privacy.md). # Tracker consent and capture exclusions Configure capture to match your site's consent and data collection choices. ## Control when the tracker loads If your site requires consent before tracking, have your site's consent manager load the Distro snippet only after the appropriate choice. The tracker otherwise allows tracking by default when Global Privacy Control does not signal a denial. After loading, your site can set the tracker choice: ```javascript window.distro.tracker.consent({ analytics: false, marketing: false }); ``` Setting either category to true grants the tracker's combined consent state. These are not independent analytics and marketing gates. With Global Privacy Control, the initial state is denied until your site supplies a choice. ## Exclude sensitive capture Add `data-distro-ignore` to an HTML form or field to exclude it from supported generic capture. Password, file and hidden fields and recognized sensitive field-name patterns are skipped by that capture path. Configure excluded paths where offered. Review custom field names deliberately; automatic patterns are not a substitute for choosing what your form should send. ## Check behavior Test denied and granted choices in a fresh browser session. Verify network requests and Distro activity for the intended pages. Use [Browser storage](/forms/storage.md) to understand persistent visitor identifiers and attribution. Changing consent behavior should be checked alongside your site's own consent banner and privacy information. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/forms/privacy.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 `build a script that syncs our docs to a CMS` 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.