Privacy Policy

This policy describes how SoloKeeper collects, uses, stores, shares, and deletes personal data, including data used by its Google integrations.

Effective date: Last updated:

Back to home Google data use

1. Scope and contact

This policy applies to the SoloKeeper product and service and to personal data processed through its account, workspace, support, and integration features.

Privacy requests: privacy@solokeeper.app . General support: support@solokeeper.app .

2. Data we process

  • Google Sign-In account data: Google account identifier, name, email address, and profile data returned through the openid, email, and profile scopes.
  • Workspace data entered in SoloKeeper, including calendar events, session details, client records, payment tracking, templates, settings, and analytics inputs.
  • Gmail message metadata and content loaded with gmail.modify. The separate SoloKeeper Gmail application handles Gmail tokens and message data. The main application sends it client names, email addresses, and display preferences; it receives no Gmail tokens, messages, connection status, or counts in return. SoloKeeper does not download Gmail attachments.
  • Google Docs OAuth tokens and connection metadata, the URL and identifier of a selected template, its title, and placeholder configuration derived from that template. The full document body is read on the server when requested but is not persisted by SoloKeeper.
  • Technical and security data such as request metadata, browser error reports, and operational diagnostics. These records are not intended to contain Gmail message data.
  • Support messages and privacy-request correspondence sent to the contact addresses.

3. How data is used

  • To authenticate users and maintain SoloKeeper accounts.
  • To provide the scheduling, client, payment, template, inbox, and analytics features.
  • To perform the Gmail and Google Docs actions a user requests and to show connection status.
  • To operate, troubleshoot, protect, and improve the reliability of the service.
  • To answer support and privacy requests and meet applicable legal obligations.

4. Google user data and Limited Use

Google Sign-In is used for account access. Gmail is connected separately and its tokens and messages are excluded from the main SoloKeeper server. Google Docs is another separate connection: SoloKeeper requests drive.file, stores the resulting OAuth tokens on the server, and uses them only for files the user selects through Google Picker or that SoloKeeper creates from those files.

SoloKeeper does not sell Google user data, use it for advertising or credit decisions, or use Google Workspace API data to develop, improve, or train generalized or non-personalized AI or machine-learning models. Google user data is used only to provide or improve the user-facing features described here and on the Google data use page .

SoloKeeper's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements. This applies to raw Google data and data derived from it.

5. Storage and retention by category

  • Gmail token and message data: handled by the separate Gmail application. Refresh tokens are encrypted in its own storage while connected. Disconnecting Gmail revokes access and removes the stored connection; closing the SoloKeeper tab does not disconnect it.
  • Google Docs tokens: kept in SoloKeeper's server-side primary storage while the Docs connection is active. A successful Docs disconnect revokes the current access token and removes the local connection record, including access and refresh tokens.
  • Google Docs content and derived template data: the document body is processed transiently when placeholders are synchronized and is not stored. The selected document URL and identifier, template title, placeholder keys, their selected SoloKeeper data sources, and any user-entered starting values are stored until the user deletes the SoloKeeper template or completes an account/data deletion request. Generated document copies remain in the user's Google Drive until the user deletes them there.
  • Account and workspace data: kept in primary storage while the account is active. SoloKeeper currently has no self-service account-deletion control or automatic post-closure purge; deletion is handled through the verified request process below.
  • Backups: deleted data may remain in encrypted, access-controlled backup storage until the backup expires. Current operational retention is up to 48 hours for hourly logical backups, 30 days for daily backups, 84 days for weekly backups, and 5 days for new pre-deployment volume snapshots.
  • Support and operational records: kept while needed to resolve the request, investigate an incident, operate the service, or meet a legal obligation. The application repository does not implement a fixed automatic purge period for these records.

6. Sharing and service providers

Server-side data may be processed by providers used for hosting, backups, error monitoring, authentication, and Google API access when needed to operate or protect SoloKeeper. Gmail tokens and messages are excluded from the main SoloKeeper server. The separate Gmail application's hosting and Google API services process Gmail data. SoloKeeper does not sell personal data or disclose Google user data to advertising platforms, data brokers, or information resellers.

7. Disconnecting integrations and deleting an account or data

  1. 1. Disconnect Gmail or Google Docs from Settings to stop future access. You can also revoke SoloKeeper from your Google Account permissions.
  2. 2. To delete a SoloKeeper account or request deletion of specified data, email privacy@solokeeper.app from the Google email address linked to the account. Identify whether the request covers the entire account or specific data.
  3. 3. SoloKeeper will reply to verify account control and confirm the requested scope. Deletion begins only after the user confirms that reply. Eligible account, workspace, template, and Google Docs connection records are then manually removed from live storage.
  4. 4. Backup copies expire on the schedules above. Deleting a SoloKeeper account does not delete Gmail data or documents in Google Drive; those remain under the user's control in Google services.

8. Rights and choices

Depending on applicable law, users may have rights of access, correction, erasure, restriction, portability, objection, and withdrawal of consent, and may have the right to complain to a supervisory authority. To make a request, use the privacy contact above.

9. Security, transfers, and updates

SoloKeeper uses HTTPS in production, restrictive browser security headers, access controls, environment-managed application credentials, and separation of Gmail data to reduce exposure of personal data. No method of storage or transmission eliminates all risk.

SoloKeeper and its service providers may process server-side data outside the user's country. Applicable transfer requirements depend on the operator and provider contracts; this policy does not claim a specific transfer mechanism that the repository cannot verify.

This policy will be updated when the service's data practices change. The Last updated date identifies the current published text.