Privacy notice for MCP integrations

This notice explains how personal data is handled when a fynk account is connected to an external AI service, such as ChatGPT or Claude, through fynk’s MCP server. It has only information character and does not prejudice or affect our terms and conditions or the data processing agreement (DPA).

1. Scope and roles

The Model Context Protocol (MCP) is an open standard that lets AI services use tools in other software. fynk’s MCP server at app.fynk.com/mcp provides such tools. When a fynk user connects an AI service to it, the AI service can read information in that user’s fynk account and carry out actions there in the user’s name.

This notice covers that connection and the data exchanged through it. It does not cover how the AI service itself processes data. That is up to the provider of the AI service (see section 4).

In terms of GDPR the customer is the controller, fynk is the processor. The customer, meaning the organization that holds the fynk account, decides whether and how fynk and the integration are used, for which purposes and who receives the data. It is the controller for the personal data in its account, including the content of documents and templates and information about parties, signatories and users. fynk GmbH processes this data on the customer’s behalf and on its instructions as a processor, under the DPA concluded with the customer.

Connection data, request logs and error reports. fynk also processes the authorization records, request logs and error reports that the integration creates as a processor under the DPA, as part of providing the service to the customer.

2. Data exchanged

What is exchanged depends on the tools the AI service calls, the task you give it and your permissions in fynk. Each connection is linked to one fynk account, the one that was active when you approved it, and only works within your own role and document permissions in that account. The AI service cannot see or do anything in fynk that you could not see or do yourself.

Data the AI service sends to fynk

The AI service sends fynk tool requests: the name of a tool and the details needed to run it. Depending on the task, these details can include:

search terms and filters
names and settings of documents, templates, tags, teams and metadata fields, values of fields and metadata, and template text
information about parties (company name, address) and signatories (name, email address, mobile phone number, job title)
the message signatories receive when signing starts
PDF files from which fynk creates documents

Each request also carries technical data: your access token, the IP address the request comes from and the user agent of the AI service.

fynk does not receive your conversation with the AI service. It only receives what the AI service puts into a tool request, which can include information taken from that conversation.

Data fynk returns to the AI service

Depending on the tool and your permissions, fynk returns:

information about documents: name, stage, type, dates, tags, teams, field and metadata values, signing settings, approval status and, where available, a summary created by fynk’s AI analysis
the PDF of a document, including signed documents, through a download link that expires after ten minutes
templates, including their full text
parties (company name, address) and signatories (name, email address, signing order). Signatories’ phone numbers are not returned.
names of the people who have access to a document
names and email addresses of the users in your fynk account and of team members
your own profile (email address, role, teams) and the account settings
the account’s configuration: tags, teams, document types, metadata fields, saved parties, playbooks, automations and imports

3. Purposes

The customer sets the purposes for which personal data is processed through the integration. They depend on its specific use case, for example drafting contracts and sending them for signature, keeping track of deadlines or organizing its contract portfolio. fynk processes the data as a processor, on the customer’s behalf and on its documented instructions, which are set out in the service agreement and the DPA.

To provide the integration within that framework, fynk my carry out the following processing on behalf of the customer:

Authenticating the connection: checking that you approved it, that it is still valid and that the integration is enabled for your account.
Answering requests: returning the information the AI service asks for.
Carrying out requested actions: for example creating documents and templates, updating fields, parties and signatories, changing tags and teams, moving documents to another stage, archiving documents and starting signing, as far as your permissions allow. When signing starts, fynk emails the signatories, just as when you start signing in fynk directly.
Processing uploaded PDFs: recognizing the text and analyzing the document to fill in its details, with the same AI analysis fynk applies to PDFs uploaded in the app, where it is available for the account.
Recording changes: changes to documents appear in the document’s audit trail under your name, just as changes you make in fynk directly.
Running and securing the service: logging requests and reporting errors, so fynk can investigate incidents and fix problems.

4. Recipients

The customer controls who receives the data. Through its admins and users, it decides whether the integration is enabled, which AI services are connected, who has access to the account and its documents, and which signatories receive documents for signing. Within the account, admins can see which users have connected which AI services and can be notified when a connection is added or removed.

Within fynk

The MCP server is part of the fynk application and runs on the same infrastructure. fynk processes the data as the customer’s processor under the DPA and uses the service providers in our list of subprocessors, among them the services for hosting, AI analysis and error reporting.

The external AI service

Everything fynk returns through the integration is made available to the AI service that was connected, for example OpenAI for ChatGPT or Anthropic for Claude.

The customer’s users choose and connect the AI service, within the settings the customer’s admins control. fynk does not engage it to process data for fynk.

Once data reaches the AI service, how it is processed there is governed by your agreement with that provider: its terms, its privacy notice and the settings of your account with it. These determine, for example, where the data is processed (which may be outside the European Economic Area), how long it is kept and whether the provider may use it to improve its models. fynk’s commitments on hosting, retention and use of data apply to processing within fynk only. They do not extend to the provider of the AI service and cannot be held responsible of the actions of the thrid-party AI service.

For ChatGPT, see OpenAI’s terms and policies. For Claude, see Anthropic’s privacy policy. For other AI services, refer to the provider’s own documents.

5. Retention

Content in your fynk account

Documents, templates and other content created or changed through the integration are stored in the fynk account like any other content. They stay there until they are deleted in fynk. When the customer’s contract ends, the data is returned or deleted as set out in the DPA and our terms and conditions. Disconnecting the integration does not delete any of it. Its up to the customer to decide how long data is stored in their account, fynk follow the customers instruction in that regard.

Connection data

Access tokens are valid for one hour. The AI service renews them with a refresh token, which is valid for three months and replaced each time it is used. If the AI service does not renew the connection within three months, the connection expires.
When a connection is disconnected, its tokens are revoked immediately and deleted within an hour. The link between the connection and your fynk account is deleted at once.
Expired tokens, and the link between an expired connection and your fynk account, are deleted seven days after expiry.

Request logs and error reports

fynk logs every request to the MCP server with the time, IP address, user agent, user and account identifiers, the tool called and the details sent with it. These details can include personal data, such as the names, email addresses and phone numbers of signatories. Template text and uploaded files are not written to the logs, and neither is the data fynk returns to the AI service. Request logs are deleted automatically after 180 days.

If a request fails unexpectedly, fynk sends an error report to the error-tracking service named in the list of subprocessors. An error report can include the details of the request and the email address of the user whose connection sent it.

Data held by the AI service

How long the AI service keeps data depends on the provider and on your settings there. Deleting data in fynk or disconnecting the integration does not delete copies the AI service has already received, for example in your chat history.

6. Your controls

Connecting

The integration only works if the MCP server is enabled for the fynk account. Admins can turn it on and off in the account settings.
A connection always starts in the AI service. You then sign in to fynk and approve the request. fynk shows you which application is asking for access. If it does not recognize the application, it shows the web address that would receive access instead and asks you to confirm that you trust it. Only approve requests you started yourself.

Permissions

The AI service always acts with your current role and document permissions in fynk. If your permissions change, the integration’s access changes with them. Tools you lack the permission for are not offered to the AI service at all.

Disconnecting and turning off

Users can see their own connections in their fynk profile under “MCP” and disconnect them there.
Admins can see every user’s connections in the account settings under “MCP”, disconnect any of them, and turn off the MCP server for the whole account. Admins can also be notified by email when a user connects an AI service for the first time.
A disconnected connection loses access immediately. Turning off the MCP server blocks all requests at once but keeps existing connections: if it is turned back on while they are still valid, they work again. To end a connection for good, disconnect it.
Removing fynk in the AI service’s settings does not necessarily revoke access in fynk. Disconnect it in fynk as well.

Disconnecting does not delete data

Disconnecting or turning off the integration only stops future access. It does not delete documents created or changed through the integration, audit trail entries, request logs, or data the AI service has already received. To delete content in fynk, delete it in fynk or ask your account admin. For data held by the AI service, please refer to the provider’s own tools, fynk can in no way influence the processing of data transferred to the thrid party ai service.

7. Requests and contact

Data in a customer’s fynk account. The customer is the controller for this data. To exercise your data protection rights regarding it, for example as a signatory or as a user, please contact the organization that uses fynk, such as your employer or the company that sent you a document. If you contact fynk instead, we will refer you to that organization, as the DPA requires, and support it in answering your request.

Data held by the AI service. Please contact the provider of the AI service.

Questions about this notice. Contact fynk GmbH, Heinrichsgasse 2/1/8, 1010 Vienna, Austria, at [email protected]. Our data protection officer is Kertos GmbH (Dr. Kilian Schmidt), [email protected]. For help with connecting or disconnecting the integration, contact [email protected].

You also have the right to lodge a complaint with a data protection supervisory authority.

Terms and conditions
Data processing agreement (DPA) and list of subprocessors
Privacy policy: how fynk processes personal data as a controller, within the scope described there, for example when you visit our website
Trust Center: security and compliance information

Last updated: October 6, 2026