Privacy at Threadly.

This notice describes how the current Threadly early-access service handles information. Public Google signup is not open yet.

What the service uses

Google sign-in provides your account identity. With your permission, Threadly reads Gmail messages relevant to your requests. Calendar access is a separate connection and can include calendar lists, busy times and event details.

How information is processed

The browser extension sends requests and selected message references to Threadly’s service hosted on Amazon Web Services. Relevant email or calendar context may be sent to an AI model through Amazon Bedrock to answer your request. The service checks account ownership and controls external actions.

What is retained

Threadly stores account details, encrypted Google credentials, preferences, conversations, generated drafts and workflow or action records. Gmail is queried on demand; that does not mean generated results or conversation history are never stored. Disconnecting Google removes the stored connection credentials and invalidates sessions. It does not delete all saved conversations or workflow records.

This website

The website stores your chosen light or dark theme in your browser and requests fonts from Google Fonts. Its interactive inbox, calendar and voice examples use fictional data. They do not connect to your Google account or record your microphone.

Your choices

You can disconnect in Threadly Settings or revoke access in your Google account. If you joined the private test, contact the Threadly team through the person who invited you for help with your stored information. A public support inbox is being set up.

Early-access status

The website and extension are available for invited testing. Wider signup, the public support contact and final public-release policies will be announced here when ready. Do not send private email contents through public issue trackers.