Privacy policy

What this policy covers

It covers LML MCP Connector, the MCP (Model Context Protocol) server through which an AI assistant reads and manages your schedule, integrating with Google Calendar.

It is a standalone document specific to this application. It neither replaces nor is replaced by the general privacy notice of the lmltech.it website, which concerns browsing the website and is a separate document.

1. Access — which data from your Google account we read

The connector requests four authorisation scopes on your Google account: two concern the calendar, the other two the account you authorised with. The two calendar scopes are presented to you as permissions to approve on the Google consent screen on first use. The other two are part of signing in with Google and do not appear as separate items, because they give access to no content: they serve only to identify the connected account. Under no circumstances does any access take place before you have authorised the application.

No other scope is requested. The connector does not access the contents of Gmail, nor Contacts, Drive, Photos or any other service on your Google account.

2. Use — the purposes the data is used for

The calendar data listed above is used for one purpose only: carrying out the calendar operations you request through your AI assistant. The email address and the account identifier play no part in those operations: they serve only to recognise the connection and to show it to you.

• Showing you the commitments within a given time range.
• Identifying the slots still free when you ask to check availability.
• Creating a new event with the details you provide.
• Updating an existing event when you ask to move or change it.
• Showing you which Google account is connected, so that you can check it and correct it if needed.

It is not used for any other purpose. The connector takes no action on its own initiative and does not run in the background: every read and every write originates from an explicit request of yours.

3. Sharing — who the data is shared with or transferred to

When you ask your AI assistant to review or modify your schedule, the calendar data needed to answer is transmitted to the MCP client you have connected — that is, to the AI assistant itself and, consequently, to the provider that operates it. This is how the Model Context Protocol works: the connector retrieves the data from Google Calendar and returns it to the client that requested it.

This transmission takes place solely upon your action, in response to a request of yours, and never autonomously. Any subsequent processing by the provider of the AI assistant is governed by that provider’s own privacy policy, which we encourage you to read.

Besides the MCP client you have connected, the data may be processed by the infrastructure providers LML Technologies relies on, acting as data processors under Art. 28 GDPR and contractually bound to operate only on the controller’s instructions: the provider of the hosting infrastructure the connector runs on, located in the European Union. An up-to-date list of the data processors is available on request by writing to info@lmltech.it.

Calendar data is under no circumstances:

• sold, disclosed or otherwise transferred to third parties or data brokers;
• used for advertising, retargeting or profiling;
• used to train, retrain or improve generalised artificial intelligence or machine learning models;
• used for creditworthiness assessments or to determine credit standing.

LML MCP Connector’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The full text of the policy is available at https://developers.google.com/terms/api-services-user-data-policy

Access by LML Technologies staff

LML Technologies staff do not access users’ calendar data. There are only three exceptions:

• where the user gives explicit and specific consent to that access;
• where access is necessary for security reasons or for debugging confined to a reported issue;
• where there is a legal obligation or an order from a competent authority.

4. Protection — security measures

Calls to the Google APIs are made exclusively over HTTPS with TLS encryption. The technical and organisational measures applied to the infrastructure the connector runs on are set out below:

• Encryption in transit: all communication between the MCP client and the connector takes place over HTTPS with TLS 1.2 or higher. Unencrypted connections are not accepted.
• Encryption at rest: sensitive data is encrypted at rest using the AES algorithm with a 128-bit key in CBC mode with HMAC-SHA256 authentication. The encryption keys do not reside in the database and are supplied to the application through protected environment variables; the system supports periodic key rotation without service interruption.
• OAuth tokens: the authorisation tokens issued by Google are stored exclusively in encrypted form inside a PostgreSQL database that is not reachable from outside, hosted on the same infrastructure as the connector. They are never written in clear text, never recorded in the logs and never transmitted to third parties.
• Access control: access to the systems is restricted to authorised LML Technologies technical staff, through named individual credentials. Administrative access is logged. Each client company connects solely through a credential dedicated to it, which can be revoked individually.
• Isolation between customers: each client company has its own separate access credential. The connector determines data ownership from that credential alone: a customer cannot reach another customer’s calendar data, because identification does not depend on any parameter the caller can modify.
• Hosting: the infrastructure the connector runs on is housed in a data centre located in the European Union.

5. Retention and deletion

You can revoke access at any time, without going through LML Technologies, from the permissions page of your Google account: https://myaccount.google.com/permissions

From that moment the connector has no further access to your calendars. The authorisation tokens and the data associated with them are deleted immediately: upon revocation the connector in turn revokes the token with Google and removes it from the live systems without delay. Any residual copies held in backups are deleted within 30 days.

You may in any case request deletion by writing to info@lmltech.it. Requests are handled within one month, as provided by Art. 12 GDPR.

• Authorisation tokens: tokens are retained for as long as the connection lasts and are deleted upon revocation or upon termination of the service, within the times stated above.
• Calendar data: calendar data is not stored. It is read from Google at the time of the request, transmitted to the MCP client that asked for it, and not retained: there is no archive of events, attendees or calendar content at LML Technologies.
• Email address and account identifier: they are kept alongside the authorisation they belong to, for as long as the connection lasts, and are deleted upon revocation within the same times as the tokens.
• Technical logs: technical logs record operational data only — date and time, client company, user identifier, requested operation, outcome and duration — and are kept for 365 days for security and diagnostic purposes. They never contain event titles, attendees, locations or descriptions, nor the authorisation tokens.

Legal bases for processing

• Performance of the contract entered into with the client company where the service is active (Art. 6(1)(b) GDPR).
• The consent you give through the Google authorisation screen, for access to calendar data, withdrawable at any time (Art. 6(1)(a) GDPR).
• Legitimate interest in ensuring the security and correct operation of the service, for technical logs only (Art. 6(1)(f) GDPR).

Transfers to third countries

The connector’s infrastructure is located in the European Union, and calendar data is not transferred outside the European Economic Area by LML Technologies.

This is without prejudice to any transfer carried out by Google, acting as an independent controller for the data that remains in your Google account, and by the provider of the AI assistant you have connected, each under its own privacy policy.

Should a transfer take place, it does so on the basis of an adequacy decision of the European Commission or of standard contractual clauses under Art. 46 GDPR.

Your rights and how to exercise them

You may at any time exercise the rights provided for by Arts. 15-22 GDPR: access to your data, rectification, erasure, restriction of processing, portability and objection. You may also withdraw your consent at any time, without affecting the lawfulness of processing carried out before withdrawal.

To exercise them, write to info@lmltech.it stating the right you wish to exercise. You will receive a response within one month of the request, as provided by Art. 12 GDPR.

You also have the right to lodge a complaint with the Italian Data Protection Authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it).

LML Technologies has not appointed a Data Protection Officer, as the conditions set out in Art. 37 GDPR do not apply. For any matter concerning data protection you can write to info@lmltech.it.

Changes to this policy

Updates are published on this page, with the last-updated date shown at the top. The address of this page is stable and does not change.

Contact

For any question about this policy or about the processing of your data: info@lmltech.it