Flopinio logoFlopinio
Beta Users and reviewers evaluating Flopinio Google OAuth access

Google Integrations

Learn what Google data Flopinio requests, stores, processes, sends, and deletes when you connect Google Sign-In, Gmail, or Google Calendar.

Explore documentation diagram

Documentation diagram

Google Integrations

Google integrations as a scoped access and review flow. Exact OAuth scopes, retention rules, and deletion instructions remain in the page text.

System Ready
Google integrations as a scoped access and review flow. Exact OAuth scopes, retention rules, and deletion instructions remain in the page text.
On this page
1

Quick scan

Flopinio separates Google Sign-In, Gmail, and Google Calendar so each OAuth flow requests only the scopes needed for the feature being enabled.

Google Sign-In uses basic identity scopes.

Gmail sync uses gmail.readonly to read recent inbox threads for External Inbox triage.

Gmail reply sending is a separate approved action.

Google Calendar events are read live on demand and are not imported automatically.

2

Status

Google integrations are Beta where labeled in the app and public catalog. Gmail intake and Google Calendar actions are available as bounded connected-account workflows; broader Google Docs, Google Sheets, or unattended workspace automation is not part of the current public claim surface.
3

Google Sign-In

Google Sign-In uses openid, email, and profile to authenticate users, link the Google identity to a Flopinio account, and confirm the account email address.
4

Gmail

Gmail sync uses gmail.readonly plus basic identity scopes. Flopinio reads recent inbox thread metadata and message bodies so users can review, route, and convert client emails into Flopinio records.
5

Google Calendar

Google Calendar events are read live when a user opens a meeting surface or asks for events. Unlinked events are not stored, and this flow does not request Google Docs or Google Sheets access.
6

What Flopinio stores

Encrypted access and refresh tokens.

Google account identifiers and provider metadata.

Connection and verification timestamps.

Synced Gmail thread records needed for External Inbox.

Calendar event references created through explicit linking or scheduling workflows.

7

Disconnect and deletion

Disconnect Google from Account or Settings.

Flopinio revokes the Google token where supported.

The connected integration account and synced integration records are deleted from active storage.

Users can request deletion of synced Google data at [email protected].

8

Review boundaries

Flopinio does not silently send Gmail replies or silently create calendar actions. Write-capable actions are approval-gated and recorded through the normal Flopinio runtime and security-event model.

Review privacy details

The Privacy Policy describes Google API Limited Use, retention, and deletion request handling.