Privacy Policy
Last updated: August 23, 2026
Speech to Text Converter turns speech or selected media into text. This policy describes what the Chrome extension and its public support pages process, why they process it, and what is sent to service providers.
Speech, text, and local storage
- The extension requests microphone access during its permission preflight and when you start recording. A preflight stream is stopped immediately and is not used for recognition. In browser recognition mode, recorded audio is handled by the browser's Web Speech service under the browser provider's terms.
- Recognized text, history, language, feature preferences, and optional AI backend settings are stored locally in your browser. You can delete history in the extension; uninstalling the extension removes its local storage according to browser behavior.
- The extension reads and updates the focused text field only to insert or undo dictated text. Existing page content is not sent to analytics.
YouTube caption downloads
When you explicitly request a YouTube transcript, the extension sends the video URL directly to YouTube and retrieves available video metadata and caption text using your browser's current YouTube session. YouTube can process connection, browser, and cookie data under its terms. The extension does not download the video's audio, send it to our AI backend, or add the downloaded caption text to extension history. The video URL, title, and caption text are not included in analytics; the generated TXT file is saved through your browser. To initialize YouTube's caption track, the extension can briefly open and close the requested video in an inactive browser tab.
Optional AI and subscription actions
When you explicitly choose AI recognition, file transcription, cleanup, or summarization, the selected audio, media file, or text is sent to the configured AI backend to perform the requested action. Soniox processes submitted audio; DeepSeek processes text submitted for correction or summarization. AI account sign-in uses an email code through Monetize; the account's session is stored in extension storage and used to verify subscription access. The backend stores account email, subscription state, usage counters, jobs, and results. Local audio is removed after processing, and provider-file deletion is requested with retries; results expire after the configured retention period (seven days by default). A submitted job can continue after the extension closes. Desktop notifications contain generic status rather than transcript text. Checkout and the customer portal use the signed-in account with the billing provider. Account, session, audio, text, and custom backend values are never included in analytics or error telemetry.
Minimized product analytics
The extension uses Amplitude to measure feature usage and reliability. Events can contain a pseudonymous SDK identifier, extension version, action or outcome, language, recognition engine or model, duration and text-length counts, and one allowlisted interface category:background, side-panel, popup,on-site, or permission.
Analytics does not include visited hostname, URL, path, referrer, transcript, audio, file name, email, access token, custom backend URL, or raw error message. Automatic IP address, city, country, region, device, browser language, operating-system, referrer, and campaign properties are disabled in the analytics clients. The public Amplitude browser project key identifies the destination project and is not an authentication secret.
Error reports
In production, unexpected failures can be sent to Sentry with the error type and a minimized code stack. The client disables default PII and removes raw messages, user data, request data, browser context, breadcrumbs, extra fields, frame context, full paths, and URL query or fragment values before sending. Expected microphone permission and device outcomes are sent to analytics only as stable categories.
Public pages and feedback
The public install and privacy pages do not run product analytics or session replay. The help, rating, and uninstall pages embed Google Forms. Loading a form sends a browser request to Google, which can process connection, browser, and cookie data under its terms. Form responses and optional contact details are sent only when you submit them.
Sharing, sale, and use limitations
Data is shared only with service providers needed to deliver a feature you request, operate minimized analytics, process payments, or diagnose unexpected failures. We do not sell user data, use it for personalized advertising, or transfer it for lending or credit decisions. Human access is limited to support you request, security and abuse prevention, legal requirements, or aggregated and de-identified analysis.
Use of information received from Google APIs complies with theChrome Web Store User Data Policy, including the Limited Use requirements.
Questions and deletion requests
Use the support form for privacy questions or deletion requests. For local extension data, delete history in the extension or uninstall it from the browser.