Google data use

How ReplyFlux uses Google data

Last updated:: October 11, 2026
Effective date:: July 17, 2026

ReplyFlux is a product of TKH Digital LLC. It is an inbox assistant for sales teams that works in Gmail (Chrome extension), Outlook (Office add-in), and the ReplyFlux web app. This page explains how ReplyFlux uses Google Sign-In, optional Google Calendar access, and third-party AI inference.

Google user data

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

ReplyFlux does not use, transfer, or sell Google user data — including raw, aggregated, or derived data — to create, train, fine-tune, or improve foundational or generalized machine learning or artificial intelligence models, whether our own or a third party's.

Google Workspace and Photos user data is used only to provide or improve user-facing features of ReplyFlux that the user requests (sign-in and, if connected, calendar-aware draft suggestions). ReplyFlux does not use that data for advertising, retargeting, credit-worthiness, or lending. ReplyFlux does not sell Google user data.

1. What ReplyFlux does

ReplyFlux reads the currently open email thread on the user's device and matches it with the user's connected CRM records to help draft replies. Supported CRM connections include Salesforce, HubSpot, Pipedrive, Zoho CRM, and Attio.

ReplyFlux creates draft suggestions only. Users review and edit every reply before sending it from Gmail or Outlook. When you ask for a draft or you send a reply, that draft text and the text you send may be stored for up to 30 days, then deleted. Deleting your account deletes that stored text as well.

2. Google APIs ReplyFlux uses

Google Sign-In

Google Sign-In is used only to authenticate your ReplyFlux account. Scopes are openid, email, and profile. ReplyFlux may receive your email address and profile name so you can sign in.

Google Calendar (optional)

When you connect Google Calendar, ReplyFlux requests read-only Calendar API access (calendar.readonly and userinfo.email) so drafts can reference your real availability and upcoming meetings. ReplyFlux never creates, edits, or deletes Google Calendar events.

Gmail API and Google Photos

ReplyFlux does not call the Gmail API or any Google Photos API. In Gmail, the Chrome extension reads the open thread from the page on your device only after you ask ReplyFlux to draft or search. That on-device text is not obtained through a Google Workspace Gmail scope.

3. AI / ML aggregator and models

ReplyFlux does not host or train its own foundation models. User-requested AI features call OpenRouter as an inference gateway. Prompt content is sent only to generate the response for that request.

Platform

Aggregator / gateway: OpenRouter (openrouter.ai), Chat Completions API
ReplyFlux does not send Google user data to any other AI gateway

Downstream inference models

The primary model is configured server-side (default openai/gpt-4o-mini). If that endpoint is unavailable, OpenRouter may try this locked fallback chain:

openai/gpt-4o-mini (OpenAI)
google/gemini-2.0-flash-001 (Google, inference only)
anthropic/claude-3.5-haiku (Anthropic)

An optional, smaller OpenRouter call (openai/gpt-4o-mini) may extract person names from the user's prompt so CRM search can run. The same privacy controls apply.

Configurations that restrict training and retention

Every OpenRouter request sets provider.zdr = true (Zero Data Retention–compatible endpoints only)
Every OpenRouter request sets provider.data_collection = deny (do not route to endpoints that collect prompts for training or non-transient storage)
These two fields are hardcoded in ReplyFlux and cannot be turned off by a client, environment flag, or dashboard override
ReplyFlux does not enable OpenRouter prompt/response logging or “share data for product-improvement” discounts
ReplyFlux does not fine-tune, distill, or continue-train any model on Google user data
OpenRouter may keep non-content operational metadata (for example status codes). Prompt and response bodies are not retained by ReplyFlux for model training

Calendar facts retrieved through the Google Calendar API, and on-device email text the user chose to draft from, may be included in that inference request so ReplyFlux can produce the suggested draft. That is a user-requested feature, not model training.

4. Data sharing and advertising

ReplyFlux does not sell user data.
ReplyFlux does not use Google user data for advertising.
ReplyFlux does not use Google user data to train public, foundational, or generalized AI models.
ReplyFlux only uses Google data to provide user-requested product features, such as sign-in and optional calendar-aware draft suggestions.