Privacy Policy

This policy applies to the Google connection flow at thetothlab.com/connect/google, where a signed-in user can grant The Toth Lab access to one or more of their Google services. It does not create any obligation to connect a Google account — connecting is entirely optional and is something you do deliberately through Google’s own consent screen.

When you connect a Google service, we collect and store only what that requires:

• A Google OAuth refresh token for each service you explicitly grant. A refresh token is a credential that lets us request short-lived access tokens from Google so we can act on your behalf for the services you approved — and nothing else.
• The email address of the connected Google account, stored as a human-readable label so you and our team can tell which account a connection belongs to.
• The email address you sign in with on this site, which identifies the connection as yours.

We do not collect your Google password, and we do not copy your Drive contents. Calendar events are different: your hub shows them, so we keep a copy of the fields it displays (for events, the title, start and end times, and a link back to Google Calendar) in your own install and refresh it from Google. Nobody else’s install can read it.

You connect one service at a time, and each one maps to a narrow Google permission. Here is what we read or write with each, and why:

• Google Calendar, read and write — calendar.events and calendar.calendarlist.readonly. We read the events on the calendar you pick and show them as the schedule in your hub. When you book an appointment from your hub — yourself, or by asking your assistant — we create that event on your calendar, and we can change or remove only events we created. We list your calendars only so you can pick which one to use. We do not create, delete, or share calendars.
• Google Drive — drive.file. The most limited Drive permission. It reaches only files The Toth Lab creates with you or that you explicitly open through us, never the rest of your Drive.

You can grant either of these, or both. Calendar uses a sensitive Google scope.

The refresh token is encrypted at rest using libsodium secretbox (XSalsa20-Poly1305 authenticated encryption) with a master key held separately from the stored data. It is never written to logs and never displayed in our interface.

We use the stored token for one purpose: to mint short-lived access tokens that let Toth Labs call Google’s APIs on your behalf, within the exact scopes you granted, to deliver the work you asked us to do. We use your Google data only to provide the features you connected it for. We do not sell your Google data, we do not use it for advertising, and we do not use it to train AI or machine-learning models. We do not let people read it except as described below.

Each client’s Google data lives in that client’s own install, encrypted and kept apart from every other client’s. Access is limited to that install’s owner, who sees it in their hub, and to the Toth Lab studio operators (Kathleen and Michael Toth) and the studio’s own agent tooling acting on their behalf, solely to carry out the work you authorized. We do not share your Google data or the stored token with third parties, except infrastructure providers that host our application strictly to keep the service running, OpenAI’s API as described below, and where required by law. OpenAI’s API is the one AI provider we send any of it to, in two ways. When you ask the in-app assistant something that needs your calendar, it may send the stored event titles, start and end times, all-day flag, and event link involved. And where search embeddings are on, that same stored calendar text is sent to OpenAI’s embeddings API to build the search index, whether or not you asked a question; OpenAI returns numbers (embeddings) that we keep for search. OpenAI’s API terms do not permit training on it, and we have not opted in to any data sharing. We never send event descriptions, attendees, or Drive contents. If you connect your own AI assistant (for example Claude or ChatGPT) to your account through our connector, it can read your calendar data there; you choose that assistant, and its provider handles what it reads under your account with them. We send nothing to those providers ourselves.

We keep the encrypted refresh token and its account label for as long as your connection is active and you want The Toth Lab to be able to do this work. When you revoke a connection, the stored token is no longer valid for Google’s APIs. Disconnecting in your hub marks the credential revoked and we stop using it, but the encrypted token stays in storage until you ask us to delete it. On your request we delete the stored credential, its account label, and the copied calendar event fields.

You are in control of this connection at all times. To disconnect:

• Disconnect the service in your hub. That stops our access immediately. To have the stored credential and any copied events deleted, email us (below), or remove the app at myaccount.google.com/permissions to cut Google’s side.
• Revoke The Toth Lab’s access directly from your Google Account at myaccount.google.com/permissions. This immediately invalidates the stored token at Google.
• And / or email us at [email protected] to ask us to delete the stored credential, any associated label, and the copied calendar event fields. We will confirm once they are removed.

“The Toth Lab’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.”

We use Google user data only to provide the features you connected it for, we transfer it only to run the service, follow the law, or with your consent, no person reads it except to support you or keep the service secure, and we do not use it for advertising, for sale, or to train AI models.

The Toth Lab is not directed to children under 13, and we do not knowingly collect data from them.

If we change how we handle connected Google data, we will update this page and revise the effective date above.

Questions about this policy or your data? Email [email protected].

The Toth Lab operates as a studio run by Kathleen and Michael Toth; the formal operating entity name is being finalized.