Privacy Policy

When you connect your Google account, Thread requests access to:

• Gmail — to read, send, and manage your email threads on your behalf.
• Google Calendar — to view, create, and update calendar events on your behalf.

These permissions are granted via Google OAuth 2.0 and can be revoked at any time from your Google Account settings.

• To generate your AI Daily Brief and smart context summaries.
• To suggest replies, meeting prep notes, and follow-up reminders.
• To display your inbox and calendar within the app.
• To queue and approve email and calendar actions on your behalf.

We do not sell, share, or use your email or calendar data for advertising purposes.

The Thread Chrome extension adds two features on top of the web app: Captain Thread (an on-page assistant) and a Google Meet copilot (live notes and transcription). Here is exactly what each one reads and sends.

Captain Thread runs on the pages you visit so it can respond when you select text, draw around part of a page, or open it from the right-click menu.

• It only reads page content when you take one of those actions — it does not continuously scan or log the pages you browse.
• The selected or circled text, and the page's URL and title, are sent to the Thread API to generate an answer. No screenshots are taken; drawing a shape reads the text underneath it from the page, not a captured image.
• Page content is never used to train any AI model.

Meet copilot only activates on meet.google.com, and only once you choose to start or join a call with Thread listening in.

• With your permission, it captures the call's audio (via the Chrome tab-capture permission) and your microphone, and sends short voice clips to Gnani for live, multilingual transcription.
• Transcripts are stored against your Thread account so the agent and meeting notes can use them later — the same way a meeting recorded through the web app is stored.
• Thread never joins or records a Meet call without you starting it from the extension.

What stays on your device: the extension stores your sign-in token and a few preferences (like whether Captain Thread is on for a site) in Chrome's local extension storage, set to be unreadable by web pages. This never leaves your browser except as part of authenticated requests to the Thread API.

Thread caches a limited snapshot of your recent threads and events in a secure database to provide fast, offline-capable views. This cache is tied to your account and deleted when you disconnect your Google account.

AI processing (summaries, suggestions) is performed via the OpenAI API. Email content sent to OpenAI is used solely to generate responses for you and is not retained by OpenAI beyond the API request per their API data usage policy.

• Google APIs — Gmail, Calendar, Drive, Docs, Sheets, Meet, Forms, Slides and Classroom access via OAuth 2.0, only for the apps you connect.
• OpenAI — AI summaries, replies and the Thread agent.
• Gnani — live, multilingual speech-to-text for Meet calls and voice input, used only when you record or speak into Thread.
• Vercel and Render — hosting and deployment for the web app and API.

You may at any time:

• Disconnect your Google account from the Settings page.
• Turn off Captain Thread for any site, or uninstall the Chrome extension entirely, from chrome://extensions — this immediately stops all page reading and Meet capture.
• Request deletion of your cached data and meeting transcripts by contacting us.
• Revoke Google permissions from myaccount.google.com/permissions.

For any privacy-related questions, please contact us at ishaansatapathy09@gmail.com.