SOLID LOGICAL · BOS

Google Connections Privacy Notice

Updated November 13, 2026

This notice explains how BOS, provided by Solid Logical LLC, uses Google sign-in and Google Calendar. Gmail integration has been removed. BOS does not request Gmail permissions or read or send messages through the Gmail API.

Information you authorize

Google handles sign-in and consent. BOS does not receive your Google password. For sign-in, BOS uses your Google account identifier, verified email address and basic profile information to identify and link your BOS account.

If you connect Google Calendar, BOS stores encrypted authorization tokens so enabled calendar features can work while you are signed out. Calendar access includes calendar identifiers, names, availability and events, and creating, updating and cancelling events for configured business workflows.

How BOS uses this information

BOS uses Google identity information for account access and Calendar information to check availability, manage appointments and business events, synchronize changes and create Google Meet links through Calendar events. Access is subject to the business’s BOS permissions and feature settings. Booking confirmations are delivered through the business’s separately configured BOS email delivery service; Gmail mailbox access is not required.

BOS does not sell Google-connected information, use it for advertising, or use it to develop or train generalized artificial-intelligence or machine-learning models. BOS’s use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and recipients

Connected information is processed in BOS’s hosted services and stored in its business database. The hosted BOS application runs on Render. Google processes authorized identity and calendar operations. Configured email delivery providers process the appointment details needed to deliver confirmations and invitations. Authorized business users can access information their BOS permissions allow. Support access is used where necessary to investigate an issue you report. Information may also be disclosed where required by applicable law.

How we protect Google user data

BOS uses HTTPS with TLS to protect information in transit between your browser and the hosted application and between BOS and Google’s identity and Calendar APIs.

Google Calendar access and refresh tokens are encrypted before being stored in the database, using authenticated encryption (Fernet). The encryption key is held in server-side configuration separately from the stored token records. Google client secrets and token-encryption keys are not included in browser pages or client applications.

Access to Google-connected information requires an authenticated BOS session. Server-side organization checks, tenant filtering and role or section permissions restrict access to the business and functions a user is authorized to use. Calendar connection management is restricted to authorized administrators. These controls also apply to calendar and appointment records that contain sensitive information.

Calendar authorization uses a short-lived, single-use authorization request, a random state value and PKCE to protect the consent callback. BOS requests the permissions needed for its enabled identity and Calendar features. Administrators can disconnect Calendar, and account owners can revoke access through Google Account connections. Support access is limited to the purposes described above.

Retention and disconnection

Calendar authorization credentials are kept while the connection is configured. Appointment and other business records follow the business’s retention and backup requirements; there is no single retention period for every record.

Gmail integration has been retired. The retirement cleanup deletes imported email messages, attachments, raw email files, associated message copies and Gmail integration credentials from active BOS storage. Encrypted infrastructure backups may temporarily retain earlier copies until the hosting provider’s retention window expires (up to seven days). The cleanup runs before the application starts to prevent restored Gmail data from becoming available again. Google sign-in and Calendar data follow the retention practices described above.

You can disconnect Calendar in BOS or revoke permissions in your Google Account connections. Disconnecting removes the stored credentials for that connection and stops future access. Revoking a shared Google project grant can also affect other Google connections and require reconnection. Disconnection does not automatically erase existing business records or backups.

Your choices and contact

Business administrators control enabled calendar workflows and user access. Contact your business administrator about information held in its BOS workspace. For questions, assistance or a request to review, correct or delete information held by Solid Logical, contact craig@solidlogical.com. Requests may need to be coordinated with the business responsible for the records and applicable retention obligations.