Last updated: 27 July 2026 · Heurivon Inc.
Heurivon's use of information received from Google Workspace APIs will adhere to the Google Workspace APIs User Data Policy, including the Limited Use requirements.
Specifically, the use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
Heurivon's use of Google Workspace data is limited to providing or improving user-facing features that are prominent in the requesting application's user interface. Heurivon will not use Google Workspace data for any purpose unrelated to providing these user-facing features, for serving ads, for developing, improving, or training non-personalized advertising systems or models, or for selling data to data brokers. Heurivon will only transfer Google Workspace data to others as necessary to provide or improve user-facing features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with prior notice to users. Heurivon will not allow humans to read Google Workspace data unless: the user has provided affirmative agreement to access specific messages or files; it is necessary for security purposes such as investigating abuse; it is required to comply with applicable law; or use is limited to internal operations and the data (including derivations) have been aggregated and anonymized.
Heurivon will not use data received from Google Workspace APIs to develop, improve, or train generalized artificial intelligence (AI) or machine learning (ML) models.
Heurivon sends Google Workspace content to third-party AI providers when required to fulfil a request you make — for example, reading your calendar to answer a scheduling question, or reading a document to summarise it. These providers operate under terms that prohibit using customer data to train or improve their models.
Heurivon does not use, transfer, or sell Google Workspace data — raw, aggregated, anonymized, or derived — to create, train, or improve any foundational or generalized AI or ML model. We do not build datasets from Google Workspace data.
Our current AI subprocessors are listed at heurivon.com/ai-providers.
Where you have connected your own AI provider key, requests are made under your account and your agreement with that provider applies. Every AI provider Heurivon supports operates under terms that exclude customer data from model training by default, at any tier. Some providers additionally offer organization-level settings that permit training — these are disabled by default, and Heurivon cannot verify them on your account. We recommend leaving them disabled. See Section 8 of our Privacy Policy for details.
Heurivon requests access to the following Google Workspace data solely to perform features explicitly initiated by you inside the application:
drive scope) for document indexing, retrieval, and optional file operations. The knowledge-base feature reads only within the specific folder you link; an automated background sync keeps that index current. General Drive agent tools are constrained to a root folder you configure in Settings; when no root folder is configured, those tools can access any file in your connected Drive. Write access is turned on when you connect your Google account, because the granted scope covers both reading and writing; you can turn it off at any time in Settings → Drive. Heurivon writes only when you explicitly ask it to create or update a file. The narrower drive.file scope cannot read pre-existing user files, and drive.readonly cannot perform write operations, so the full drive scope is required.Heurivon does not request or use Gmail API access. Email features in Heurivon use IMAP and SMTP with credentials you supply separately.
Questions about our Google Workspace data practices?
Heurivon Inc.
privacy@heurivon.com
For full details, see our Privacy Policy.