MCP Privacy Notice

1. Scope and Current Status

This notice describes how data can flow through the Rheos Model Context Protocol (MCP) server when an authorised AI-assistant client (such as Claude, ChatGPT, Cursor or another MCP-compatible client) calls Rheos tools on a user's behalf. It supplements the main Rheos Privacy Policy, which continues to apply to Rheos account, workspace, billing, AI and product data.

Controller: Rheos App Ltd, company number 17105158, 60 Farm Road, Beeston, Nottingham, England, NG9 5DA. Contact: archie@rheos.app.

2. What the MCP Server Does

The MCP server exposes scoped tools that can read or change data in an authorised Rheos organisation. Depending on the tool and granted scope, this can include:

• brand details (including the brand's contact email and phone number where you have added them), the brand document and its earlier versions, audiences, offerings, content pillars, visual style, source documents and website-source material;
• post text, drafts, schedules and attached assets, and generated or uploaded images and videos, including links to the stored files;
• the social accounts connected to a brand, with each account's name and connection status;
• customer-requested website scraping or source import;
• AI text or image generation;
• create, update, schedule or publish actions; and
• feedback reports that an assistant sends to the Rheos team when a tool fails or falls short (see Section 7).

The server does not preload an entire account into a client. A tool returns the information used for that request, subject to organisation and scope checks. A client with write or publish access can change workspace data or cause content to be published, so review both the client and the requested scope carefully before authorising it.

3. Authentication and Authorisation

Whichever method is used, removing an AI assistant from its own interface is not a substitute for revoking its Rheos API key or OAuth authorisation where the credential remains valid.

4. What Data an Authorised Client May Receive or Change

The data returned depends on the selected organisation, tool arguments and scopes. It may include customer content such as brand sources, identity documents, brand contact details, drafts, assets and platform connection details. A write or publish tool may create content, alter drafts, start AI generation, retrieve a customer-authorised website, or publish to a connected social platform.

The MCP server enforces organisation and scope checks and is not intended to expose raw payment-card details or another organisation's data. Grant the least access needed, review tool actions and generated content, and revoke a credential when the client no longer needs access.

5. The Request Chain and Third Parties

An MCP request can involve two distinct types of third party:

1. The client you chose. Once your selected AI assistant or MCP client receives Rheos data, that provider handles its copy under its own terms and privacy notice (for example Anthropic's or OpenAI's). Rheos does not control whether that provider retains data or uses it to improve or train its own systems — review the provider's settings and terms before authorising it.
2. Processors used by Rheos to perform a tool. A generation or import tool may cause Rheos to send the required data to a Rheos processor: Google AI Studio / Gemini and Anthropic Claude (through Google Cloud and Amazon Web Services) for AI text generation; Fal.ai or, on selected paths, Microsoft Azure OpenAI (GPT-Image-2) for image generation; Firecrawl for customer-requested website retrieval; Google Cloud / Firebase for core data and operations; Vercel for hosting; Auth0 for OAuth sign-in; and Sentry for diagnostics when errors occur.

The main Privacy Policy contains the full recipient and subprocessor list. A client you select is not a Rheos subprocessor merely because you ask it to call Rheos.

6. Google API Services User Data & Limited Use

Where an MCP tool is permitted to expose Google-derived customer data, it may return only the data needed for the customer-requested tool action and within the granted Rheos and Google permissions. Active Google access today is Google Drive read-only import and YouTube publishing (youtube.upload, youtube.readonly). Google Search Console, Google Analytics and Site Verification access is rolling out via the dashboard (see the main policy, Section 7) and is not currently exposed through MCP tools. No Gmail access exists.

A customer-selected MCP client that receives Google-derived data processes its copy under its own privacy terms, but Rheos continues to apply Google's restrictions to Rheos's own use and transfers.

7. Logging, Telemetry and Model Use

Rheos does not promise that MCP request or response payloads are never logged:

• MCP-triggered AI flows use Rheos's standard AI wrapper, which records usage and can store up to the first 500 characters of serialised input and the first 500 characters of serialised output in per-organisation usage records. Tool arguments or generated content can therefore appear in these snippets.
• Usage and operational records can include the tool or flow, organisation, timestamp, usage amount, status, latency and diagnostic context needed for usage accounting, rate limits, abuse prevention and service operation.
• Each MCP request is logged with the organisation, a one-way hash of the credential's identity, a request ID and the type of assistant (for example Claude or ChatGPT, read from the client's user agent).
• An assistant can send the Rheos team a feedback report when a tool fails or falls short. A report holds what the assistant writes (a summary, what was tried, which can include what you asked for, what it expected and what happened), plus the organisation, brand ID, assistant type, request ID and time. Rheos keeps these reports to find and fix problems; they are not shown to other users in your organisation.
• Sentry and platform logs can receive error and diagnostic context when something fails.
• As described in Section 3, Rheos stores API keys as one-way hashes. Keys stored in full before that change remain in our database only until they are revoked, and can no longer be used to connect.

Rheos does not use MCP tool-call payloads to train public AI models. Your chosen AI assistant may have its own training or improvement settings, which you should review with that provider.

8. Retention and Deletion

Customer content remains subject to the main Privacy Policy, including the 30-day account-deletion process. MCP API key and OAuth authorisation records, feedback reports, AI input/output snippets and usage records, diagnostic logs, deletion audit records, and backups are retained according to necessity, security, contractual and legal requirements rather than a fixed published period.

Revoking an API key or OAuth grant stops future authorised calls using that credential, but it does not automatically delete data that a third-party client already received. To address that copy, contact the client provider and use its deletion controls.

9. Security

Rheos applies organisation and scope checks to MCP requests, stores API keys as one-way hashes and masks them in list responses. Those measures do not remove the risks of giving a third-party client read, write or publish access. Keep keys private, grant minimum scopes, review publish actions, rotate or revoke credentials after any exposure, and remove access when no longer needed.

10. Your Rights and Choices

The rights in the main Privacy Policy apply to personal data processed through MCP, including access, rectification, erasure, restriction, portability, objection, withdrawal of consent where applicable, and the right to complain to the Information Commission, the UK data protection regulator (called the Information Commissioner's Office until 30 September 2026).

To stop a client from making future calls, revoke its Rheos API key in the dashboard's MCP settings, or revoke the OAuth authorisation where that method is used. Send privacy requests or complaints to archie@rheos.app.

11. Changes to This Notice

We will update this notice when access to the MCP server opens beyond the private beta, and when its authentication methods, client controls, scopes, retention settings, security design or tool surface change in a way that affects your data. We will update the effective date when it changes, and material changes will be notified in accordance with the main Privacy Policy.

12. Contact

For MCP-specific privacy questions or data requests: