Meet the Compliance Audio Editorial Team Behind Our API

By Compliance Audio editorial team · Updated 2026-11-18

This page explains why Compliance Audio exists and how we build our text-to-speech API for startups drafting legal documents. You will learn about our voice licensing, data policy, and editorial standards. We focus on honest comparisons and clear technical limits, so you know exactly what you are getting.

If you are a developer or founder who needs reliable audio generation without enterprise overhead, this is for you. We avoid hype and superlatives, sticking to the facts about our API’s capabilities, pricing, and support. Read on to understand how we handle your data and why we keep things simple.

Meet the Compliance Audio Editorial Team Behind Our API

Frequently asked questions

Who runs this website?

Compliance Audio is an independent storefront for a cloud text-to-speech API. We are not affiliated with OpenAI, ElevenLabs, or other major brands. This site is an independent storefront for a lightweight API with character-based pricing and straightforward documentation.

Are the voices legally licensed?

Yes. Our eight voice presets are based on licensed recordings from LibriTTS-R, which is available under the CC BY 4.0 license. Additionally, some voices originate from LibriVox public-domain audiobook readings. This ensures that the synthetic speech generated by our API is legally compliant for your projects.

Do you use my text for training?

No. Input text is used only to produce the audio file and is not used for training our models. We respect your data privacy by ensuring that your specific text inputs remain dedicated solely to the generation task without being added to our broader training datasets.

Is there a phone number for support?

No, we do not have a phone number or live chat. Support is provided via email only. This keeps our operations lightweight and efficient, allowing us to focus on delivering a reliable text-to-speech API without the overhead of traditional customer service channels like phone support.

How do I contact the editorial team?

You can reach our editorial team via email. Visit our contact page to send your inquiries. We do not offer phone support or live chat, so email is our primary method for communicating with users and handling any questions regarding the API, pricing, or technical details.

Are you affiliated with OpenAI?

No, we are not affiliated with OpenAI. Our API endpoint mimics the OpenAI speech endpoint structure, so you can use the official OpenAI SDKs by simply changing the base URL. However, we are an independent provider with our own pricing, voices, and infrastructure, distinct from OpenAI.

Do you have SOC 2 certification?

No, we do not have SOC 2, HIPAA, or GDPR certification. We are a lightweight API provider for startups and do not offer enterprise contracts, SLAs, or uptime guarantees. Our focus is on providing a simple, character-based pricing model and reliable audio generation without complex compliance overheads.

Can I request a voice change?

No, we do not offer custom voice cloning or voice design. You must choose from our eight preset voices: Aria, Nova, Luna, Sage, Felix, Milo, Atlas, or Orion. These voices are based on licensed recordings and cannot be customized or cloned for individual customers at this time.

How is the watermarked audio identified?

Every generated audio file carries an inaudible watermark that marks it as synthetic speech. This watermark is embedded directly into the audio output by our engine, allowing you to identify that the audio was generated by our text-to-speech API without affecting the listening experience for your users.

Do you store the generated audio files?

No, generated audio is returned in the response and not stored by us. We keep request metadata, such as time, character count, and status, for billing purposes. Your input text is also not stored for training, ensuring that your specific content remains private and transient.

What is CC BY 4.0?

CC BY 4.0 is a Creative Commons Attribution license. Our voices are based on recordings from LibriTTS-R, which uses this license. It allows us to use the recordings as the base for our TTS engine. This ensures legal clarity for startups using our API for various projects.

Are the voices based on real people?

Yes, our voices are based on licensed recordings from real people. Specifically, they come from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. These are distinct presets like Aria, Felix, or Luna, not imitations of celebrities or politicians.

Do you offer refunds?

Failed requests are free, and the charge is returned in full if synthesis fails. We use USDT on the TRON network for top-ups, and balance does not expire, so unused credits remain available for future use.

How do you handle data privacy?

Input text is used only to produce audio and is not used for training. Generated audio is returned in the response and not stored. We keep request metadata for billing. We do not have SOC 2, HIPAA, or GDPR certifications.

Our Mission

Sound wave illustration for: Our Mission

Compliance Audio was built for startups that need reliable audio for legal documents without enterprise overhead. We provide a lightweight TTS API with straightforward, character-based pricing, helping teams generate legal audio efficiently.

We avoid hype, sticking to facts so you can make informed decisions about your audio infrastructure.

Simplifying Legal Tech

Simplifying Legal Tech

We strip away the complexity of traditional legal tech audio solutions. By offering a simple API that handles text-to-speech for documents, we allow your team to focus on legal work, not audio engineering.

Honest Comparisons

Honest Comparisons

We compare features directly, highlighting where our API excels for legal text and where it might not fit, so you can choose the right tool.

Startup Focus

Startup Focus

Designed for startups, our pricing model scales with your usage. With no monthly plans or minimum spend, you only pay for what you use, making it easy to integrate audio into your legal workflows.

Voice Licensing

Sound wave illustration for: Voice Licensing

Our voice presets are built on licensed recordings, ensuring that the synthetic audio you generate has a clear legal foundation. We selected specific voices to cover the range of tones needed for legal documentation, from calm narration to energetic delivery, all grounded in high-quality source material.

LibriTTS-R License

LibriTTS-R License

Every voice in our catalog is derived from the LibriTTS-R dataset. This ensures that the voice presets are based on real human recordings. You get the natural prosody of human speech with the consistency of an API.

  • Based on real human speech patterns
  • High-fidelity source recordings
  • Consistent voice quality across requests

CC BY 4.0

The LibriTTS-R dataset is released under the Creative Commons Attribution 4.0 International license. This means we can legally use these recordings as the base for our TTS engine. You can rely on the clarity and naturalness of the output without worrying about obscure licensing restrictions for your generated audio files.

Public Domain Source

The original recordings come from LibriVox, which features public domain audiobook readings. This combination of public domain source material and a permissive CC BY 4.0 license for the dataset provides a robust and transparent foundation for our API. It’s a straightforward legal path from source to your final audio file.

Data Policy

Sound wave illustration for: Data Policy

We built Compliance Audio for startups that treat data privacy as seriously as their code. When you send text for legal document generation, that input is used exclusively to synthesize the audio file and is never added to our training datasets for future model improvements.

Once the synthesis completes, the generated audio is returned to you in the response and is not stored on our servers. We retain only the necessary request metadata—such as timestamp, character count, and status—for billing and usage tracking purposes.

No Training on Input

Your text input is processed solely to produce the audio output. We do not use your input text for model training, ensuring that your specific legal phrasing or case details remain distinct from our underlying engine data.

No Audio Storage

Generated audio files are delivered directly in the API response and are not persisted in our storage systems. This means your voice outputs are transient, reducing the risk of long-term data exposure for sensitive legal communications.

Metadata Retention

We keep request metadata, including generation time, character count, and status, strictly for billing accuracy and operational monitoring. This minimal data allows us to track usage without storing the actual content you are converting.

Editorial Standards

Sound wave illustration for: Editorial Standards

We build our API for startups that need reliable audio for legal documents, so we keep our promises simple and specific. Our editorial standards ensure that every claim about performance, pricing, or capabilities is grounded in the actual behavior of our text-to-speech engine.

Fact-Based Reviews

We test our own endpoints against the published character limits and voice presets. When we mention speed or latency, we reference real-world generation times for typical legal text lengths, avoiding vague benchmarks. We use the tts-1 and tts-1-hd models as described in our documentation.

  • Verified character counts for all voice outputs
  • Generation tests for long-form legal texts
  • Confirmed language support for all 23 listed languages

No Hype

We avoid superlatives like 'best' or 'fastest' unless we can prove them with date-stamped data. We don't claim human-like perfection; we state that our voices are based on licensed recordings from LibriVox. We clearly distinguish between synthetic speech features and actual human nuance, so you know exactly what you are integrating.

Clear Distinctions

We explicitly note what our API does not do, such as streaming or SSML support, to prevent integration surprises. We clarify that our key system is unique to our storefront and not affiliated with OpenAI, even though the SDK compatibility is identical. This clarity helps startups choose the right tool without hidden assumptions.

  • Explicit listing of missing features (no streaming, no SSML)
  • Clear distinction from OpenAI's official offerings
  • Transparent explanation of character counting and pricing
Editorial Standards

Contact Information

Sound wave illustration for: Contact Information

We are a small team focused on delivering reliable TTS for legal tech startups. We built this API to be transparent and straightforward, avoiding the complexity of enterprise contracts.

Email Support

For all inquiries, please email us directly at [email protected]. This is our only support channel, ensuring every message is tracked and addressed by the team that built the API.

No Phone Number

We do not offer a phone number. By relying on email, we avoid hold times and ensure your technical questions are answered by engineers who understand the API’s specifics, rather than generalist support agents.

Response Time

Since we are a lean startup team, responses are direct and technical, focusing on solving your specific integration issues quickly.

Technical Limits

Sound wave illustration for: Technical Limits

Compliance Audio is built for speed and simplicity, which means we prioritize flexibility over rigid enterprise guarantees. We operate as a lean service, meaning you get direct access to our API without the overhead of complex contracts or uptime pledges.

No SLA

We do not offer a Service Level Agreement guaranteeing specific uptime percentages or response time commitments. Our infrastructure is optimized for cost-efficiency, so while we strive for stability, we do not legally bind ourselves to a 99.9% uptime promise or compensate for minor outages.

No Certifications

We currently do not hold third-party certifications such as SOC 2, HIPAA, or GDPR compliance certificates. While we follow standard data practices, we do not maintain the extensive audit trails required for these specific regulatory badges. Startups using our API accept this trade-off for lower costs.

Best Effort

All services are provided on a "best efforts" basis. We will make reasonable attempts to resolve issues quickly, but we do not guarantee exclusive resources or priority support queues. For complex legal document processing, you retain full control over your input text and generated audio files.

  • No dedicated support queue
  • Shared infrastructure resources

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Teams must carefully monitor character counts to avoid unexpected costs.

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. OpenAI API reference: create speech
  3. MDN: Web Speech API
  4. openai-python on GitHub
  5. FFmpeg documentation
  6. openai-node on GitHub
  7. Tether (USDT)
  8. curl documentation
  9. LibriVox public-domain audiobooks
  10. Node.js documentation
  11. TRON developer hub: TRC-20
  12. LibriTTS-R corpus (OpenSLR 141)

More on this site