Data use and governance
Who can connect
Anyone with an Awin login can connect their own assistant where Awin MCP is available.
Each person connects with their own Awin login. Do not share one login between several people or assistants.
Awin MCP doesn’t change your permissions
Awin MCP uses your existing Awin login and role. It doesn’t grant access to any account, report or action you don’t already have in the Awin platform. When you are removed from an account in Awin, that account is also no longer available to your assistant.
Where your data goes
When you ask a question, Awin sends the answer (for example, your performance figures) to the assistant you connected. From there it is handled by that assistant’s provider under your agreement with them, for example Anthropic for Claude or OpenAI for ChatGPT.
Before connecting, check that using your assistant with Awin data fits your organisation’s policies, and review your assistant’s data and privacy settings.
What Awin records
Awin keeps a log of MCP requests (who asked, which tool, when, and whether it worked) to run and secure the service. Awin doesn’t receive or store the conversations you have with your assistant.
Stopping access
You can remove the Awin connector in your assistant at any time.
Awin may suspend Awin MCP access to protect accounts or the service.
Sign-in and security
Awin MCP uses your Awin login. You sign in once per assistant in your browser, and the assistant receives its own secure pass. You never type your password into the chat and you never paste an API token.
What happens when you connect
You add
https://mcp.awin.comas a connector in your assistant.The assistant opens the Awin sign-in page in your browser.
You sign in with your Awin email and password, as you do for the Awin platform. If asked, approve access.
You return to the assistant. It can now call Awin on your behalf.
The assistant stays connected, so you don’t need to sign in again for every question. If your session ends, the assistant will ask you to sign in again.
Is API token needed?
No. Awin MCP doesn’t use Awin API tokens. If you already use an API token for other integrations, keep it private and don’t paste it into your assistant. If a setup screen asks for a client secret or a token, stop and check you are following the correct set-up process for your assistant.
What the assistant can see
Only what you can already see. The assistant uses your Awin login, so it sees the same accounts and the same data as you in the platform.
Your role applies. Publisher users don’t get advertiser-only reports, or the other way around. Agency users see only the accounts they already manage.
Mostly read-only. Every tool reads data except one: creating publisher tracking links.
Keeping your access safe
Only connect assistants you trust, and only on devices you control.
Each assistant has its own pass. Disconnecting one doesn’t affect the others.
Remove connectors you no longer use. See the Disconnect section in each connector guide.
Changed jobs or lost a device? Remove the connector in each assistant, and change your Awin password as usual.
Your assistant provider’s terms apply to what you share in the chat.