Google User Data Privacy Supplement

Effective date: October 28, 2026

This supplement is part of the AIVane Privacy Policy. It explains how AIVane accesses, uses, stores and shares information received from Google APIs. AIVane is an independently operated software product. Contact support@aivane.net for privacy questions, access or deletion requests.

Google sign-in is separate from Google Sheets access

Signing in with Google provides basic account information to sign you in or create and link your AIVane account. Signing in does not grant access to Google Sheets, Google Drive, Gmail or contacts. The Privacy Policy describes the sign-in information AIVane receives and stores. Connecting Google Sheets requires separate, optional authorization on Google's consent page in your browser. AIVane never receives your Google password.

Permissions and spreadsheet data

By default, Google Sheets connections request https://www.googleapis.com/auth/drive.file. AIVane uses this permission to read and write spreadsheets you choose with Google's file picker and spreadsheets AIVane creates for you. This permission does not grant access to your other Drive files. AIVane does not list or search your Drive.

In internal and invited desktop builds, you can explicitly choose Grant full spreadsheet access for an existing connection to open spreadsheets by link without selecting each one in the picker. This requests the additional sensitive permission https://www.googleapis.com/auth/spreadsheets, which allows viewing and editing all your Google Sheets. AIVane uses it only for spreadsheets specified in your automations and access checks you request; it does not open other kinds of Drive files. Access depends on the permissions Google actually grants. This option is disabled in public desktop builds until Google verification is complete. Google may show an unverified-app warning during testing. Organization connections currently request drive.file only and do not offer this additional authorization.

AIVane reads the connected account's email address, display name and Google account identifier from Google Drive to identify the account. It reads spreadsheet identifiers, sheet names, table structure and cell values, and creates or updates spreadsheets, only as needed for the automation you or your organization configure or an access check you request. Connection metadata includes the account identifier, granted permissions and connection status. For organization connections, AIVane also records the identifiers of spreadsheets selected in the picker to explain access-check results.

Connections on your computer

In the desktop app, you can add a Google account under Connections. The connection details and refresh token stay on your computer; AIVane's servers do not receive these local connection tokens. The refresh token is stored in AIVane's data folder in secrets/connections-secrets.json. AIVane does not encrypt this file. It relies on operating-system file permissions, so local administrators, other software with sufficient permissions and backup software may be able to read it. Short-lived access tokens are kept in memory.

When an automation runs on your computer, spreadsheet data goes directly between your computer and Google. Run results, recordings, screenshots and automation files can contain that data and remain locally until you delete them. Your workflows can send data to destinations you configure, and your backup or synchronization software may copy local files. The Desktop Privacy Policy describes local storage and removal.

Organization connections for cloud runs

In an organization with AIVane Cloud access, an organization administrator can connect a Google account at app.aivane.net. The organization's automations can then use the selected connection in cloud runs, including configured scheduled runs while your computer is off. Cloud connections are available only to organizations with cloud-run access.

AIVane's servers store the refresh token encrypted with AES-256-GCM and bound to the organization and connection. The refresh token stays on AIVane's servers. A cloud run's isolated environment receives a short-lived Google access token through an authenticated interface bound to that run, after membership, entitlement and connection checks. The administrator's single-use picker page also receives a short-lived access token in page memory to open Google's picker. Tokens are not placed in page URLs, run records, logs or diagnostic reports.

Cloud runs send spreadsheet data between the isolated run environment and Google to carry out your automation. The account service and cloud run storage are hosted in the United States; hosting and cloud execution providers process data needed to provide these features. Results and screenshots are deleted from AIVane's cloud run storage 30 days after the run ends. The record that a run occurred and its billing record remain. Copies downloaded to your computer remain until you delete them.

Diagnostic reports, support and session replay

While Send usage and error reports is on, automatic diagnostic reports can be sent as described in the Desktop Privacy Policy. In desktop builds with Google Sheets connections, reports for runs identified as using Google Sheets omit the run events, non-screenshot run artifacts and run-record result fields. This is not complete removal of Google data: the automation, input values other than password-like inputs, status, error and screenshots can remain. Screenshots can show spreadsheet values entered into a page. Older installed versions may have different reporting behavior; review the policy included with your installation.

A support report you choose to send can include spreadsheet content in its runs, automations, recordings and AI conversations. You can review the report before sending it. Saved connection tokens are removed from diagnostic and support reports. Reports are stored on AIVane's US server and deleted 30 days after receipt, or earlier on request; limited ticket metadata remains. Support staff may access reports from outside the United States and may use third-party AI tools to analyze the report you authorize. The Desktop Privacy Policy describes report contents and the email providers used for support notices.

While Send usage and error reports is on, session replays sent to PostHog Cloud US can capture spreadsheet content shown in the AIVane window, including run results. Turning this setting off in Settings › About stops reports and replays. Replays follow the analytics retention described in the Privacy Policy; the 30-day run-storage limit does not apply to them. Contact support to request deletion.

Optional AI processing and retention

Spreadsheet data is sent as AI task context when you ask the AI about a run or automation containing it. If you configure your own provider, requests go to that provider under its terms. Workflows that explicitly call an AI service send the data you configure for those steps.

AIVane Hosted AI sends requests through AIVane's service to DeepInfra, Inc. The specific models can change. DeepInfra's data-privacy documentation states that standard inference inputs and outputs are processed in memory, deleted after the request and not used for training; operational metadata is retained. AIVane's current Hosted AI routes use this service. The Privacy Policy describes the provider's processing locations. Retired provider routes are disabled; tasks pinned to them cannot continue.

AIVane records Hosted AI requests, including the instructions and context sent to the model, its response, the sending account and device, timing, model used and credits charged. Request and response content can include Google spreadsheet data from your requested AI task. This content is retained for 30 days, then the retention job deletes the request and response files and response previews. Request metadata, including identifiers, timing, model and usage, remains, along with separate account, settlement and billing records, for their stated purposes. Only AIVane's operator can read request content in the administration system, and only to handle your support request or a security issue.

Limited Use

AIVane'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.

AIVane uses Google user data only to provide or improve the user-facing features described here. It does not sell Google user data, use it for advertising, transfer it to data brokers or surveillance services, use it to determine creditworthiness, or use it to develop, improve or train generalized AI or machine-learning models. Transfers are limited to providing these features, handling security or abuse, complying with applicable law, or a merger or acquisition with your explicit prior consent. People at AIVane access Google user data only with your affirmative permission for specific data, such as a support report you choose to send, when necessary to investigate a security issue or abuse, or when required by law. Hosted AI inference data is not used for training by the current provider as described above.

Disconnecting and deleting data

Disconnecting a local desktop connection calls Google's revocation endpoint and deletes its saved tokens. For an organization connection, Disconnect deletes the stored refresh token and clears AIVane's token cache for that connection without calling Google; it does not revoke the same account's other connections. The separate Revoke at Google action requires confirmation and revokes that Google account's authorization across the AIVane Google project, which can affect other organizations and local desktop connections. A token already issued by Google may remain valid until Google expires or revokes it.

You can also remove AIVane's access in your Google Account settings. Spreadsheets that automations created or changed remain in your Google Drive. Disconnecting does not erase previous run results, support reports, AI request records, replays or backups; the retention periods and deletion choices above still apply. Delete local files and backups you no longer need, or contact support@aivane.net to request deletion of an organization's stored connection, cloud run results or other personal data held by AIVane. We may verify your identity and retain records required by law.