§ i
Connect once
Sign in with Google or Outlook. Thread holds the broad OAuth scope; the apps never do.
§ ii
Grant surgically
Pick the categories and labels. Set expiry, rate, schedule. Preview the matches first.
§ iii
Revoke in a click
Every grant lives in one place. Mute, throttle, or revoke without re-asking the user.
Why Thread
OAuth was never designed to say “only the receipts”. Apps ask for the whole inbox, you say yes, and now an analytics startup reads your therapist's emails. Thread fixes the verb. The grant is specific, signed, revocable, and visible.
The permissions we request, and why.
When you connect a Gmail account, Google shows you a consent screen. These are the scopes on it, in plain words. Thread holds them and then self-limits in code — the grants you write are the real gate, and they are always narrower.
gmail.readonlyRead the mail in your granted scope
Thread reads a message so it can classify it and answer a request an app you authorized is allowed to make. Read-only is the narrowest scope that supports what Thread does today, so it is the one we ask for.
Cannot send, delete, label, or change anything in your mailbox — the scope permits no writes at all.
userinfo.emailSee the address of the mailbox you connected
So your dashboard can show which mailbox a grant belongs to, and so reconnecting maps to the same account instead of silently making a second one.
No profile, no contacts, no photo.
calendarRead and write calendar events — only if you turn it on
Requested on a separate, later consent, and only when you enable the calendar source. Lets a scheduling app see the events you granted and write the ones you allowed.
Not requested when you connect a mailbox. Skipping it leaves mail working.
What we never do with Google data
- Never sold, and never used for advertising.
- Never used to train generalized AI or machine-learning models.
- Never handed to anyone but the specific app you granted, for as long as that grant is live.
- Never read by a human, except when you ask us to debug something, for security, or where the law requires it.
- Message bodies are never written to our database, our caches, or our logs.
Thread's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The full detail is in our Privacy Policy.