Daidalytics MCP for Google Analytics

Privacy policy

Last updated: 18 November 2026

This policy explains what Daidalytics MCP for Google Analytics ("the service") does with your data when you connect it to your Google account. In short: the service reads your Google Analytics data only when you ask for it, passes it to the AI assistant you connected, and does not store it. It stores what it needs to keep you signed in, and the notes you choose to save.

Who is responsible

The service is developed and operated by Daidalytics ApS (CVR 45049272), Store Mølle Vej 8, 5. tv, 2300 København S, Denmark ("we", "us").
Contact: gunnar.griese@daidalytics.com

Our role depends on the data:

The service is a Model Context Protocol (MCP) server. It lets an AI assistant that you connect (for example Claude, ChatGPT or Cursor) run Google Analytics 4 reports and look up property information on your behalf, using your own Google account's access.

Data Accessed

When you sign in with your Google account, the service requests this access:

With that access the service can read:

The service cannot change, create or delete anything in Google Analytics. It does not request your name, profile picture or any other Google data.

Apart from Google data, the service handles:

How Your Data Is Used

The service uses the data exclusively to:

We do not sell your data, do not use it for advertising, and do not use it to develop, improve or train AI or machine-learning models. The service itself contains no AI model. No analytics or telemetry is collected about how you use the service beyond the server logs described below.

The use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data Sharing

Your data is shared only with:

We share data with nobody else, unless the law requires it.

Data Storage and Protection

The service, its database, its file storage and its logs run in the EU, in Google Cloud's Finland region.

DataWhere it is stored
Google Analytics data (reports, account and property lists, dimensions and metrics) Not stored. It is fetched from Google for each request, returned to your assistant, and not written to any database, file or log.
Google access and refresh tokens, and records of your sign-in session In the service's database, encrypted by the service before they are written.
Your Google account ID and email address Held in memory while your sign-in is checked. Written only as the author of a context-layer change, and in the logs as described in the last row.
Context layers, with the author's email address (or Google account ID) and change note In a private storage bucket that only the service can access.
Server logs: the technical data above; your Google account ID when access to a property is refused; the property ID and version number when a context layer is updated or exported, with your email address for an update; and, when a report times out, the property ID and an outline of the request (date range, names of the dimensions, number of metrics, whether filters were set) In the service's log storage. Logs never contain tokens, report results, filter values or the content of a context layer.

Security measures (data protection mechanisms for sensitive data)

Data Retention and Deletion

DataHow long it is kept
Google Analytics dataNot stored.
Google tokens and sign-in recordsDeleted automatically at most 90 days after your session was last renewed.
Google account ID and email address in memoryUp to 5 minutes.
Context layersThe current version is kept until it is replaced or you ask us to delete it. Up to 10 earlier versions are kept, each for at most 90 days, and deleted data can be recovered for 7 more days.
Server logs30 days.
Sign-in cookies (in your browser)15 minutes for the approval step; up to one year for remembering which assistants you approved or declined.

Revoking access. You can disconnect the service at any time in your Google account under Third-party apps and services (https://myaccount.google.com/connections). From that moment Google rejects the tokens the service holds, and the service can no longer read your data. You can also remove the connector in your AI assistant.

Deletion. After you revoke access, the encrypted copies of the tokens are useless and are deleted automatically within 90 days. To have them, a context layer, or any other data about you deleted sooner, write to gunnar.griese@daidalytics.com.

Legal basis and your rights

Where we are the data controller, we process sign-in data to provide the service you asked for (GDPR Article 6(1)(b)), and logs on the basis of our legitimate interest in running a secure service (Article 6(1)(f)). Where we are a data processor, the legal basis is a matter for the organisation responsible for the property.

Under the GDPR you have the right to access, correct, delete, restrict or object to the processing of your personal data, and to receive it in a portable form. Write to gunnar.griese@daidalytics.com to use these rights; for data we process on behalf of an organisation, we pass your request on to it. You can also complain to the data protection authority in your country.

Other ways of connecting

Some applications send the service a Google token you already gave them, instead of using the sign-in above. Such a token is checked with Google and used for that request, and is not stored. Organisations that connect with an API key do so under a separate agreement.

Changes

If this policy changes, the new version is published on this page with a new date. If a change affects how your Google data is used, we will ask for your consent before it applies to you.