--- title: "MCP connector privacy policy" description: "The privacy policy of the Talkspirit MCP connector: who is responsible, what an AI assistant connected to Talkspirit can reach, what leaves Talkspirit and to whom, what Talkspirit stores and for how long, and your rights." category: integrations section: api-and-webhooks tags: [ai] type: Reference lastUpdated: 2026-11-03 locale: en canonical: https://support.talkspirit.com/en/integrations/mcp-connector-privacy-policy --- # MCP connector privacy policy *Version 1.5.3.* *Effective date: 3 November 2026.* This policy covers one data flow: a person connects an AI assistant (Claude, ChatGPT or another Model Context Protocol client) to their Talkspirit account through the MCP connector at `https://mcp.talkspirit.com/mcp`, hosted in France. Organisations on Talkspirit's Swiss hosting connect through `https://mcp.ch.talkspirit.com/mcp`, which runs in Switzerland; for its details, write to `privacy@talkspirit.com`. --- ## In short - **The connector only reaches what the connected person can already see in Talkspirit.** It grants no new access. - **What it returns goes to the AI assistant the person chose**, under that provider's own terms. - **Talkspirit logs technical data about each call** (who, which tool, outcome, timing), not the content read or written. - **Administrators can set the connector to read-only or disable it**, and revoke members' keys. - **Questions or requests:** `privacy@talkspirit.com`. --- ## Who is responsible - **Talkspirit SAS**, Paris, France, publishes the connector. Contact: `privacy@talkspirit.com`, the data protection (DPO) contact named in the Data Processing Agreement (DPA). - **For your organisation's content**, your organisation is the controller and Talkspirit SAS its processor, under the DPA every customer has. Your organisation, as controller, decides whether its members may use the connector (the "MCP access" setting, enabled by default). Talkspirit has no agreement with the AI provider on your organisation's behalf: the provider is a recipient your member chooses, within your organisation's rules, not a Talkspirit sub-processor. - **For the connector's technical, access and security logs**, Talkspirit SAS is the controller. Legal basis: its legitimate interest in running and securing the service (Art. 6(1)(f) GDPR). --- ## Who decides what an assistant can do - **Each person connects individually**, by signing in or with a personal key created under **My account › MCP keys** (read-only by default). There is no shared key. - **Connecting is optional.** - **Administrators set "MCP access" for the organisation**: *Enabled* (default), *Read-only* (every write refused and hidden) or *Disabled* (every request refused, no key can be created). It applies to everyone, administrators included, from their next request. - **Administrators can list and revoke members' personal keys.** - **The organisation's sign-in rules apply**: a sign-in connection is refused when the app would refuse the same person (forced or disabled sign-in provider, suspended or removed member); a personal key is refused once its owner is suspended or removed. - **Switching off the AI assistant** also switches off the connector's knowledge search. --- ## What the connector processes **What it receives.** Only what the assistant puts into each request, such as a search or the text of a comment to create, and any file it uploads to attach to a task, goal, metric, proposal, agenda item, checklist or document. It does not ask for the conversation and has no access to the assistant's memory, chat history or files. **What it can return**, within what the connected person can see: - **Organisation structure**: circles, roles, role assignments and time allocations, members' display names and identifiers. - **Work items**: projects, tasks, checklists, goals, key results, metrics, with their attached files and links. - **Governance and meetings**: tensions, proposals, documents and working agreements, meetings and their participants, agendas, reports, and meeting transcripts (the spoken text). - **Free text**: comments, posts, and passages found by knowledge search. - **Files** attached to a task: name, type, size and, only if asked for, a temporary download link that works without signing in (one hour by default). **Contact data is not returned.** Other members appear by display name only; the connected person's own sign-in name is shown to them. Email addresses, phone numbers, birth dates and last-connection times are not returned; an automated test fails the build if one is added. Text typed into a comment or description is returned as written, with any personal data in it. **What it can write**, with write access: create and update tasks, goals, comments and other items, and upload a file to attach to a task, goal, metric, proposal, agenda item, checklist or document, always as the connected person and under their name; nothing marks it as made by an assistant. It can remove an assignee from a task or a key result, a label from a task, a link from an agenda item or a checklist, and a file or link attached to a task, goal, metric or proposal (the file itself is kept), and it can delete a comment written by the connected person themselves; it deletes no task, board, goal, key result or meeting, and no comment written by someone else. What it writes is ordinary content, kept and deleted like any other. **No automated decisions about people.** The connector takes no decision with legal or similarly significant effects on a person (Art. 22 GDPR). --- ## Why it is processed - **To answer the assistant's request**: read, search or write content. - **To enforce access**: identity, permissions and organisation settings, on every call. - **To run and secure the service**: logs and metrics detect faults and support security investigations. --- ## Who receives it - **The AI assistant the person connected** receives the result of every call; Talkspirit sends it nothing on its own initiative. That provider may process data outside the European Economic Area, under its own terms and any agreement the organisation has with it. - **No AI provider on Talkspirit's side**: the connector calls none; knowledge search computes its embeddings on Talkspirit's own servers. - **Hosting**: the connector runs at Cloud Temple, a French SecNumCloud-qualified provider, in France. Its logs, metrics and traces are processed on Talkspirit's monitoring servers at OVHcloud, in France; the logs and the log archive are stored at Cloud Temple, in France. Talkspirit itself does not transfer connector data outside the EEA. - **No one else.** No analytics or advertising service receives connector data. --- ## What Talkspirit stores, and for how long | What | Content | Kept for | |---|---|---| | Call log | Person and organisation identifiers, tool, sign-in method, outcome, duration, the kind of item and operation (for example "task, create") and the number of items. No free text from the request and no content returned is logged. On a failure, a short error message (up to 200 characters) is kept to diagnose it. Refusals are logged with their reason. | 90 days in the log store. On the French platform, a copy is also written to a security archive, where it is kept for one year from the day it is written, then deleted automatically; it is kept for security investigations | | Access logs | Your IP address, time, address requested and response status, for every request reaching Talkspirit | 90 days in the log store; on the French platform, also in the security archive described above | | Metrics | Tool, sign-in method and outcome, with no person or organisation identifier | Up to 30 days | | Traces | Timing of each call and its organisation identifier | 72 hours | | Strategic analysis reports | From strategic analyses run through the connector before it stopped offering them: verdict, summary and report text, and the goals, projects, gaps and organisation snapshot the analysis used, per organisation and requesting person | As long as the organisation's account, then deleted under the DPA's end-of-contract terms | | Indexed knowledge | Passages of the organisation's content, for knowledge search | Set per organisation; defaults: five years for proposals, one year for meeting material, none for goals and documents. Expired content is deleted nightly. | | Personal keys | A hash of the key (never the key itself), its owner, name, prefix, permissions, creation, expiry and last-use dates, and for a revoked key who revoked it and when | Erased when its owner deletes it. A key an administrator revokes is kept, unusable, as the audit trail of the revocation, for as long as the organisation's account | | Sign-in sessions | No access or refresh token. Talkspirit's sign-in service keeps a session record so the assistant can stay connected | Lapses after a period without use set by Talkspirit's sign-in service | Talkspirit's other services log the connector's requests as they do when you use the app. Deleted data can remain in Talkspirit's encrypted backups for as long as those backups are kept; the DPA security annex describes them. At contract end, the DPA's deletion terms apply. --- ## When a connection ends - **A personal key** is refused on its next request once it is deleted or revoked, or once the administrator sets "MCP access" to *Disabled*. - **A sign-in connection**: a suspended or removed member is refused once Talkspirit's access check sees the change, at most 90 seconds later. Disconnecting in the AI assistant stops the renewal of access; a token already issued may work until it expires. The session lapses after a period without use; to end it sooner, ask your administrator or write to `privacy@talkspirit.com`. - **Content already delivered** stays with the AI provider, under its terms. --- ## Security Traffic is encrypted (HTTPS), every call runs with the app's permission checks, and organisations are kept separate. The DPA's security annex describes the measures. --- ## Your rights Under the GDPR you can access, correct or delete your personal data, restrict or object to its processing, and receive it in a portable format. - **For your organisation's content**, send your request to your organisation (the controller), which answers it with Talkspirit's help as its processor. - **For anything else on this page**, write to `privacy@talkspirit.com`. - **You can stop at any time**: disconnect the connector in your assistant, or delete your key. - **You may lodge a complaint** with a supervisory authority, in France the CNIL (www.cnil.fr), or the authority of the country where you live or work. --- ## Changes to this policy Talkspirit updates this page and its effective date when the connector's data handling changes. --- ## Next steps - [The Talkspirit MCP server](/en/integrations/what-the-mcp-server-can-do): how to connect an AI assistant, and what the connector can read and write - Data Processing Agreement (DPA): the processing Talkspirit performs for your organisation - Data Protection Impact Assessment (DPIA): the risk assessment for Talkspirit's AI features; it covers what Talkspirit and Mistral AI process, not what the AI assistant you connect does with the results - Sub-processor due diligence report: the assessment of Mistral AI - AI system registry: the EU AI Act registry entry