Aiaa Privacy Policy
Last updated: October 18th, 2026
Introduction
Analytical42 does not store, sell or share any data accessed through Aiaa. This policy explains how Aiaa accesses and handles Google user data, and what choices you have.
Aiaa is operated by Analytical42 (CVR 29228396), Bastrupvej 30, 4400 Kalundborg, Denmark. In this policy, "we" and "us" mean Analytical42, and "you" means anyone who connects their Google account to Aiaa.
What Aiaa is
The AI Analytics Assistant (Aiaa) is an analytics product developed by Analytical42 together with The Social Shop. It lets you ask questions about your own business data in Claude, an AI assistant made by Anthropic, and get insights, reports and recommendations back. Technically, Aiaa uses an OAuth application through which you authorise Claude to query your Google BigQuery data via Google's BigQuery MCP server.
When you connect, Google issues an access token directly to Claude. Claude then sends requests straight to Google BigQuery. No server operated by Analytical42 sits between Claude and Google, so the data never passes through our systems.
The data Claude can query is data your organisation has chosen to make available in BigQuery. Together with you, we identify the relevant data, for example from Google Analytics, your CRM, ad accounts or ERP, and structure it in your BigQuery project. That setup work is done as a client engagement under a data processing agreement, separately from the Google sign-in described in this policy.
Aiaa is used by Analytical42, The Social Shop, and employees of our clients who have been given access to their organisation's BigQuery projects.
Google user data Aiaa accesses
Aiaa requests one Google OAuth scope: https://www.googleapis.com/auth/bigquery (view and manage your data in Google BigQuery). With it, Claude can:
- list the projects, datasets and tables you have access to
- read table schemas and metadata
- run queries and read their results
Access is limited to Google Cloud projects where you have been granted the required IAM roles. Aiaa cannot reach any project you do not already have permission to use.
As part of signing in, Google confirms which Google account you are using. Aiaa does not request access to Gmail, Google Drive, Contacts, Calendar or any other Google service.
How the data is used
BigQuery data is used only to answer the questions you ask Claude in conversations you start, such as analyses, reports and checks of your own data.
We do not use data accessed through Aiaa:
- for advertising or marketing
- to build user profiles
- to train or improve artificial intelligence or machine learning models
- for any purpose other than providing the analysis you request
We never sell this data.
Storage and retention
Analytical42 stores no Google user data. We do not keep copies of your BigQuery data, query results or access tokens.
- Your BigQuery data stays in your own Google Cloud project, under your organisation's control.
- Access tokens are issued by Google to Claude and held by Anthropic as part of the Claude connector. They are never sent to Analytical42.
- Query results shown in a Claude conversation are retained according to your Claude account settings and Anthropic's policies, and you can delete those conversations in Claude.
Sharing and third parties
We do not share Google user data with anyone. Two providers handle data as part of how Aiaa works:
| Provider | Role | Privacy Policy |
|---|---|---|
| Authenticates you and hosts BigQuery and the BigQuery MCP server | Google Privacy Policy | |
| Anthropic | Provides Claude, which sends your queries to BigQuery and shows you the results | Anthropic Privacy Policy |
We may disclose information only if required by law, and only to the extent required.
Google API Services Limited Use
Aiaa's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular, data obtained through Google APIs is not used to develop, improve or train generalised artificial intelligence or machine learning models, and no human at Analytical42 reads it unless you ask us to help with a specific analysis, it is needed for security reasons, or it is required by law.
Roles under GDPR
When BigQuery data contains personal data, our client remains the data controller for that data. Where Analytical42 or The Social Shop works with it on a client's behalf, including preparing data for Aiaa, we act as data processors under data processing agreements with that client.
Use of Claude is governed by the agreement between the Claude account holder and Anthropic. Analytical42 is the data controller only for the limited contact information you send us directly, such as an email to our privacy contact.
Security
- Sign-in uses Google's OAuth 2.0. Analytical42 never sees your Google password or access tokens.
- What each user can reach is controlled by Google Cloud IAM in each project. We recommend granting only the roles Aiaa needs: MCP Tool User, BigQuery Job User and BigQuery Data Viewer.
- All traffic between Claude and Google is encrypted over HTTPS.
Revoking access and your rights
You can stop Aiaa's access at any time, in any of these ways:
- Disconnect the BigQuery connector in your Claude settings.
- Remove the app under Third-party connections in your Google Account at myaccount.google.com/connections.
- Ask your Google Cloud project administrator to remove your IAM roles.
Under the GDPR you have the right to access, correct, erase and restrict processing of your personal data, and to object to it. For data in a client's BigQuery project, contact that organisation first; we will help them respond. You can also complain to the Danish Data Protection Agency, Datatilsynet.
Changes and contact
We may update this policy when Aiaa changes. The date at the top shows when it was last updated, and significant changes will be communicated to active users.
Questions about this policy or your data:
Analytical42
Bastrupvej 30, 4400 Kalundborg, Denmark
CVR 29228396
phillip@analytical42.com