Legal & Policy

Gmail & Google API Disclosure

How RepliaOS uses Gmail, Google APIs, and Google OAuth for optional email-related functionality.

Last updated: May 2026

1. Overview

RepliaOS may allow an authorized user or organization to connect a Gmail account using Google OAuth and Google APIs for email-related functionality.

This page applies only to Gmail-related functionality that RepliaOS publicly documents. It does not describe or imply support for Google Drive, Google Calendar, Google Workspace administration, or unrelated Google services.

2. Why Gmail Access Is Requested

When enabled by the relevant organization or user, RepliaOS may request Gmail access in order to:

Authenticate a Gmail integration through Google OAuth
Send user-requested or organization-requested communications through the connected Gmail account
Support configured organization communication workflows that depend on that connected Gmail account

Gmail access is optional. RepliaOS can still be evaluated through its other public materials without connecting a Gmail account.

3. Data That May Be Accessed

RepliaOS may access only the Google account information and Gmail data needed for the specific email-related workflow being used, such as:

Basic authenticated Google account identity information
Sender, recipient, timestamp, and delivery-related metadata
Email content needed to compose, send, or support the requested communication workflow
OAuth access tokens, refresh tokens, and related authorization metadata needed to maintain the connection securely

This disclosure does not mean RepliaOS has unrestricted access to all Gmail content or all Google account data.

4. How Google API Data Is Used

Google API data is used solely to provide the user-facing functionality requested by the relevant user or organization.

RepliaOS's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google API data connected through Gmail is not:

Sold
Used for advertising
Used for retargeting
Used to build advertising profiles
Shared except as necessary to provide the service, comply with law, protect security, or with the relevant user or organization's direction or consent
Used to train generalized AI or machine-learning models

5. Controls, Revocation, and Retention

Connected Gmail integrations are permission-controlled and intended to be used only within the authorized organizational context.

Users may revoke Gmail access through their Google account permissions. Where available, connected integrations may also be disconnected through RepliaOS administrative or integration settings.

OAuth credentials are treated as sensitive data. Access tokens and refresh tokens are protected accordingly, and retained records after disconnection are limited to what is reasonably necessary for operations, security, audit logging, legal compliance, dispute resolution, or enforcement of agreements.

For related information, review the following public pages: