Google data use

How SoloKeeper Uses Google Data

This page explains what SoloKeeper accesses from Google, why that access is requested, and what SoloKeeper does and does not do with your Google user data.

Back to home Privacy

1. Google Sign-In

SoloKeeper uses Google Sign-In so users can create and access their accounts with Google. During sign-in, SoloKeeper receives basic Google account information such as your name, email address, account identifier, and profile details needed to authenticate you.

2. Gmail and Google Docs connections

If you explicitly connect Gmail, SoloKeeper requests Gmail access so the app can load message data relevant to your client operations workflow directly in your browser. This supports client-linked inbox review, message-level unread and attention status, attachment-presence display, the SoloKeeper "Need reply" Gmail label, and moving messages to or from the Gmail trash. SoloKeeper does not download attachments. When you choose to write a session notification, SoloKeeper opens a prefilled compose window in Gmail; you review and send the message in Gmail. Gmail access tokens and message data are handled only in the active browser tab; they are not sent to or stored by SoloKeeper's server.

If you explicitly connect Google Docs, SoloKeeper uses per-file Google Drive access to read a Google Docs template you select through Google Picker and extract placeholders such as {{client.name}}. When you generate an invoice, SoloKeeper creates a copy in your Drive and replaces placeholders in that copy. It does not modify the source template.

3. Data SoloKeeper accesses

  • Google account identity data required for account access.
  • Gmail message metadata such as sender, recipient, subject, and timestamps.
  • Gmail message content and attachment metadata when those messages are loaded for the inbox workflow.
  • Recipient, subject, and message draft content used to open a prefilled Gmail compose window at your request.
  • Google Docs content and metadata for templates you select through Google Picker and for invoice copies SoloKeeper creates from those templates.
  • A short-lived Gmail access token kept only in memory in the active browser tab, plus OAuth token and connection metadata stored for the separate Google Docs integration.

4. What SoloKeeper does with Google data

  • Authenticate your SoloKeeper account through Google Sign-In.
  • Show Gmail-linked client messages inside the inbox workflow.
  • Show that a Gmail message has attachments without downloading those files.
  • Open prefilled session-notification drafts for you to review and send in Gmail.
  • Read Google Docs templates, create invoice copies in Drive, and replace placeholders in those copies.
  • Display Google integration state and let you reconnect or disconnect the integration.

5. What SoloKeeper does not do

  • SoloKeeper does not sell Google user data.
  • SoloKeeper does not use Google user data for advertising.
  • SoloKeeper does not inspect or modify unrelated Gmail messages or Drive files, and it does not modify your source Google Docs templates.
  • SoloKeeper does not use Gmail or Google Docs content to train generalized models.
  • SoloKeeper does not send Gmail access tokens or Gmail message data to its server and does not persist them there.
  • SoloKeeper's use of raw or derived data received from Google Workspace APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

6. Revoking access

You can disconnect Gmail or Google Docs from inside SoloKeeper. You may also revoke the app’s access from your Google account permissions page. Revocation can disable Google-powered features inside the app until the account is connected again.

7. Questions or requests

For Google-data or privacy questions, contact privacy@solokeeper.app . For general product support, contact support@solokeeper.app .