Privacy Policy

Overview

FreeTextoSpeech ("we", "our", "us") operates the website freetexttospeech.net (the "Service"). This Privacy Policy explains what information we collect, how we use it, the cookies we and our partners set, and the choices you have. By using the Service you agree to the practices described here.

Information We Collect

Text input: When you use the cloud text-to-speech tool, the text you enter is sent to our servers to generate audio. We do not permanently store your text or the generated audio. Text is processed in real time and discarded after the audio is delivered to your browser. When you use the in-browser (on-device) engine, your text never leaves your device.

Speech-to-text uploads: When you use Audio to Text, Free Speech to Text, or MP3 to Text, the selected audio is sent through our server to Groq for transcription. We do not store the audio or transcript. When you use our shared service, we retain limited usage metadata, such as file size, duration, processing status, account identifier when signed in, and IP address, to enforce daily limits and prevent abuse. Groq states that inference data is not retained by default, except in limited reliability or abuse-monitoring circumstances; its account-level Zero Data Retention setting can disable that temporary retention.

Your own Groq key: If you choose the optional “Use my API key” feature, your key is kept in session storage for the current browser tab and sent over HTTPS to our server when you validate it or request a transcription. Validation checks whether the key can access Groq's Whisper model without transcribing audio. We use the key only to make the requested Groq call. We do not write the key, audio, transcript, or a usage record for that request to our database. Clearing the key or closing the tab removes it from session storage. Groq counts the request toward your organization's Groq quota and applies its policies.

Usage and log data: Like most websites, we and our service providers may automatically collect technical data such as your IP address, browser type, device and operating system, referring pages, the pages you view, and timestamps. This helps us keep the Service stable, prevent abuse, and understand how it is used.

Optional account: Core tools work without an account. If you sign in with Google or an email magic link, we store your email address, display name, and avatar URL (when Google provides one), plus a Google account id when you use Google. We keep you signed in, apply signed-in quotas and features, and (if you are subscribed) send product and marketing emails. We also store a session record tied to an HttpOnly session cookie. Magic-link tokens are stored only as a short-lived hash.

Optional synced product state: Signed-in users may save up to 500 pronunciation replacements and resume up to 100 recent reading positions. Reading sync stores a locally generated SHA-256 document fingerprint, title, route, locale, section, character offset, and playback time. We do not store the document body, uploaded audio, transcript, or speaker embedding in these account-state records. Anonymous users keep equivalent state in browser storage.

Feedback and tool requests: When you use the in-app Feedback or Request a tool forms, we store your message, page URL, and limited technical metadata (such as IP address and user agent). If you check Email me updates, we also store your email (typed in, or your signed-in account email) and may email you from status@freetexttospeech.net about that submission. Cloudflare Email Workers are only used to contact people who opted in. We may also notify the FreeTextoSpeech team at blog.boopul@gmail.com.

Tool not working reports: The one-click Tool not working control emails the team at blog.boopul@gmail.com and stores the page URL plus limited technical metadata so we can investigate outages. It does not collect your email unless you separately submit Feedback with updates turned on.

No account required for core use: You can generate speech without registering. Signing in is optional and unlocks higher limits, the in-browser engine, and email preferences described below.

Email Communications

Transactional emails are sent from status@freetexttospeech.net using Cloudflare Email Workers when you request a message or an action needs confirmation. Examples include one-time cloud TTS recovery notices, sign-in magic links, feedback acknowledgements you request, unsubscribe confirmations, and supporter activation or claim messages triggered by a verified tip. These messages do not turn on marketing email.

Marketing and product emails for signed-in users may include new tools, tips, offers, promos, campaigns, and other FreeTextoSpeech marketing. The product-update checkbox is optional and unchecked until you choose it. We record the choice and time on your account. You can change it any time on your dashboard, use the unsubscribe link in marketing emails, or contact us.

We retain marketing preference flags on your account while the account exists. We also remember acceptance of the current Privacy Policy and Terms in your browser and, when signed in, on your account so you are not asked again unless those terms materially change. Unsubscribing turns marketing emails off but does not delete your account. Transactional messages you request may still be sent.

Community Supporter Program

Gumroad processes voluntary one-time and monthly support payments. Its notification gives us a sale identifier, product identifier, amount, currency, recurring-payment details, and the name and email supplied to Gumroad. Because Gumroad notifications are not signed, we verify each sale through Gumroad's authenticated API before granting perks. We store the amount, support frequency, and identifiers for administration and duplicate prevention, encrypt the payment email, and keep a keyed email hash for matching and recovery. We do not store the raw notification payload or payment-card details.

New supporter checkouts require sign-in and benefits attach to that account. If an older or unmatched payment is recovered without signing in, an essential HttpOnly ftts_supporter device cookie may temporarily identify that browser; only a keyed hash of its random value is stored in our database. IP addresses are used for abuse controls and ordinary anonymous quotas, not as durable proof that a payment belongs to you.

Activation and claim emails are transactional and do not change your marketing preference. Public supporter recognition is off by default and appears on the supporter leaderboard only after a signed-in supporter opts in and chooses a display name; payment amounts, email addresses, and benefit expiry dates are never shown there. Recognition can be removed at any time. Active supporter pages do not render our AdSense metadata, slots, or loading script.

How We Use Information

We use the information we collect to operate, maintain, and improve the Service, to remember your preferences, to keep the Service secure and prevent abuse, to display advertising that helps keep the Service free, to send transactional and (when subscribed) marketing emails, to review feedback and tool requests, and to comply with our legal obligations.

Cookies and Local Storage

We use cookies and similar technologies (such as browser local and session storage) for essential functionality, to remember settings like your chosen voice and speed, to measure performance, and to support advertising. When you sign in with Google or email, we set an HttpOnly session cookie (Domain .freetexttospeech.net, lasting about 30 days) to keep you authenticated. New supporter checkouts use that signed-in account. A legacy or recovery supporter claim may set the essential HttpOnly ftts_supporter cookie for up to one year so recovered benefits can survive IP changes and later transfer to an account. Local storage may also keep drafts, pronunciation replacements, reading positions, and supporter-prompt frequency. If you opt to use your own Groq API key, session storage keeps that key available across transcription tools in the same tab. Generated audio is not stored there. For a full breakdown, see our Cookie Policy.

Advertising and Google AdSense

We use third-party advertising companies, including Google AdSense, to serve ads when you visit the Service. These companies may use cookies and similar technologies to show ads based on your visits to this and other websites.

• Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites.
• Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this Service and/or other sites on the internet.
• Google may use the DoubleClick DART cookie to serve ads based on your activity. This and other advertising cookies may collect data such as your IP address, browser, and pages visited.
• We do not provide your text input or generated audio to advertising partners.

You may opt out of personalized advertising by visiting Google's Ads Settings. You can also opt out of a third-party vendor's use of cookies for personalized advertising at aboutads.info and optout.networkadvertising.org.

On ad-supported tool pages, we run a local ad-availability check when you start a generation. The check looks for blocking of small ad-shaped page elements and a same-origin test script. If blocking is detected, generation pauses and the site asks you to allow ads or use active supporter benefits. The check does not inspect your text, create a tracking identifier, or provide your text to an advertising partner. Active supporter pages do not render the check or our AdSense code.

For more on how Google uses information from sites that use its services, see Google's Privacy & Terms.

Analytics

We may use analytics services (such as Google Analytics) to understand aggregate, anonymized usage, for example which pages are most visited and how the Service performs. These services may set their own cookies and process technical data as described in their respective privacy policies.

Other Third-Party Services

The Service relies on third-party infrastructure for hosting, content delivery, fonts, speech processing, and voluntary support. These providers process data needed to deliver their part of the Service. Gumroad processes support payments and sends the sale notifications described above. Groq processes audio submitted to the transcription tools. The in-browser voice model is downloaded from a public content-delivery network the first time you use that engine.

Data Security

All data transmitted between your browser and our servers is encrypted in transit using HTTPS/TLS. Because we do not store your text, generated audio, or account passwords for the core Service, the amount of personal data at risk is kept to a minimum.

Your Rights and Choices

Depending on where you live, you may have rights under laws such as the GDPR (EEA/UK) or the CCPA (California), including the right to access, correct, or delete your personal data, and to object to certain processing. You can control cookies through your browser, opt out of personalized ads using the links above, unsubscribe from marketing emails via the link in those emails or your dashboard email toggle, and contact us to exercise any applicable rights.

Children's Privacy

The Service is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, please contact us and we will take appropriate steps to remove it.

International Users

The Service may be operated and processed using infrastructure located in various countries. By using the Service, you understand that your information may be processed in locations outside your country of residence, where data protection laws may differ.

Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with a new revision date. Continued use of the Service after changes take effect constitutes acceptance of the updated policy.

Contact

If you have questions about this Privacy Policy, please contact us at blog.boopul@gmail.com.