# Privacy integrations

> Connect your Mintlify documentation site to privacy platforms like Osano and Transcend to manage cookie consent, compliance banners, and user preferences.

:::card{title="Osano" href="/guides/integrations-privacy-osano" horizontal="true"}
Manage cookie consent with [Osano](https://www.osano.com/).
:::

:::card{title="Transcend" href="/guides/integrations-privacy-transcend" icon="shield-check" horizontal="true"}
Manage cookie consent with [Transcend](https://transcend.io/).
:::

## Cookie consent and disabling telemetry

To check whether a user has already consented to cookies for General Data Protection Regulation (GDPR) compliance, specify a local storage key and value under `cookies`:

```json theme={null}
  "integrations": {
    "cookies": {
      "key": "LOCAL STORAGE KEY",
      "value": "LOCAL STORAGE VALUE"
    }
  }
```

If you set these values, your site checks local storage for the specified key and value to determine if a user consented to cookies. If a user has not consented to cookies, your site disables telemetry for that user.

If you'd like to disable telemetry for all users, add the following to your `docs.json` file:

```json theme={null}
  "integrations": {
    "telemetry": {
      "enabled": false
    }
  }
```

:::callout{intent="note"}
If you disable telemetry, you cannot collect feedback on your documentation pages, even if you enable feedback in your dashboard.
:::

## Related topics

- [Osano](/guides/integrations-privacy-osano)
- [Fathom](/guides/integrations-analytics-fathom)
- [Plausible](/guides/integrations-analytics-plausible)

## Related pages

- [Admin](./admin-index.md)
- [Agent](./agent-2-index.md)
- [Agent](./agent-index.md)
- [Agent-ready content](./agent-ready-content-index.md)
- [AI](./ai-index.md)
- [Analytics](./analytics-index.md)
- [API docs](./api-docs-index.md)
- [API reference](./api-reference-index.md)
- [Assistant](./assistant-2-index.md)
- [Assistant](./assistant-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.