Privacy Policy

Overview

TalkToTextly is a browser-first transcription tool. Most audio is processed on your device using in-browser AI. For selected higher-risk mobile sessions, TalkToTextly may show a visible notice and offer a guarded remote transcription worker when that worker is healthy and the file, language, size, and duration are supported.

This policy explains what limited product, analytics, advertising, and browser-stored data may still be involved when you use the site.

What data we process

Audio and transcription content

In the local browser path, your audio file stays in your browser during transcription. We do not send the recording to TalkToTextly servers for processing, storage, or manual review.

In the remote-worker path, after you continue past the visible notice, your browser uploads the selected audio file to the transcription worker over HTTPS. The worker returns the transcript to your browser and removes temporary audio and transcript files after completion or error. Worker logs are metadata-only and must not include audio, transcript text, file names, or multipart request bodies.

Browser-stored data

If you use features like transcription history, language preferences, or consent settings, that information may be stored locally in your browser using localStorage or similar browser storage.

Usage and reliability data

We may collect limited analytics and diagnostics data such as page views, device/browser type, feature usage, performance timings, and error events. We do this to keep the product working, measure reliability, and improve the experience.

Advertising data

We use Google AdSense to support the free product. Depending on your consent choice and Google’s policies, Google and other advertising partners may use cookies, web beacons, and similar identifiers to collect or infer data such as page context, browser/device details, IP address (or IP-derived region), advertising identifiers, and ad interaction events.

For details, see How Google uses data when you use our partners’ sites or apps.

How we use data

• To run transcription locally in your browser
• To route supported high-risk mobile transcription attempts to a guarded remote worker after a visible notice, when enabled and healthy
• To load model files and static assets required for the app to function
• To monitor errors, performance, and product reliability
• To measure aggregate product usage
• To serve ads that help keep TalkToTextly free
• To respond to support requests you send us

Third-party services

• Google AdSense — advertising
• Google Analytics — aggregate analytics and measurement
• Sentry — error monitoring and debugging
• Hugging Face — model delivery to the browser
• TalkToTextly remote transcription worker — optional high-risk mobile transcription processing
• AWS Amplify / CloudFront — static hosting and delivery

Cookies and consent

TalkToTextly uses essential browser storage for site behavior, and we ask for your choice before enabling ads and analytics measurement. You can continue with essential-only functionality or accept ads and analytics.

If you accept advertising, ad partners may set or read cookies and similar technologies (including web beacons) to measure ad performance, frequency, fraud prevention signals, and ad relevance.

You can also clear locally stored transcription history, settings, and consent state from your browser at any time.

Security

• HTTPS is used for the site and third-party requests
• Audio transcription happens locally on-device unless you continue after a visible notice for a supported high-risk mobile attempt
• No account is required to use the core tool
• We minimize telemetry and avoid sending audio or file names in analytics events

Your choices

• Use essential-only site functionality instead of ads/analytics consent
• Clear browser storage to remove local history and preferences
• Contact us with privacy questions or deletion requests for support emails you sent us directly