Privacy policy

Last updated 24 September 2026

Mantaq is an AI workspace. This policy explains what we collect, why we collect it, who we share it with and what you can ask us to do about it. It covers the whole product, and it covers Google data in particular detail because connecting a Google account is the part people ask about most.

About the Mantaq platform

Mantaq lets a team ask questions in plain language and get answers drawn from the systems they already use, with the reasoning shown alongside the answer. To do that it connects to sources you choose, retrieves what is relevant to a question, and sends that material to an AI model to produce the response.

Two consequences follow, and both are covered below: your content passes through an AI model provider (sub-processors), and Mantaq can only ever read what the account you connected could already read (connected accounts).

What we collect, and how

Information you give us

• Account details. The email address used to sign in, and the display name your team sets.
• Content you put in. Documents, files, questions, conversations, agent instructions and workspace settings.
• Correspondence. Anything you send us by email when you ask for support.

Information from systems you connect

• Content from connected sources. When an administrator connects a source, Mantaq reads material from it so questions can be answered against it.
• Credentials for those connections. Stored encrypted, and described under Google user data and connected accounts.

Information collected automatically

• Operational logs. Requests to the service, timestamps and error traces, used to keep it running and to investigate faults.
• Model usage. Token counts and cost per person, so administrators can see activity and spend across their workspace.

Cookies

The Mantaq application sets a session cookie so you stay signed in. It is necessary for the product to function and is not used for advertising or cross-site tracking. This marketing site, mantaq.ai, sets no cookies and runs no analytics or advertising trackers.

How we use it

• To provide the product: retrieving material, producing answers, running agents and showing the reasoning behind a result.
• To keep accounts secure and to verify that someone asking for data is entitled to it.
• To operate and maintain the service, including diagnosing faults.
• To give administrators visibility of usage and cost in their own workspace.
• To respond when you contact us.
• To meet legal obligations that apply to us.

We do not sell personal data. We do not use your content or your Google data for advertising or profiling.

Google user data

Connecting a Google account is optional. Mantaq works without one. You only grant access if you want to ask questions about your Search Console or Analytics data.

What we request, and why

Permission	What it allows	Why we need it
webmasters.readonly	Read-only access to Search Console for properties the connected account can already access.	To answer questions about search queries, landing pages, clicks, impressions and average position.
analytics.readonly	Read-only access to Google Analytics 4 for the same account.	To answer questions about users, sessions, acquisition channels and page views.
userinfo.email	The email address of the connected Google account.	To display which account is connected, so teams can tell several linked accounts apart and avoid linking the same one twice.

These are the narrowest scopes that support the feature. Mantaq holds no permission to create, edit or delete anything in your Google account, and it cannot see any Google property the connected account does not already have access to.

How we use Google data

When a question needs Search Console or Analytics data, Mantaq requests the figures needed to answer it and uses them for that answer. Nothing else.

• Google data is fetched at the time of the question, not copied into a separate store or search index.
• We do not retain the Search Console or Analytics figures after the answer has been produced.
• We do not use Google user data to train, retrain or improve any AI model.
• We do not use it for advertising, profiling or any form of marketing.

What we store, and how it is protected

The only Google data we keep is what is needed to maintain the connection you authorised:

• A refresh token. This is the credential that lets Mantaq keep reading on your behalf. It is encrypted before it is written to disk, on infrastructure we control, and the key is kept separately from the data.
• The Google address and the name your team gave it. This is how the connection is identified in the interface.

Short-lived access tokens are requested from Google as needed and held in memory only; they are never written to disk. No Google credential is ever sent to the browser, written to logs, or returned by any API we expose.

Who can see it

A connected Google account is available to everyone in your Mantaq workspace, so a team can work on shared client accounts. Nobody outside your workspace can reach it.

Connected accounts and integrations

Beyond Google, Mantaq can connect to sources such as Slack, Google Drive, Notion, Confluence, SharePoint, Jira and others. In every case the same rules apply:

• An administrator makes the connection. It is not something an individual member can do quietly.
• Mantaq can only read what the connecting account could already read. The integration grants no new reach.
• Credentials are held by Mantaq, encrypted, and are never shown to users or returned by any API.
• Disconnecting a source ends Mantaq's access to it.

Those third-party services are governed by their own privacy policies, and what they do with your data on their side is not something we control.

AI models, and what is never used for training

Producing an answer means sending the question, and the material retrieved to answer it, to an AI model provider. That is inherent to how the product works.

Your content is not used to train, retrain or improve any AI model. Not ours, and not the model provider's. It is sent to produce your answer and for no other purpose.

AI output can be wrong or incomplete. Mantaq shows the sources and steps behind each answer precisely so it can be checked rather than taken on trust.

Sub-processors

We use a small number of providers to run the service. They process data on our instructions and only to deliver the product.

Provider	What it does	Where
Amazon Web Services	Hosts the application, the database and stored files.	EU (Stockholm)
Anthropic	Provides the AI model that produces answers.	United States
Google	Supplies Search Console and Analytics data, only for accounts you connect.	Per Google's own terms

If we add or replace a sub-processor we will update this page. Ask us at support@mantaq.ai if you need to be told in advance.

Disclosure to third parties

We do not sell your data. We share it only:

• with the sub-processors listed above, to run the service;
• when you tell us to, for example by connecting a source;
• if the law requires it, or to establish or defend a legal claim;
• to protect the security of the service or the rights of its users.

International transfers

The application and its data are hosted in the European Union, in AWS's Stockholm region. Producing an answer involves sending content to an AI model provider in the United States, so some processing takes place outside the EU. Where that happens we rely on the safeguards in our agreements with those providers.

Security

• Traffic to Mantaq is served over HTTPS, and calls to third-party APIs go over TLS.
• Stored third-party credentials are encrypted at the application level, with the key held separately from the data.
• Short-lived access tokens are kept in memory and never written to disk.
• Connecting and disconnecting sources is restricted to administrators.
• Agents run in isolated, temporary sandboxes, and credentials are attached by a proxy rather than being exposed to the agent.

No system is perfectly secure. If you believe you have found a vulnerability, please tell us at support@mantaq.ai and give us a reasonable opportunity to fix it before publishing.

Retention and deletion

• Google figures are not retained at all. They are fetched to answer a question and discarded.
• Connection credentials are kept until the source is disconnected, then deleted.
• Your content and conversations are kept while the workspace is active, so the product can use them. Administrators can set a retention period for chats.
• Operational logs are kept for a limited period for diagnostics and then rotated out.

When a workspace is closed we delete or return its data as agreed with the organisation that owns it.

Your rights

Depending on where you live you may have the right to access your personal data, to have it corrected or deleted, to object to or restrict how it is processed, and to receive a copy in a portable form.

Much of this is available directly in the product: you can see and delete your own conversations, and an administrator can remove a member and their data. For anything else, write to support@mantaq.ai and we will respond.

In most cases your employer or the organisation that owns your workspace decides what goes into Mantaq and why. Where that is so, they are the data controller and we process on their behalf, so requests may need to go to them. We will help.

Removing access

You can disconnect a Google account at any time in Mantaq under Admin, then Existing Connectors, then Google Account, then Unlink. This deletes the stored refresh token immediately, and Mantaq can no longer read that account's data.

You can also revoke access directly from your Google account at myaccount.google.com/permissions, which takes effect regardless of anything done inside Mantaq.

Other connected sources are removed the same way, from the admin area. Removing a connection ends Mantaq's access to it.

Children

Mantaq is a workplace product and is not intended for children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, contact us and we will delete it.

Changes to this policy

If what we do with your data changes, we will update this page and the date at the top before the change takes effect. Where the change is significant we will tell workspace administrators directly.

Contact

Questions about this policy, about data we hold, or to exercise any of the rights above: support@mantaq.ai.