Google integrations

Google Sign-In is separate from Gmail and Google Calendar connections. Gmail and Calendar remain paused for public use while verification and security readiness work is completed. A configured OAuth client or successful local test does not mean Google has approved the integration.

Google Sign-In uses openid, email, and profile to authenticate your Flopinio account. Gmail requests gmail.readonly and basic identity scopes for recent inbox thread metadata and message bodies. Flopinio does not send Gmail replies.

Calendar events are read on demand. Event references are stored when you explicitly link or schedule work. Calendar changes use Flopinio's review and approval controls. Disconnecting Flopinio does not delete messages or events in your Google account.

Gmail intake and manual capture work without AI. AI generation and embedding processing are off by default for each Google connection. Only its account owner can opt in after reviewing the disclosure and available providers. Organization administrators cannot consent for someone else.

Processing remains unavailable until the relevant provider routes have been reviewed. Organization-owned keys and external AI clients do not automatically qualify. Changes to disclosed processing can require renewed consent. Withdraw consent from the connection's Google content and AI controls to stop further processing and schedule removal of existing AI and search artifacts.

Captured Google text appears in a read-only source section, separate from editable work. The source stays private unless its owner explicitly shares it with the work record's audience. That audience follows the record's current access permissions. Independently authored work remains separate. A task created from a request inherits its source sections. Sharing those sections uses the original request's audience; viewing them from the task also requires access to that request.

Uncaptured Gmail content expires after 30 days based on message occurrence time. Explicitly captured source sections remain until their target is removed, the source is erased, or Google is disconnected.

Disconnect stops Flopinio access immediately and starts asynchronous erasure of source content and associated AI/search copies. It preserves independently authored work and content-free audit evidence. Check deletion status in Account > Integrations. Historical content that cannot be separated safely requires review and is not reported as successfully erased.

Erasing one source also clears the generated AI and search artifacts that used it, along with any connection-wide context, to prevent in-flight processing from recreating erased content. Other captured sources and the artifacts built only from them remain available.

Google token revocation, active-storage cleanup, the independent deletion journal, and backup expiry have separate verification states. The active-storage cleanup target is 24 hours. A maximum 90-day encrypted-backup retention is a readiness target, not a verified guarantee; existing immutable locks and assessment acceptance must be checked before that promise is published. Restored systems must apply current deletion records before returning to service.

Revoking Google authorization can affect other Google connections in the same Google Cloud project. Reconnect only after local cleanup and token revocation have finished. Flopinio account sign-in identity is retained. Request data deletion or ask about a pending operation at [email protected].

Flopinio follows Google's Limited Use requirements. Google content is not used for advertising or general model training. Human access is limited to the specific consent, security, and legal cases described in the Privacy Policy. Read Privacy, Terms, and the connection disclosure before enabling a feature. Verification or integration availability does not imply a Google partnership or endorsement.