> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/account-and-security/data-and-privacy.md). # Data and privacy Primer's compliance standards (SOC 2 Type II, GDPR, CCPA) and Trust Center, how Primer accesses your data, what the website pixel collects, and where to find the privacy policy. ## Privacy policy and terms * Privacy policy: [sayprimer.com/privacy-policy](https://www.sayprimer.com/privacy-policy) * Terms of service: [sayprimer.com/terms-of-service](https://www.sayprimer.com/terms-of-service) ## Compliance and the Trust Center Primer is **SOC 2 Type II** attested and **GDPR** and **CCPA** compliant. Current compliance reports, subprocessors, and security details are published in Primer's Trust Center at [trust.sayprimer.com](https://trust.sayprimer.com/) — the authoritative source, kept up to date as certifications renew. You can also request a copy of the latest SOC 2 report from . > Compliance status and certification dates are managed by Primer's security/legal team, not set in the product, so specifics live in the [Trust Center](https://trust.sayprimer.com/) rather than here. For a signed **DPA** or **MSA**, or a specific **GDPR / CCPA / data-processing** question, contact — these are handled by Primer's security/legal team, not configured in the app. ## CRM access is read-only Primer connects to your CRM **read-only** — it reads records to build audiences and never writes, edits, or deletes anything in your CRM. See [Connecting a CRM](/primer/connections/integrations/connecting-a-crm.md). Deleting a connection in Primer disables the sync and removes Primer's access. ## What the website pixel collects The [website pixel](/primer/connections/website-tracking/installing-the-pixel.md) collects, for visitors to your site: * Pageviews and form-field submissions * Device metadata (browser, device type, screen, language) * A visitor/session identifier stored in the browser * Attribution data (referrer, UTM parameters, ad click IDs) The pixel automatically **skips bots and non-production hosts** (like `localhost` and staging domains), so those don't pollute your data. --- # 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://support.sayprimer.com/primer/account-and-security/data-and-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 `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.