Instinct's Google Workspace integration is one of the best-documented parts of the product because the company's Privacy Policy names the services and explains special rules for Workspace data.
Current official list: Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides, and Google Tasks.
That list applies when a user chooses to link Google Workspace. It does not mean Instinct automatically receives Workspace access for every account.
What Google Workspace data can Instinct receive?
Instinct says it can receive access to:
- Gmail;
- Google Calendar;
- Google Drive;
- Google Docs;
- Google Sheets;
- Google Slides;
- Google Tasks.
The policy also mentions related:
- file metadata;
- message metadata;
- calendar event details;
- other content made available through Google Workspace APIs.
This is broader than a simple "connect Google" button. Depending on the permission scope, Workspace can provide both content and structured context the assistant may use for tasks.
Why would Instinct use Workspace data?
The Privacy Policy says Workspace information is used to provide the service, including so the personal assistant can take actions on the user's behalf, and to personalize the experience.
That can support workflows involving:
- understanding email context;
- recognizing dates and commitments;
- working with files or documents;
- planning around calendar events;
- tracking tasks.
The policy establishes the data and purpose. It does not guarantee the success of every specific workflow.
For task-level evidence, use the Instinct Task Database.
Does Instinct train AI models on Google Workspace data?
Instinct says no for information received directly from Google Workspace APIs.
The policy states that Workspace API information is not used to:
- evaluate AI models;
- fine-tune AI models;
- train AI models;
- improve AI models;
- serve ads, including personalized or retargeted advertising.
This is a specific exception to Instinct's broader privacy language, which says some other user information may be used for model development and improvement.
That distinction is important. A general statement like "Instinct trains on user data" is incomplete unless it also explains the Workspace exception.
See Instinct AI Privacy for the broader model-training policy and the Google Workspace exception.
Can third-party AI providers receive Workspace data?
Instinct says third parties may process Google Workspace information on its behalf to help provide the service, including third-party AI model providers.
The company also states that it does not disclose raw or derived Workspace or Photos API user data to third-party AI services for model training or secondary purposes.
So there is a difference between:
- processing data to provide the user's requested service;
- using that data for unrelated model training or secondary purposes.
The policy permits the first under its stated conditions and says it does not permit the second.
Can I revoke Google Workspace access?
Yes. Instinct's Privacy Policy says users may revoke access by:
- initiating a conversation with the Instinct agent; or
- disconnecting through settings within Instinct's Workspace.
Revoking access changes future connectivity, but users should also understand the separate deletion rule.
Does disconnecting Workspace delete everything Instinct already collected?
Not necessarily.
Instinct's policy says users may request deletion of information collected through Google Workspace APIs, and it explains a Workspace/account deletion path.
The broader privacy section also warns that disconnecting a third-party integration does not automatically delete data previously collected from that integration.
The safe mental model is:
disconnect = revoke access
delete = request removal of already collected/indexed data
Those are different operations.
Is Google OAuth the same as Google Workspace access?
No.
The Privacy Policy separately mentions information received from login integrations such as Google OAuth, including profile and email address.
That is different from granting access to Gmail, Calendar, Drive, and other Workspace content.
A user should look at the permission screen to understand which type of Google connection is being requested.
What permissions should users review?
Before connecting Workspace, check which services and scopes are being requested.
A narrow workflow may not need the same access as a broad personal-assistant workflow. Consider whether the task actually requires:
- Gmail content;
- calendar events;
- files;
- documents;
- tasks;
- write access rather than read access.
The current public Privacy Policy describes categories of access, but the live permission screen is the best place to see the exact scopes requested for your account.
Google Workspace and action risk
Privacy is only one side of the integration.
If Instinct can use connected data to take actions, the user also needs to consider what can happen when context is wrong or incomplete.
Instinct's Terms warn that actions can be incorrect and may not always be reversible.
So for high-impact workflows, verify the result even when the underlying data comes from a trusted Google account.
Frequently asked questions
Does Instinct connect to Google Workspace?
Yes. Instinct's Privacy Policy explicitly describes what happens when a user chooses to link Google Workspace.
Which Google services are listed?
Gmail, Calendar, Drive, Docs, Sheets, Slides, and Tasks.
Is Workspace data used to train Instinct's AI?
Instinct says information received directly from Google Workspace APIs is not used to evaluate, fine-tune, train, or improve AI models.
Is Workspace data used for ads?
Instinct says it does not use information received from Workspace APIs for advertising, including retargeting or personalized advertising.
Can I disconnect Google Workspace?
Yes. The policy describes revoking access through the agent or Instinct Workspace settings. Deleting previously collected data is a separate step.