About SpeechCraft: Team, Licensing, and Data Policy

By SpeechCraft editorial team · Updated 2026-11-19

This page explains who runs SpeechCraft, how we license our voice data, and exactly how we handle your input text. If you are a mobile product team evaluating text-to-speech APIs, you need to know where our voices come from and whether your user data stays private. We strip away enterprise complexity to give you a clear, honest view of the service behind the API.

We are an independent storefront focused on mobile developers who value transparency over hype. Here you will find details on the CC BY 4.0 licensing for our voice presets, and our straightforward data retention policies. Read on to understand exactly what you are getting when you send text to our API.

About SpeechCraft: Team, Licensing, and Data Policy

Frequently asked questions

Who runs this website?

This is an independent storefront for the SpeechCraft TTS API, built for mobile product teams. We are not affiliated with OpenAI, ElevenLabs, or other major brands. Our team focuses on providing a reliable, cost-effective text-to-speech solution without enterprise complexity, helping you compare options and switch to an API that fits your budget and technical stack.

Where do the voices come from?

Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. Each generated audio file carries an inaudible watermark marking it as synthetic speech. These voices provide clear narration suitable for mobile applications. Custom voice cloning is not offered.

Is the content licensed?

The underlying voice data originates from LibriTTS-R (CC BY 4.0) and LibriVox public-domain readings. While the source material has specific licenses, the generated audio files produced by our API are yours to use. We do not claim ownership over the specific voice performances, but we provide the engine that synthesizes them from these licensed sources.

Do you store my audio files?

Generated audio is returned in the response and is not stored by us. Input text is used only to produce the audio and is not retained for long-term storage. We keep request metadata, such as time, character count, and status, strictly for billing purposes to ensure accurate accounting of your usage and charges.

Do you use my text for training?

No. Input text is used solely to produce the audio file for your request. It is not used for training our models or improving the API. This ensures your content remains private and is not repurposed to enhance the synthetic voice engine, providing a clear separation between your data and our model development.

How can I contact support?

Support is available via email only. We do not offer a phone number or live chat. You can reach our team through the contact page or by emailing us directly. Please include your API key and details about your issue so we can assist you efficiently with your text-to-speech requests.

Do you have a phone number?

No, we do not have a phone number. All support is handled via email. This allows us to maintain a direct line of communication and provide detailed written responses to your technical questions or billing inquiries. You can find our email address on the contact page or in your account dashboard.

Are you affiliated with OpenAI?

No, we are not affiliated with OpenAI, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API endpoint mimics the OpenAI speech endpoint structure, so you can use the official OpenAI SDKs by changing the base URL. However, we are an independent provider with our own pricing, voices, and infrastructure.

Do you offer SLA?

No, we do not offer a Service Level Agreement (SLA) or uptime guarantee. Our service is designed for flexibility and cost-effectiveness rather than enterprise-grade contractual guarantees. While we strive for reliability, we do not promise specific availability percentages or compensation for downtime. This approach keeps our pricing simple and accessible for mobile product teams.

Are you HIPAA compliant?

No, we do not have HIPAA certification or compliance. We do not offer on-premise installs or specialized data handling for healthcare requirements. Our service is general-purpose, suitable for most mobile applications. If you require specific regulatory compliance, you should verify that our standard data practices meet your organization's internal legal and security standards.

Who owns the copyright?

The copyright for the generated audio files belongs to you. The underlying voice models and API infrastructure are owned by SpeechCraft. The source recordings come from LibriVox (public domain) and LibriTTS-R (CC BY 4.0), which may have their own attribution requirements depending on your specific use case.

Can I use the voices commercially?

Yes, you can use the generated audio files commercially. Our API is designed for mobile apps and other commercial products. You can use the output commercially. However, always review the specific license of the source material if required by your project.

How do I report a bug?

You can report bugs via email support. Please include your API key, the text input, the voice used, and a description of the issue. Our team reviews these reports to improve the API. Since we do not have live chat, email allows us to track issues systematically and provide detailed updates on fixes.

Where is your server located?

We do not specify a single server location or offer data-center choices. Our infrastructure is cloud-based and distributed to ensure reliability and low latency for global users. We do not provide on-premise installation options. Data is processed in our cloud environment, and request metadata is stored for billing purposes regardless of your geographic location.

Who We Are

Sound wave illustration for: Who We Are

SpeechCraft is an independent storefront for a cloud text-to-speech API, designed to help mobile product teams find reliable, cost-effective solutions without enterprise complexity. We simplify API integration so you can focus on building your app.

Editorial Team Focus

Editorial Team Focus

We specialize in simplifying API integration for mobile developers. Our editorial team curates clear, specific guidance on TTS implementation, ensuring you understand exactly how our API fits your technical stack.

Mobile Industry Expertise

Mobile Industry Expertise

We understand the unique constraints of mobile environments. From character limits to latency considerations, we provide concrete examples and workflows tailored to mobile product teams who need consistent performance on varying devices.

  • Optimized for mobile app workflows
  • Clear character and speed limits
  • Real-world integration examples

Independent Storefront

Independent Storefront

As an independent storefront, we offer a direct path to the SpeechCraft API. We are not affiliated with OpenAI, ElevenLabs, or any other major brand, providing a transparent, budget-friendly alternative for your projects.

Voice Licensing

Sound wave illustration for: Voice Licensing

Our voice presets are built on high-quality recordings from the LibriTTS-R dataset, ensuring a solid foundation for natural-sounding synthesis.

We provide eight distinct presets that cover a wide range of tonal needs for mobile products.

LibriTTS-R Source

LibriTTS-R Source

Every voice in our catalog originates from the LibriTTS-R dataset, which provides clean, high-fidelity audio recordings suitable for modern TTS engines.

CC BY 4.0 License

The underlying recordings are licensed under Creative Commons Attribution 4.0 (CC BY 4.0), allowing us to integrate them into our commercial API while respecting the original creators' rights.

LibriVox Public Domain

Many of the source readings come from LibriVox, leveraging public domain audiobook content to ensure broad accessibility and ethical sourcing of voice material.

Data Privacy Policy

Sound wave illustration for: Data Privacy Policy

We prioritize data integrity for mobile product teams by keeping your input text strictly for synthesis. Your text is not used to train our models or improve voice engines. Once the audio file is generated, it is returned in the response and not stored on our servers.

We retain minimal metadata solely for billing accuracy and debugging. This includes the request timestamp, character count, and status code. This data helps us verify charges and resolve issues, ensuring transparent cost tracking for your API usage without retaining the actual content you process.

Input Text Usage

Your input text is used exclusively to produce the audio file. We do not use your text to train our models or improve our voice engines. Once the audio is generated, the text is not stored for long-term retention.

Audio Storage Policy

Generated audio is returned in the HTTP response and is not stored on our servers. You are responsible for saving the audio file to your own infrastructure. We do not keep copies of your generated speech files after delivery.

Metadata Retention

We keep request metadata (time, character count, status) for billing and debugging. This ensures accurate charge calculation and helps us resolve technical issues. No personal identifiable information is linked to this metadata beyond your account key.

Contact and Support

Sound wave illustration for: Contact and Support

We handle all customer inquiries through a single, dedicated email address. This ensures that every question is reviewed without the noise of multiple channels.

There is no live chat widget or phone number to call. Asynchronous communication allows for thoughtful, accurate responses to your technical or billing questions.

Email Support Only

All support requests are directed to [email protected]. This is our only official channel for assistance.

We do not maintain separate support queues for different tiers, as all accounts receive the same level of attention.

No Live Chat

Unlike many SaaS platforms, we do not offer real-time chat. This reduces overhead and keeps our costs low for you.

You can expect a written response rather than a quick chat bubble, allowing for detailed explanations and code snippets.

Response Times

We aim to respond to all emails within 24 hours during business days.

Complex technical issues may take slightly longer, but we will acknowledge receipt promptly.

Contact and Support

Limitations

Sound wave illustration for: Limitations

SpeechCraft is an independent API storefront designed for mobile product teams who prioritize straightforward pricing and technical simplicity over enterprise-grade guarantees. We provide reliable text-to-speech synthesis without the complexity of traditional vendor contracts, allowing you to focus on your app's core features.

No SLA Guarantee

We do not offer a formal Service Level Agreement (SLA) or uptime guarantee. Requests are processed one after another, so under load a request may wait in a queue. This model allows us to keep costs low and flexible for teams who do not require strict 99.9% uptime contracts.

No Certifications

Our service does not hold specific industry certifications such as SOC 2 or HIPAA. We are built for general mobile app use cases rather than regulated healthcare or financial sectors requiring audited compliance. Our data policy ensures input text is not used for training, but we do not provide official compliance certificates.

No Phone Support

We offer support exclusively via email. There is no live chat or phone number available. This keeps our overhead low and ensures every inquiry is documented and searchable. For urgent issues, please include your API key and request details in your email for faster resolution.

Affiliation Statement

Sound wave illustration for: Affiliation Statement

We are an independent storefront for the SpeechCraft TTS API. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our service operates separately, using the OpenAI SDK structure only for compatibility.

Not Affiliated with OpenAI

Our API endpoint and billing are distinct from OpenAI’s services. While we mirror the request shape of the OpenAI speech endpoint, we use our own infrastructure and voice models. We do not use OpenAI’s engines or branding.

Independent Service

SpeechCraft is built for mobile product teams who need reliable, cost-effective text-to-speech without enterprise complexity. We manage our own keys, balance systems, and voice licensing independently. You can switch to us without relying on another platform’s ecosystem.

Third-Party Comparisons

When we compare our service to others, we cite only published facts with dates. We do not claim to be the best or fastest. Comparisons are based on measurable data like price per character and language support, not subjective marketing claims.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. There is no complex streaming protocol required; the audio is returned as a complete file.

Avatar of the voice aria
ariafemale
Avatar of the voice nova
novafemale
Avatar of the voice luna
lunafemale
Avatar of the voice sage
sagefemale
Avatar of the voice felix
felixmale
Avatar of the voice milo
milomale
Avatar of the voice atlas
atlasmale
Avatar of the voice orion
orionmale

23 languages

Any voice speaks any of these languages.

Sources and further reading

  1. Wikipedia
  2. MDN: Web Speech API
  3. IETF RFC 7845: Ogg Opus
  4. LibriTTS-R corpus (OpenSLR 141)
  5. LibriVox public-domain audiobooks
  6. Creative Commons Attribution 4.0
  7. TRON developer hub: TRC-20
  8. LibriTTS-R paper (arXiv 2305.18802)
  9. openai-node on GitHub
  10. openai-python on GitHub
  11. Python documentation
  12. curl documentation

More on this site