Contact Us
Have questions, feedback, or need support for OfflineTTS? The OfflineTTS Project Team reviews product, privacy, licensing, and editorial correction requests. We aim to review ordinary messages within two business days. A reproducible investigation, legal request, or complex licensing question may take longer.
Email Us
For all inquiries β general questions, technical support, bug reports, privacy, or business partnerships.
[email protected]What to Include in a Bug Report
A report is most useful when another person can repeat the problem. Include the page URL, selected engine, model or precision, voice, language, browser and version, operating system, and whether the tool used WebGPU or WebAssembly. Describe the exact steps, the expected result, the actual result, and any visible error message. Mention whether it happened on the first model download or after the model was already cached.
Screenshots and short console excerpts can help, but remove unrelated account information, file names, and private content first. If the issue involves a particular sentence or audio clip, try to reproduce it with a short non-confidential sample that we are allowed to inspect. Reports that only say βit does not workβ are difficult to diagnose because browser storage, device memory, extensions, and model downloads can produce similar symptoms.
Privacy and Sensitive Material
Do not email confidential scripts, private recordings, passwords, API keys, identity documents, medical or financial records, or third-party material you are not authorized to share. Describe the problem, redact personal information, and use a harmless replacement sample whenever possible. Email is a support channel, not a secure file-transfer service.
The browser tools are designed to keep speech inference local. Website analytics and the non-English Kokoro phonemization exception are documented separately in the Privacy Policy. If your question is about a data request or deletion, identify the relevant browser, device, page, and approximate date without sending the original text or audio.
Corrections, Licensing, and Business Requests
For a factual correction, send the affected URL, quote the statement, and include a primary source or a reproducible observation. For licensing questions, name the engine, model, voice, input material, and planned use; we can point to published upstream information but cannot provide legal advice. Partnership proposals should explain the proposed integration, user benefit, commercial relationship, and any data flow involved.
General Inquiry
Questions about features, capabilities, or how OfflineTTS works.
Bug Reports
Found a bug or issue? Help us improve by reporting it.
Partnerships
Business inquiries, integrations, or collaboration opportunities.
Before You Reach Out
You may find your answer in these resources:
- Frequently Asked Questions β Common questions about TTS, STT, privacy, and usage
- Privacy Policy β Local processing, analytics, browser storage, and the phonemization exception
- About Page β How OfflineTTS works and the technology behind it
- Transparency & Testing β Operator, editorial process, test method, model sources, and corrections