Simplafy MCP

This page supplements the Privacy policy and the Terms of use, which remain fully in force.

1.1. MCP (Model Context Protocol) is an open industry standard that lets an AI assistant use tools from external systems. Simplafy MCP is the Simplafy platforms' implementation of that standard.

1.2. In practice: you authorize the assistant and can then ask, in plain language, for things you would otherwise do manually in the platform.

1.3. Simplafy MCP is not a separate product nor a new database. It is a second way into the same platform you already subscribe to.

1.4. The feature is optional and is not enabled automatically.

1.5. Availability varies by platform and evolves over time. What is available, and with which tools, is shown in the platform itself.

1.6. Because it is an open standard, Simplafy MCP is not tied to any single assistant: any AI client compatible with the protocol can be connected, following the connection instructions shown in the platform itself. Publishing a connector in a particular assistant's store is a separate process, specific to that vendor, and is not a precondition for the direct use described on this page.

2.1. The credential is issued by an authenticated user and operates under that user's access profile: the tools available to the assistant do not exceed what that profile can reach in the platform.

2.2. Each operation is authorized by the same access controls that apply in the platform interface. There is no parallel authorization path created for the assistant.

2.3. Where the credential is displayed on screen, it appears only once, at the moment of issuance. Treat it like a password: do not share it, do not send it by e-mail or message, do not publish it.

2.4. The way it is issued varies by platform: in some, the connection is authorized through your AI assistant's standard flow; in others, a key is generated in your profile inside the product.

3.1. This is the most important clause on this page. When you connect an AI assistant, the data it reads leaves the Simplafy perimeter and is transmitted to the artificial intelligence provider you chose to connect (for example, OpenAI, in the case of ChatGPT).

3.2. From that point on, the provider's processing of that data is governed by the provider's own terms and privacy policy, not by this page. We recommend reading them before connecting.

3.3. Simplafy does not control what the AI provider does with the content it receives, including any retention, human review or use for model training.

3.4. The assistant receives the records you ask for. Those records may contain personal data of third parties — for example the name, ID number, phone number, address or history of your organization's contacts, customers or patients. Keep this in mind before connecting and when phrasing requests.

3.5. We work continuously so that each response carries only what the task needs. This effort reduces, but does not eliminate, the transmission of personal data when the data itself is what you asked to look up.

4.1. The roles defined in the Privacy policy remain in place: as a rule, the customer/USER is the Controller of the data entered into the platform, and Simplafy acts as the Processor.

4.2. Connecting an AI assistant is an instruction from the Controller. By connecting, the Controller determines that the AI provider becomes a recipient of the data reachable by the credential.

4.3. The Controller is responsible for ensuring an appropriate legal basis for this transmission, informing its data subjects where applicable, and observing the sector-specific rules of its industry.

4.4. The authorization recorded in the product is access control. It does not, in itself, constitute a legal basis for processing, nor does it replace data subjects' consent where consent is required.

5.1. In Simplafy Hub, today:

• Operation log: every assistant action is logged with the credential and user that acted, the organization, the tool used, whether it was a read or a change, the result, the number and identifiers of the records reached (up to 50 per operation), the time and the response latency. Of the parameters sent, only identifiers, filters and pagination are kept — never free text. The log is kept for 12 months and then deleted by an automatic daily routine.
• Credentials: the access credential is valid for 15 minutes; the refresh credential is valid for up to 30 days and is replaced on every use. The Hub stores only a hash of the credentials, never their value.
• Revocation: the user revokes under Configurações → Meu perfil → Meus assistentes (Settings → My profile → My assistants); organization administrators see and revoke all members' connections, and limit which roles and areas assistants can reach, under Configurações → Controle de assistentes (Settings → Assistant control). The assistant can also end the connection through the standard revocation endpoint (/api/oauth/revoke). Revocation applies from then on, without waiting for the credential to expire.

5.2. On the other Simplafy platforms, Simplafy MCP is being rolled out in stages. What is available on each — including how to revoke a credential — is shown in the platform itself, at the time of authorization.

5.3. On every platform, the operation log does not store the content of the responses returned to the assistant.

5.4. Stopping access ends future use of the credential. It does not reach data already transmitted to the AI provider — for that data, the provider's terms and channels apply.

5.5. Communication between the assistant and the platform takes place exclusively over an encrypted channel (TLS), under a domain controlled by Simplafy.

6.1. On platforms that handle sensitive personal data, such as health data, the feature will only be offered once enabled by the responsible organization, under the applicable contractual terms — not by an individual user's decision.

6.2. Additional logging, retention and transparency requirements applicable to those contexts will be described in the platform itself and in the contractual instruments, before the feature is made available.

• It does not create a parallel database or a copy of your content: the content continues to live in the platform.
• It does not replace the platform interface, which remains available and is where the organization manages access.
• It is not a support channel nor a channel for communicating with Simplafy.

8.1. Questions about this page, data subject requests and data protection communications must be sent through the channels listed in the Privacy policy or directly to the Data Protection Officer (DPO).

9.1. This page describes the current state of the feature and will be updated as it evolves. The version in force is always the one published at this address, identified by the date at the top.

9.2. In case of conflict between this page and the Privacy policy or the Terms of use on matters governed by those documents, those documents prevail.