What Threadglance reads, stores and cannot do.
· Controlled pilot
Privacy summary
Provider permissions
Microsoft Mail.Read and Google gmail.readonly permit broad mailbox reading. Threadglance limits ordinary use to bounded Inbox data. Optional Spam Watch reads a small recent Spam or Junk sample only after you turn it on for a mailbox. The optional Sent Items writing profile is Outlook-only and starts only when you request it.
What it cannot do
It has no provider permission to send, delete, move, label or mark messages. Attachment presence may be shown, but files are not fetched, opened or analysed.
Processed briefly
A bounded Outlook preview or Gmail snippet and limited message details are processed to produce the inbox analysis. Raw preview or snippet text is not retained in the Threadglance database.
What is stored
Sender, Reply-To address, subject, timestamps, summaries, reply status, category corrections, caution signals, suggested drafts, optional draft preferences and limited operational records may be stored.
Exactly what the providers permit
Microsoft grants the application delegated Mail.Read permission after you consent. Ordinary checks are restricted by the application to selected Inbox message fields. If you turn on Spam Watch for a mailbox, a check also reads no more than 10 messages from the Junk folder received in the previous seven days. Microsoft access tokens are kept in an encrypted server-side token cache and are not returned to the browser.
Google grants gmail.readonly together with basic account identity after you consent. Google classifies gmail.readonly as a restricted scope that can read messages and settings. Threadglance does not call Gmail settings, send, draft, modify or attachment-content endpoints: ordinary checks request Inbox message identifiers, the selected From, Reply-To, Subject and Message-ID headers, labels, timestamps, attachment presence and a bounded Gmail snippet. If you turn on Spam Watch, a check uses the same selected fields for no more than 10 Spam messages from the previous seven days. Other non-Inbox history changes receive an identifier-and-label-only check and are not fetched for headers or snippets. The offline refresh token is encrypted server-side and is not returned to the browser.
What remains after analysis
- Processed for analysis
- Sender, Reply-To address where supplied, subject, timestamps, attachment indicator and either a bounded Outlook body preview or Gmail snippet. If enabled, the saved time zone and optional owner-provided facts may be included for draft wording only.
- Stored by Threadglance
- Limited message details and derived results such as summaries, reply decisions, caution signals, missing-information prompts and suggested drafts. Optional per-mailbox draft preferences may store a time zone, name, country or region, age and literal signature until you clear them or disconnect. Message records and their derived results are kept for up to 30 days from the message date; scan history is kept for up to 30 days.
- Category corrections
- If you confirm or change an email category, Threadglance stores the fixed category, the original automated category, a one-way message-version fingerprint and limited analysis provenance. The change applies only to that email version: it does not alter Outlook or Gmail or teach future classifications. It does not store your correction as free text or use it to train a shared model. The correction is deleted with its message record.
- Optional Spam Watch
- Spam Watch is off by default for every mailbox. When enabled, each check reads at most 10 recent Spam or Junk messages from the previous seven days. Only new or changed content uses analysis. Links and attachments are not opened, and no reply draft is created while the message is observed there. Turning Spam Watch off deletes its stored Spam Watch message records and derived results without changing the provider mailbox.
- Not stored after analysis
- The raw message body, bounded Outlook body preview or Gmail snippet. Attachments are not fetched or opened.
- Redrafting
- Your current draft, the stored summary and optional style guidance are processed to return a revised draft. Threadglance does not add the edited draft to its database through the redraft endpoint.
- Email-app handoff
- When you choose “Review & send in email app”, Threadglance creates a local mailto link using the provider's Reply-To address when available, otherwise the sender address, plus the subject and your current edited draft. Nothing is sent by Threadglance.
How “Write more like you” works
For Outlook only, and only when you request a refresh, Threadglance reads up to 40 usable messages from Sent Items from the previous 90 days. The message text is used on the server to calculate aggregate signals such as typical length, formality and warmth. Sent bodies, subjects, recipients, message IDs and attachments are not stored in the profile. This feature is not available for Gmail during the named-tester pilot.
Dates, approved facts and signatures
You can save a time zone and, optionally, a name, country or region, age and signature for one mailbox. Saving requires an explicit per-mailbox opt-in checkbox; Threadglance does not populate or enable these details automatically. The time zone supplies today's date and weekday. Saved facts may be used only when a message directly asks for that fact. They are never inferred from mailbox history, an address, an IP location or the selected time zone.
The time zone and optional facts may be sent to OpenAI as bounded draft context during analysis or redrafting. The literal signature is not treated as an instruction and is appended by Threadglance after the model response. You can clear these values at any time; disconnecting the mailbox deletes them.
Where processing occurs
Provides the mailbox data after you approve delegated Mail.Read access.
Provides Gmail identity, Inbox metadata, message headers, labels and bounded snippets after a named test user approves gmail.readonly access. If the user turns on Spam Watch, Google also provides up to 10 recent Spam messages per check through the same permission. Google classifies gmail.readonly as a restricted scope.
Provides sign-in, the database and scheduled-job services.
Hosts the website and server-side worker.
May process bounded Outlook preview or Gmail snippet text, selected message details, stored summaries and draft text when analysis or redrafting is used. If you save draft details, the selected time zone and any optional name, country or age may be included as bounded draft context. The literal saved signature is appended by Threadglance after the model response. At the last documented check on 2 October 2026, the configured OpenAI project had organization data sharing for model improvement disabled. Threadglance does not use connected-mailbox content to train a shared model, and requests set store: false so Responses application state is not deliberately stored. Zero Data Retention is not enabled; standard abuse-monitoring logs may retain customer content for up to 30 days. The project control must be rechecked before each pilot expansion.
When branded sign-in delivery is enabled, Resend receives the sign-in recipient address, one-time-code email content and delivery metadata. When the separate deletion-review notice is enabled, Resend receives the named operator address, random deletion request ID, workflow status, bounded error code, operational timestamps and protected recovery path. That notice contains no deleted user email, account identifier, mailbox details, message content or credential. Ireland is the sending region only; Resend stores email and log data in the United States for 30 days. Open and click tracking must remain disabled.
When bot protection is enabled for sign-in, Turnstile processes browser and security signals such as IP address, TLS fingerprint, user agent, site key and origin. Threadglance passes the single-use challenge result to Supabase Auth for validation and does not send mailbox content or reply drafts to Turnstile.
The production deletion ledger uses a dedicated Cloudflare Worker and KV namespace to store random deletion request and event IDs, status, timestamps, a checksum and the Supabase Auth owner UUID encrypted with AES-256-GCM. The encrypted UUID remains pseudonymous personal data, but Cloudflare receives no decryption key, email address, mailbox content or provider token. An unresolved pending tombstone is retained until deletion is resolved. After completion, the pending and completion pair expire after up to 400 days and exact retries do not extend that date. This controlled-pilot period combines the current seven-day managed-backup window, one annual recovery-control review cycle and a 28-day exceptional recovery and advice margin; it is an internal policy, not a statutory requirement, and must be reviewed before general release. Historical decryption-key versions remain only in Vercel while an event still needs them.
Google Limited Use
Threadglance's use and transfer of information received from Google Workspace APIs adheres to the Google Workspace API User Data and Developer Policy, including its Limited Use requirements. Gmail data is used only to provide the visible inbox analysis and draft features the tester requests. It is not sold, used for advertising or credit decisions, or used to train a shared or general-purpose model.
Pause, reset or disconnect
- Pause automatic checksKeeps the mailbox connected while scheduled checks stop.
- Turn off Spam WatchStops Spam or Junk checks and deletes their stored Threadglance results for that mailbox. It does not remove or change mail in Gmail or Outlook.
- Turn off writing guidanceStops using the aggregate profile without deleting it.
- Reset writing guidanceDeletes the aggregate writing profile for that mailbox.
- Clear draft preferencesDeletes the saved time zone, name, country or region, age and signature for the selected mailbox. Existing drafts remain until their normal retention ends.
- Disconnect the mailboxDeletes Threadglance's stored provider credential, mailbox address, display name, derived inbox results, saved category corrections, draft preferences, signature, writing profile and scan history. For Gmail, Threadglance also asks Google to revoke the authorization and reports when Google-side revocation could not be confirmed. The immutable provider account identifier remains for a short two-minute safety fence so an older consent callback cannot reconnect the mailbox during revocation, then it is cleared. A minimal internal account record remains for up to 90 days for account integrity and support. This record is pseudonymous, not anonymous: it keeps the Threadglance owner ID, internal record ID, provider and disconnected status, non-content operational settings and counters, and timestamps. It does not keep the mailbox address, display name, provider account identifier, token, email details, results, draft preferences, signature or writing profile after that fence closes.
- Delete the accountOpen Preferences and use “Permanently delete Threadglance”. A recent email-code session, a short-lived one-use challenge and the exact typed confirmation are required. The workflow stops checks, deletes every mailbox connection and saved app result, then hard-deletes the sign-in account and sessions. A content-free status receipt remains for up to 30 days.
Disconnecting or deleting the account does not delete or change email. Microsoft-side consent can be revoked separately in your Microsoft account or by your administrator. Gmail deletion attempts Google revocation after the local credential is removed; if that cannot be confirmed, remove Threadglance in your Google Account permissions. The Google OAuth named-test-user list is operator-controlled and requires separate removal during the controlled test. A legacy raw-email Vercel pilot allowlist entry also requires operator removal when the deletion receipt flags it; database-backed grants are the production access record. Deleted records may remain in encrypted Supabase backups for the active backup window. The independent Cloudflare Workers KV journal is active and records content-free pending and completion events outside Supabase. A restored environment must stay offline until that journal has been replayed and zero remaining application rows, sessions and Auth user have been proved. The ledger endpoint rejects unauthenticated access and an authenticated smoke test returned a signed receipt, but a destructive live account-deletion rehearsal has not yet been run. Read the deletion steps and scope.
Limits of the analysis
No automated analysis can prove that an email is genuine or safe. Threadglance shows evidence and a suggested next step; consequential requests should be checked through contact details you already trust.