About the Audibook Team, Licensing, and Data Policy

By Audibook editorial team · Updated 2026-11-18

This page details the operational structure, licensing, and data policies of the Audibook API. It explains how our independent storefront functions for publishers seeking reliable text-to-speech infrastructure for audiobook production. We outline the technical basis of our voices, our data retention practices, and the specific limitations of our service tier.

You will find clear information on our voice licensing from LibriVox, our approach to input data usage, and our support channels (email only). This resource is intended for technical leads and publishers who need to understand the engineering constraints, legal basis, and data handling procedures before integrating the API into their self-publishing workflows.

About the Audibook Team, Licensing, and Data Policy

Frequently asked questions

Who owns this site?

This is an independent storefront for the Audibook text-to-speech API. Accounts are specific to this domain, playtk66.com. We operate as a standalone provider, managing keys and billing directly without intermediary platforms or third-party storefronts.

Are you affiliated with OpenAI?

No. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API endpoint shape matches the OpenAI speech endpoint for SDK compatibility, but we are a separate entity.

Is the data encrypted?

Input text is used only to produce audio and is not stored. Request metadata is kept for billing.

Do you sell user data?

No. Input text is used solely for audio synthesis and is not used for training. Generated audio is returned in the response and not stored. We retain request metadata only for billing purposes.

How do I contact support?

Support is by email only. There is no phone number and no live chat. You can reach us via the contact page or email link provided on the site for any inquiries regarding your account or API usage.

Is there a physical address?

We do not list a physical address. As an independent API provider, we operate without a public-facing office location. All operations, including billing and support, are handled digitally through our website and email channels.

Are the voices copyrighted?

Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. Each generated file carries an inaudible watermark marking it as synthetic speech, ensuring clear identification of the audio source.

Can I sue for errors?

We do not offer an SLA or uptime guarantee. Failed requests are refunded in full. While legal rights exist, we do not provide specific liability terms or enterprise contracts. Errors in synthesis are handled via refunds for failed requests.

Do you have a privacy policy?

We retain request metadata (time, characters, status) for billing. Input text is not stored after synthesis. We do not hold GDPR certificates, but we process data strictly for service delivery and billing purposes as described.

Is the team remote?

We are an independent storefront. The team structure is not publicly disclosed. Support is handled via email, and operations are managed digitally. We do not publish details about our internal team composition or work location preferences.

Do you use AWS?

We do not offer on-premise install, data-center choice, or certifications. Our service is delivered via the API endpoint without revealing the specific cloud provider used.

Can I audit your data usage?

You can view your own usage, balance, and characters left on the dashboard. We do not offer third-party audits or detailed data usage reports beyond what is visible in your account settings and billing history.

Is the API open source?

No. We do not provide an official SDK of our own, nor is the API code open source. You use the OpenAI SDK or plain HTTP. The implementation details of our server-side processing are proprietary.

Do you hire voice actors?

Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) from LibriVox public-domain audiobook readings. We do not offer custom voice cloning or uploading your own voice. The voices are presets.

Editorial Team

Sound wave illustration for: Editorial Team

Audibook is engineered for reliable audio production. Our engineering focuses on API stability, voice synthesis accuracy, and transparent pricing for publishers and self-publishing workflows. We prioritize infrastructure that scales with your content volume without hidden fees.

We operate as an independent storefront, distinct from the underlying voice dataset providers. Our engineering decisions are driven by practical needs for audiobook production, ensuring consistent output for long-form text conversion.

Engineering focus

Engineering focus

Our primary metric is reliable character-to-audio conversion. We maintain the API infrastructure to handle batch processing efficiently, ensuring that long texts are split and joined seamlessly for audiobook workflows.

The team prioritizes API stability and voice synthesis accuracy over feature bloat. We deliver exactly what publishers need: high-fidelity synthetic voices with transparent pricing and no hidden fees.

Independent operation

Audibook functions as an independent storefront for the TTS API. We manage our own billing and key issuance; customer support is by email only.

Accounts are site-specific, allowing publishers to manage their credits and usage independently. This structure ensures that your data and billing are handled directly by our engineering team.

No external affiliation

We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API endpoint mimics the OpenAI shape for convenience, but we are a separate entity.

The voices are sourced from LibriVox and licensed under CC BY 4.0. We do not use proprietary voice models from other companies, ensuring full transparency in our voice licensing and data usage.

  • Independent billing and key management
  • Direct engineering control over API stability
  • No reliance on third-party platforms for core operations
  • Transparent voice licensing via LibriVox

Voice Licensing

Sound wave illustration for: Voice Licensing

Our synthetic voices are derived from the LibriTTS-R dataset, which captures licensed recordings of narrators reading public-domain audiobooks. This foundation ensures that every generated voice retains a natural, high-fidelity quality suitable for professional audiobook production without the overhead of custom studio sessions.

LibriTTS-R dataset

The underlying audio data comes directly from high-quality recordings in the LibriTTS-R corpus. We use these recordings to define our eight voice presets, ensuring consistent clarity and tone across all generated speech files.

CC BY 4.0 license

The source material is licensed under Creative Commons Attribution 4.0 International. This open license allows us to build commercial-grade TTS engines while respecting the original creators' rights. You receive a clean, synthetic audio file with no hidden royalty obligations for your published audiobooks.

LibriVox source

The recordings originate from LibriVox, a community of volunteers reading books in the public domain. By leveraging these existing public-domain readings, we provide stable, reliable voices without relying on single performers or exclusive contracts that could disrupt your production pipeline.

Voice Licensing

Data Policy

Sound wave illustration for: Data Policy

Audibook processes text exclusively for immediate audio synthesis. Your input characters are not ingested into training datasets, ensuring that your manuscript text remains distinct from the model’s learning corpus. This isolation preserves the integrity of your source content without contributing it to future voice model iterations.

Input text not trained

The text submitted to the API is used solely to generate the requested audio file. We do not retain your narrative content for retraining or model improvement, ensuring your published works remain private.

Audio not stored

Generated audio files are returned directly in the API response and are not persisted on our servers after delivery. Generated audio is returned in the response and not stored.

Metadata kept

We retain request metadata including timestamp, character count, and status for billing accuracy. This minimal data allows us to verify usage against your balance and process refunds for failed requests without storing the actual audio content or the source text.

Contact Support

Sound wave illustration for: Contact Support

Our support infrastructure is designed to remain lean and cost-effective, ensuring that our API pricing stays transparent and competitive for publishers. We prioritize asynchronous communication, allowing you to document issues clearly and receive detailed technical responses without the overhead of real-time staffing.

Email only

All support inquiries are handled via email. This allows our engineering team to provide thorough, written responses that can be referenced in your project logs. Please include your API key and relevant request IDs for faster resolution.

No live chat

We do not offer live chat widgets or instant messaging support. This decision reduces operational complexity and keeps our focus on API reliability and clear documentation rather than real-time availability.

No phone number

There is no dedicated phone line for customer service. You can reach us exclusively through the email address provided in our documentation. This ensures all communications are recorded and searchable.

Contact Support

Limitations

Sound wave illustration for: Limitations

Audibook operates as an independent API storefront without formal service-level commitments. We do not provide financial compensation for downtime or performance deviations, allowing us to maintain agile infrastructure without the overhead of enterprise-grade guarantees.

Our service model prioritizes cost-effective scalability over rigid uptime promises. Users should design their applications to handle transient failures gracefully, as we do not guarantee continuous availability or specific latency thresholds.

No SLA

We do not offer a Service Level Agreement (SLA). There are no contractual penalties for delays or outages, keeping our pricing simple and transparent for self-publishing workflows.

No uptime guarantee

Unlike enterprise providers, we do not promise a specific percentage of operational time. Infrastructure maintenance or unexpected load may affect availability without notice.

No certifications

We do not hold SOC 2, HIPAA, or GDPR certificates. Our infrastructure is standard and secure, but we do not undergo third-party audits to validate compliance for specific regulatory industries.

Network Structure

Sound wave illustration for: Network Structure

Audibook operates as an independent storefront for a single text-to-speech API infrastructure. Each site in the network is an independent storefront for the same text-to-speech API.

Independent storefront

Each site acts as a self-contained commercial entity with its own branding and customer-facing interface. This structure allows us to maintain specific operational focus without relying on third-party platform policies or brand associations.

Same API core

All storefronts route requests to the identical API core. Voice presets, character limits, pricing models, and processing queues remain uniform regardless of which domain you use to access the service.

Site-specific accounts

Authentication credentials are isolated per site. An API key or Google account created on one domain does not transfer to another. You must manage keys and balances separately for each storefront you utilize.

Network Structure

FAQ

Sound wave illustration for: FAQ

Audibook is an independent storefront for the Audibook TTS API. Accounts and keys are site-specific, though the underlying engine remains consistent across the network.

Who owns this site?

This is an independent storefront. Each site in the network operates separately with its own accounts, though they share the same API core.

Are you affiliated with OpenAI?

No. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, or Microsoft. Our API shape mimics theirs for convenience, but we are a separate entity.

Is the data encrypted?

We use standard encryption for data in transit and at rest. Specific infrastructure details are not publicly disclosed.

Do you sell user data?

No. Input text is used only to produce audio and is not used for training. Generated audio is returned and not stored. Request metadata is kept only for billing.

How do I contact support?

Support is by email only. We do not offer live chat or a phone number.

Is there a physical address?

  • No physical address is listed.

Are the voices copyrighted?

Voices are based on LibriTTS-R (CC BY 4.0) from LibriVox public-domain audiobook readings.

Can I sue for errors?

Liability is governed by our terms of service. We do not offer an SLA or uptime guarantee.

Do you have a privacy policy?

Yes, see the /privacy/ page for details on data retention and usage.

Is the team remote?

The team operates independently. Specific team structure details are not published.

Do you use AWS?

We use cloud infrastructure. Specific providers are not disclosed.

Can I audit your data usage?

You can view your own request metadata (time, characters, status) in your account dashboard.

Is the API open source?

No. The API is proprietary. We use the OpenAI SDK format for compatibility.

Do you hire voice actors?

No. We do not hire voice actors; we license existing recordings from LibriVox.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Empower authors to share their stories and build lasting careers through direct reader engagement.

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. Node.js documentation
  3. openai-node on GitHub
  4. ISO 639 language codes
  5. LibriTTS-R paper (arXiv 2305.18802)
  6. openai-python on GitHub
  7. FFmpeg documentation
  8. Creative Commons Attribution 4.0
  9. OpenAI API reference: create speech
  10. IETF RFC 7845: Ogg Opus
  11. LibriVox public-domain audiobooks
  12. W3C WAI: making audio and video accessible

More on this site