SpeakToText

SpeakToText helps people write faster in the Windows apps they already use. A user can speak to create polished prompts, emails, replies, and notes, select text and ask a free-form question about it, or have text read aloud.

Live Assistant is an optional work-session surface for inbox organization, grounded drafts, meeting preparation, reports, approvals, and action receipts. Google access is not required for the core voice typing, read aloud, or highlighted-text features.

Gmail read access lets SpeakToText read only the mailbox content needed for a workflow the user requests, such as reviewing selected messages, classifying inbox work, finding unanswered conversations, extracting action items, or preparing context for a reply.

Gmail compose access lets SpeakToText create drafts and perform a send only after the user has requested the action and the app approval controls permit it.

Google Calendar event access lets SpeakToText review upcoming meetings for preparation and create a calendar event after explicit user approval.

Google Sheets access lets SpeakToText append an approved activity report or business record to the spreadsheet and range selected by the user.

Connecting Google is optional and begins only after the user chooses Connect and completes Google consent. Each connected Google account receives its own connection identifier and account label so work is routed to the account the user selected.

External writes are prepared as pending approvals bound to the exact user, provider account, destination, and action payload. Approval is single-use. A completed provider action produces a receipt, while an uncertain result is marked for review instead of being silently repeated.

Users can disconnect a Google account at any time from SpeakToText. The stored authorization is removed and a Google token revocation request is submitted when available.

Google OAuth tokens are encrypted at rest and are never included in Live Assistant prompts or action receipts. SpeakToText does not sell Google user data, use it for advertising, determine creditworthiness, or use it for generalized model training.

SpeakToText keeps only the minimum operational records needed for account routing, approvals, replay protection, receipts, and user-visible history. Full mailbox threads and raw OAuth tokens are not stored in action receipts.

The SpeakToText Privacy Policy linked below describes Google API Services User Data handling, retention, deletion, and the Google API Services User Data Policy Limited Use requirements.

The public Privacy, Security, Data deletion, Terms, and Contact support pages are available below without signing in. The Privacy Policy URL is the same URL configured on the Google OAuth consent screen.