{"id":2388,"date":"2026-07-31T18:28:22","date_gmt":"2026-07-31T16:28:22","guid":{"rendered":"https:\/\/www.edito-pdf.com\/edito-mcp-privacy-policy\/"},"modified":"2026-08-01T10:21:17","modified_gmt":"2026-08-01T08:21:17","slug":"edito-mcp-privacy-policy","status":"publish","type":"page","link":"https:\/\/www.edito-pdf.com\/en\/edito-mcp-privacy-policy\/","title":{"rendered":"Edito – MCP Privacy Policy"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tPrivacy<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tTerms and Conditions<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tEULA<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

PRIVACY POLICY<\/h1>\n

EDITO-PDF\u00ae MCP CONNECTOR<\/h1>\n
\n\nJugaad S.r.l.<\/strong> \u2013 Via Luigi Reverberi 30A, 42027, Montecchio Emilia (RE)\nPEC: jugaad@legalmail.it | E-mail: contatto@edito-pdf.com\nLegal representative: Dr. Giacomo Verdi\n\n<\/div>\n\n
\n\n

Art. 1 \u2013 Data Controller<\/h2>\nThe Data Controller is Jugaad S.r.l.<\/strong>, with registered office at Via Generale Luigi Reverberi 30\/A, 42027 Montecchio Emilia (RE), VAT No. 02905570350, SDI SUBM70N, in the person of its legal representative Dr. Giacomo Verdi (hereinafter also “the Controller” or “the Provider”).\n\nFor communications regarding this privacy policy: support@edito-pdf.com | Tel. 0522-1607520.\n\n

Art. 2 \u2013 Scope of Application<\/h2>\nThis Privacy Policy applies exclusively to the Edito-Pdf MCP Connector (hereinafter “the Connector”), which enables AI assistants such as Claude (Anthropic) to interact with pseudonymized documents generated by the Omissis<\/strong> module within the EDITO\u00ae<\/strong> platform, via the Model Context Protocol (MCP).\n\nThis privacy policy does not cover the Edito-Pdf web application (app.edito-pdf.com) or other platform services, which are governed by their own privacy policy available at https:\/\/www.edito-pdf.com\/en\/edito-privacy\/<\/a>.\n\n

Art. 3 \u2013 Data Processed<\/h2>\n3.1 Authentication data<\/strong>\nOAuth 2.0 tokens (access token, refresh token), API keys (stored as irreversible SHA-256 hashes), and the internal user identifier associated with the Edito-Pdf account.\n\n3.2 Pseudonymized document content<\/strong>\nThe Connector retrieves exclusively the text of documents already pseudonymized by the Omissis module of the Edito-Pdf platform. All personally identifiable information (PII) is replaced with opaque labels (e.g., [[PERS_1]], [[LOC_2]]) before<\/em> reaching the Connector or any AI model. The Connector never accesses or transmits the original non-pseudonymized text through the MCP protocol. \n\n3.3 Entity dictionaries (server-side only)<\/strong>\nThe mapping between pseudonymous labels and real values is stored in the Edito-Pdf platform database. It is accessed server-side exclusively when the user explicitly requests de-pseudonymization. Real values are never returned in tool responses or exposed to the AI assistant. \n\n3.4 Email address<\/strong>\nThe email address associated with the user’s Edito-Pdf account is used exclusively to deliver de-pseudonymized documents upon the user’s explicit request.\n\n3.5 Technical logs<\/strong>\nThe Connector records authentication events and errors for security and debugging purposes. Logs may include: timestamps, user ID, client ID, IP address, user-agent, and error codes. Logs do not contain document content, entity values, or API keys in plain text. \n\n

Art. 4 \u2013 Purpose and Legal Basis (GDPR Art. 6)<\/h2>\n\n\n\n\n\n\n\n\n
Purpose<\/th>\nLegal basis<\/th>\n<\/tr>\n<\/thead>\n
Authentication and authorization to access user documents<\/td>\nPerformance of contract (Art. 6(1)(b))<\/td>\n<\/tr>\n
Retrieval and presentation of pseudonymized document content<\/td>\nPerformance of contract (Art. 6(1)(b))<\/td>\n<\/tr>\n
De-pseudonymization and delivery of documents via email<\/td>\nExplicit user request \/ Performance of contract (Art. 6(1)(b))<\/td>\n<\/tr>\n
Security logging and fraud prevention<\/td>\nLegitimate interest (Art. 6(1)(f))<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n

Art. 5 \u2013 Data Recipients and Transfers<\/h2>\n5.1 Infrastructure<\/strong>\nGoogle Cloud Platform (region: europe-west1, Belgium) \u2014 Cloud Functions, Firestore, Cloud Storage. SMTP relay for email delivery. \n\n5.2 AI assistant providers<\/strong>\nThe pseudonymized text of documents is transmitted to the AI assistant (e.g., Claude by Anthropic) through the MCP protocol. Since documents are pseudonymized before reaching the AI provider, no real personal data is shared with it. \n\n5.3 No other third parties<\/strong>\nThe Connector does not share data with advertisers, analytics providers, data brokers, or any other third parties.\n\n5.4 International transfers<\/strong>\nAll data processing takes place within the EU\/EEA (Google Cloud europe-west1). Pseudonymized text transmitted to AI providers may be processed outside the EEA according to their respective data processing agreements. Since the text is pseudonymized, no directly identifiable personal data leaves the EEA. \n\n

Art. 6 \u2013 Data Retention<\/h2>\n