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:
- We are the data controller for the data we need to run the service: your sign-in data (Google account ID, email address, tokens), server logs and sign-in cookies.
- We are a data processor for the Google Analytics data the service reads at your request and for the context layers you save. The data controller for that data is the organisation responsible for the Google Analytics property (you, your employer or your client). The terms of service set out the processing terms.
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:
https://www.googleapis.com/auth/analytics.readonly: See and download your Google Analytics data. Used to run the reports you ask for and to list your accounts, properties, dimensions and metrics. Read-only.openid: Confirms which Google account signed in.email: Your Google account's email address. Used to identify your session and to sign the changes you make to a context layer.
With that access the service can read:
- Google Analytics data: the accounts and properties your Google account can see, their dimensions and metrics, report results (standard, realtime, pivot and funnel reports), and data-access reports for properties you administer.
- Google account information: your Google account ID and your email address.
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:
- Context layers: documents that you or your assistant save about a Google Analytics property (tracking plan, annotations), with a change note. Each document starts with a short header: the title, description and tags you give it, and the property's ID and Google Analytics address, which the service adds.
- Technical data: IP address, browser or client name, the address requested and the time of each request. For some requests the service also records the property ID and, when a report times out, an outline of the request (see the logs row below).
- Sign-in cookies: strictly necessary cookies set during the approval step of sign-in. The public pages set no cookies, and the service uses no tracking or advertising cookies.
How Your Data Is Used
The service uses the data exclusively to:
- run the Google Analytics requests your assistant makes on your behalf, and return the results to that assistant;
- keep you signed in, so you don't have to approve access on every request;
- check that your Google account can read a property before returning data or a context layer for it;
- sign the changes you make to a context layer with your email address (or Google account ID);
- operate and secure the service and investigate errors, using the technical data.
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:
- The AI assistant you connected. Report results are returned to it because you asked for them. What the assistant and its provider do with them is governed by that provider's terms and privacy policy.
- Google Cloud, which hosts the service as our data processor.
- Other people with access to the same Google Analytics property, for context layers only: everyone whose Google account can read a property can read, export and change that property's context layer through the service, and can see who made each change. An export returns the same document split into files, in the Open Knowledge Format, to the assistant that asked for it; the service sends it nowhere else. Don't put personal or confidential information in a context layer.
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.
| Data | Where 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)
- Encryption in transit: all connections to the service, and from the service to Google's APIs, use HTTPS/TLS.
- Encryption at rest: tokens and sign-in records are encrypted by the service before they reach the database, with a key kept in a separate secret store. Google Cloud additionally encrypts all stored data.
- Token isolation: your Google tokens are never passed to AI assistants. An assistant receives its own separate session token, which only works with this service.
- Access control: the service checks with Google that your account can read a property before it returns data or a context layer for it. The database and storage bucket are not publicly accessible. Access by our staff to stored records (logs and context layers) is limited to what is needed to operate and secure the service, to comply with the law, or to help you when you ask. We do not look at your Google Analytics data.
- Data minimisation: the service requests read-only access, the narrowest Google Analytics access there is, and does not store the Google Analytics data it reads.
- Revocation: you can withdraw the service's access at any time, as described below.
Data Retention and Deletion
| Data | How long it is kept |
|---|---|
| Google Analytics data | Not stored. |
| Google tokens and sign-in records | Deleted automatically at most 90 days after your session was last renewed. |
| Google account ID and email address in memory | Up to 5 minutes. |
| Context layers | The 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 logs | 30 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.