Affise MCP server › Data notice
This notice covers the Affise MCP server — the hosted endpoint at mcp.affise.com and the self-hosted npm package. It supplements the Affise privacy policy rather than replacing it: where the two overlap, this page is the more specific of the two, because the MCP server handles one thing the website never does — an API key you hand to it so an AI assistant can read your account.
Your Affise API base URL and API key. On the hosted endpoint you enter them once in the sign-in form; when you self-host you set them as environment variables and they never leave your machine.
The parameters of each question your assistant asks on your behalf: dates, filters, offer and partner identifiers, sub-ID values. These are derived from what you asked, so they can contain anything you put in the question.
Ordinary request metadata: your IP address, a timestamp, and a request identifier that is echoed back to you in the X-Request-ID response header.
No account is created. Your name, your email address and your contact details are not collected and not stored — the server never asks for them.
A session record, and nothing besides: a session identifier, an internal user identifier, your Affise base URL, your API key encrypted with AES-256-GCM, creation and last-use timestamps, and the role your key reported when you signed in. The key is decrypted for the duration of a single request and never written to a log.
On the hosted endpoint these records live in Redis. When you self-host, the API key is read from the environment and then removed from it, so a dependency loaded later cannot read it back out of the process.
Answers from the Affise API are cached in memory to keep repeat questions fast. The cache is never written to disk and does not survive a restart.
Your Affise data itself is not copied, warehoused or analysed. The server forwards a request, hands the answer to your assistant, and keeps nothing beyond the short cache below.
The table is exhaustive — there is no other store.
| Sign-in flow (browser session) | 15 minutes |
| Authorization code | 10 minutes |
| Cached answers | 1 to 30 minutes, depending on the tool |
| Session record, including the encrypted API key | As long as the access token is valid |
| Refresh token | 90 days |
Revoking access in your MCP client, or signing out, deletes the session record and the encrypted key with it. You do not have to wait for the expiry.
The Affise API. That is the destination: every request goes to your own Affise account, authenticated with your own key, and returns only what that key is allowed to see.
The AI provider you chose. This is the boundary worth understanding. Answers are handed to your assistant, so they become part of your conversation with whoever runs it — Anthropic, OpenAI, or another provider. What happens to that conversation is governed by your agreement with them, not by Affise. Business and enterprise plans from the major providers exclude API traffic from model training by default; consumer plans may not.
Nobody else. No analytics, no advertising, no telemetry, no third-party trackers, no data brokers. The endpoint makes outbound requests to exactly one host: the Affise base URL you configured.
Every one of the tools is read-only, so connecting an assistant cannot change or delete anything in your Affise account.
The key you supply sets the ceiling on what an assistant can read. An affiliate key reaches only that affiliate's own data; if you want to narrow what the assistant sees, supply a narrower key.
You can revoke access at any time from your MCP client, which deletes the stored session.
To ask what is held about you, or to have it deleted, write to [email protected]. Rights that apply across the Affise platform are described in the Affise privacy policy.
How credentials are handled, what is in scope, and how to report a vulnerability are described separately — including the findings we have already assessed. Reports go to [email protected] with SECURITY at the start of the subject line. Never include a live API key in a report.