> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/ai-assistants/data-and-privacy.md).

# AI assistants: data and privacy

What an AI assistant can see in your eMarketeer account, and where the data goes.

What an AI assistant can see in your eMarketeer account, and where the data goes.

## What the assistant can see

The assistant reads from the accounts you belong to. Every user on an account can read its data through the connector, whatever their role in eMarketeer. Changes need the Marketing User or Administrator role on that account.

## Where your data goes

When you ask a question, the data needed to answer it is sent to the AI provider you connected. That can include contact details and report figures. Your agreement with that provider covers how they handle it.

eMarketeer doesn't keep anything extra. Spreadsheet exports you ask for are deleted after one day.

## Personal data

You remain responsible for the personal data in your eMarketeer account. Before you share contact data with an AI assistant, check that your agreement with the provider covers processing personal data.

## Disconnect

You can disconnect at any time. See [Connect Claude to eMarketeer](https://support.emarketeer.com/integrations/ai-assistants/connect-claude.md#disconnect) or [Connect ChatGPT to eMarketeer](https://support.emarketeer.com/integrations/ai-assistants/connect-chatgpt.md#disconnect).


---

# 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.emarketeer.com/integrations/ai-assistants/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.
