> 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/legal/legal.md).

# Let’s Talk Legal

At eMarketeer, we value clarity and transparency. This page brings together all the key legal documents that define how we work with you — whether you’re a customer, partner, prospect, or simply exploring our platform.

Pick a document below, or use the navigation on the left.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Terms of Service (TOS)</strong></td><td>The agreement that governs your use of eMarketeer's services.</td><td><a href="/legal/terms-of-service.md">Terms of Service (TOS)</a></td></tr><tr><td><strong>Data Processing Agreement (SCC)</strong></td><td>How eMarketeer processes personal data on your behalf, including the Standard Contractual Clauses.</td><td><a href="/legal/scc.md">Data Processing Agreement (SCC)</a></td></tr><tr><td><strong>End User License Agreement (EULA)</strong></td><td>The license terms for using the eMarketeer software.</td><td><a href="/legal/end-user-license-agreement-eula.md">End User License Agreement (EULA)</a></td></tr><tr><td><strong>Acceptable Use Policy (AUP)</strong></td><td>The standards for using eMarketeer's products, services and websites.</td><td><a href="/legal/acceptable-use-policy.md">Acceptable Use Policy (AUP)</a></td></tr><tr><td><strong>Governance, Risk and Compliance</strong></td><td>Our governance structure, policies and procedures for privacy, security and transparency.</td><td><a href="/legal/governance-risk-and-compliance.md">Governance, Risk and Compliance</a></td></tr><tr><td><strong>Cloud Security Measures</strong></td><td>The security measures that protect data in our cloud environment.</td><td><a href="/legal/cloud-security-measures.md">Cloud Security Measures</a></td></tr><tr><td><strong>Information Security Policy</strong></td><td>How we protect information, from personnel security and access control to encryption and secure development.</td><td><a href="/legal/information-security-policy.md">Information Security Policy</a></td></tr><tr><td><strong>Cookie Policy</strong></td><td>How we use cookies on our website and how you can turn them off.</td><td><a href="/legal/cookie-policy.md">Cookie Policy</a></td></tr><tr><td><strong>Privacy Policy</strong></td><td>How we process and protect personal data under the GDPR.</td><td><a href="/legal/privacy-policy.md">Privacy Policy</a></td></tr><tr><td><strong>eMarketeer's Statement on the Schrems II Ruling</strong></td><td>Our position on the Schrems II ruling and data stored with US-based providers.</td><td><a href="/legal/emarketeers-statement-on-the-schreem-ii-ruling.md">eMarketeer's Statement on the Schrems II Ruling</a></td></tr></tbody></table>

While some documents may be available in multiple languages, the English version is the one that legally governs our relationship. Translations are provided for convenience and do not override the original.


---

# 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/legal/legal.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.