How your data is handled
What Mantaq stores, what it does not, and who can reach it. Written to be checked rather than skimmed.
The short version
Fetched, not copied
Search Console and Analytics figures are requested when a question needs them and used to answer it. They are not copied into a separate store or search index, and they are not retained once the answer has been produced.
One credential, encrypted
The only Google data kept is the credential that maintains the connection, plus the account's email address and the name your team gave it. The credential is encrypted before it is written to disk, with a key held separately.
Never used for training
Google user data is not used to train, retrain or improve any AI model, and it is not used for advertising or profiling.
Who can reach a connected account
A connected Google account is available to everyone in your Mantaq workspace, which is what lets a team work on shared client accounts. Nobody outside the workspace can reach it.
Connecting and disconnecting are administrator actions. An ordinary member can ask questions about a linked account but cannot add or remove one.
Connect and disconnect Google accounts, see which are linked, remove any of them.
Ask questions about any linked account. Cannot add, change or remove a connection.
No access of any kind.
What is in place
The permissions requested from Google carry no write capability, so there is no write path to restrict.
Stored Google credentials are encrypted at the application level, not only by the disk underneath them.
Working tokens are requested from Google as needed and held in memory only. They are never written to disk.
No Google credential is sent to the browser, written to logs, or returned by any API the product exposes.
The linking endpoints verify the caller is a workspace administrator before doing anything.
Unlinking deletes the stored credential at once. Access can also be revoked from the Google account itself.
Traffic to Mantaq is served over HTTPS, and calls to Google APIs go over TLS.
Mantaq can read no Google property that the connected account could not already read.
Model usage and cost are recorded per person, so an administrator can see activity across the workspace.
Found a problem?
If you believe you have found a security issue in Mantaq, write to us and we will get back to you. Please include enough detail to reproduce it, and give us a reasonable chance to fix it before publishing.