Thirp

Privacy: Thirp for Google

This notice covers Google user data for Thirp's Google connectors. Each connector has its own section below. Sheetbridge for Google is the current one. For Sheetbridge for Google, Google's consent screen shows Thirp Sheetbridge. It is not a privacy notice for a hosted multi-tenant Thirp Organization that stores your spreadsheets.

Last updated: October 16, 2026

Privacy · Commitments · Sharing and disclosure · Sheetbridge for Google · What is accessed · Why · Data protection · Where tokens live · Retention · Deletion and revoke

Commitments for every Thirp for Google connector

Thirp Sheetbridge's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Thirp does not sell Google user data. Thirp does not use Google user data for advertising. Thirp relays the agent's requests and results in transit and does not store sheet contents. The Google token never leaves the user's computer. Results go to the AI agent you chose to connect, for example ChatGPT.

Thirp never uses your Google data to train AI or passes it to anyone who does. When you direct an AI agent to use your data, the agent sends it where you ask, under that agent's own terms.

The pack calls Google’s APIs from the machine where you installed it.

You can also revoke Thirp Sheetbridge under your Google Account’s third-party app access. For site/form data, write privacy@thirp.net as described on the Privacy page.

Sharing and disclosure

Thirp sends Google user data to the AI agent you choose to connect, at your direction, and doesn't share it with anyone else. Google user data is disclosed only if required by law.

Sheetbridge for Google

What is accessed

When you choose Connect Google in the Sheetbridge for Google pack, Thirp Sheetbridge requests access to:

Why

So an authorized agent can work on your sheets through a pack you run on hardware you control — read and update cells in a sheet you point it to by URL, and create new spreadsheets — without opening an inbound port for that path.

Data protection

Production connections between the Agent, the caller and the Broker use TLS 1.2 or newer, with server certificates verified. Production Brokers refuse to run without TLS.

The Broker ends TLS on each hop and relays your application data as opaque bytes. It reads only Thirp's own framing and control messages, holds data in memory only while relaying it, and never writes payloads to disk.

Logs record connection metadata such as ids, timestamps, service names, remote address and error reasons. They never contain request or response bodies, and they never contain credentials in readable form: tokens appear only as a short hash or 'set'.

Where tokens live

OAuth tokens for your Google account are stored only on that machine. On Linux and macOS they live at ~/.config/thirp/sheetbridge-for-google/google.json with file mode 0600. On Windows they live at %USERPROFILE%\.config\thirp\sheetbridge-for-google\google.json, protected by the user profile's permissions. Thirp does not keep a copy of those tokens as a hosted Google-data store for this product.

Retention

Thirp does not store sheet contents. Google tokens stay on the computer where you installed Sheetbridge for Google — the file under Where tokens live — until you disconnect Google or delete that file.

Deletion and revoke

Disconnect Google in the pack and delete the local token file on that machine.