> 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

Where to find Primer's SOC 2 report, GDPR and CCPA details and Trust Center, how Primer accesses your CRM, what the website pixel collects, and 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's compliance reports, subprocessors and security details are published in its Trust Center at [trust.sayprimer.com](https://trust.sayprimer.com/), which is kept current as certifications renew. Certifications are managed by Primer's security and legal team rather than set in the product, so check the Trust Center for what's current.

For a copy of the latest SOC 2 report, a signed **DPA** or **MSA**, or a specific **GDPR / CCPA / data-processing** question, contact <support@sayprimer.com>.

## CRM access is read-only

Primer [connects to your CRM read-only](https://support.sayprimer.com/primer/connections/integrations/connecting-a-crm.md): it reads records to build audiences and never writes to your CRM. Deleting the connection in Primer stops the sync and deletes the connection Primer stored.

## What the website pixel collects

The [website pixel](https://support.sayprimer.com/primer/connections/website-tracking/installing-the-pixel.md) collects, for visitors to your site:

* Pageviews and form submissions (password fields are never captured)
* Device metadata (browser, device type, screen, language)
* A visitor and session identifier stored in the browser
* HubSpot's visitor ID (its `hubspotutk` cookie), on sites that run HubSpot
* Segment's visitor, user and account IDs, and the email, name, phone, company and website your site gave Segment, on sites that run Segment
* Attribution data (referrer, UTM parameters, ad click IDs)
* On a site that runs Meta's pixel: the visitor details that pixel already holds (such as an email, phone or name your site gave it or it read from a form on your site, even one the visitor didn't submit), the event data your site sends it, and its browser and ad-click cookies

It doesn't track **bots** or **non-production sites** such as `localhost`, staging and preview domains, so those don't reach 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=<question>&goal=<user_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.
