Our Infrastructure and Voice Licensing Details

By P94 Editorial Team · Updated 2026-11-18

This page outlines the operational structure and data handling policies of LingvoRead, an independent text-to-speech API provider. We serve independent publishers and audiobook creators who require precise voice synthesis without enterprise overhead. Our infrastructure is designed for startups needing automated content localization through a transparent, per-character pricing model.

Here you will find details on our voice licensing sources, specifically the LibriTTS-R dataset, and our strict data retention practices. We also define our infrastructure limits, including the absence of an SLA, and clarify our support channels. This information ensures you understand the technical and operational boundaries of our API before integration.

Our Infrastructure and Voice Licensing Details

Frequently asked questions

Who runs LingvoRead?

LingvoRead is an independent storefront for the P94 text-to-speech API. We operate as a distinct entity providing cloud synthesis services. Our team manages the API endpoint at api.playp94.com/v1. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, or Microsoft. We function as a standalone provider for developers and publishers requiring reliable TTS infrastructure without enterprise overhead.

Where are the voices sourced from?

Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0). These sources include public-domain audiobook readings from LibriVox. Each generated audio file carries an inaudible watermark marking it as synthetic speech. We do not offer custom voice cloning or emotion tags. The voices are static presets designed for consistent, high-quality synthesis.

Is my data safe with P94?

Input text is used solely to produce the audio and is not used for training models. We retain request metadata, including time, character count, and status, strictly for billing purposes. Generated audio is returned in the response and is not stored on our servers. This ensures your content remains private and is not repurposed for other uses.

Do you store the audio files I generate?

No. Generated audio is returned directly in the API response and is not stored on our servers. We only keep request metadata, such as timestamp, character count, and status, for billing and usage tracking. This minimizes data retention and ensures your synthesized audio files are transient unless you save them locally after retrieval.

How can I contact support?

Support is available via email only. We do not offer a phone number, live chat, or SLA guarantees. You can reach us through the contact page at https://playp94.com/contact/. We prioritize direct communication to address technical inquiries efficiently.

Is P94 affiliated with OpenAI?

No. LingvoRead is not affiliated with OpenAI, despite our API endpoint shape matching the OpenAI speech endpoint. We are an independent provider. Our SDK compatibility allows you to use official OpenAI libraries by changing the base URL. We are a separate entity with distinct pricing, voices, and infrastructure, unrelated to OpenAI’s services.

Do you have a physical address?

We do not list a physical address. As a cloud-based API provider, we operate independently without a public office location. Our infrastructure is managed remotely. This aligns with our model of providing scalable TTS services without the overhead of physical premises. All operations, including billing and support, are conducted digitally via our website and email.

Are you certified (SOC 2, HIPAA)?

We do not hold SOC 2, HIPAA, or GDPR certifications. We do not offer on-premise installations or enterprise contracts. Our service is designed for general use cases without specific regulatory compliance guarantees. If you require certified infrastructure, please verify our standard data practices via our privacy details. We focus on transparent, per-character pricing instead of compliance overhead.

Who We Are

Sound wave illustration for: Who We Are

LingvoRead is an independent storefront providing a reliable text-to-speech API for independent publishers and audiobook creators. We operate without enterprise overhead, enabling startups to automate content localization and voiceover production through a transparent, per-character pricing model.

Our infrastructure is built for precision and transparency, ensuring that every generated audio file meets specific quality standards for professional use cases without the complexity of large-scale enterprise contracts.

Independent Editorial Team

Independent Editorial Team

We are a dedicated editorial group focused solely on delivering high-quality synthetic speech. We manage the API infrastructure and voice presets directly, ensuring consistent performance for our users.

  • Direct management of voice presets
  • Lean operational structure
  • Focus on audiobook and publishing workflows

API-First Approach

API-First Approach

Our entire product is designed around a clean, standard-compliant API. We use a request shape identical to the OpenAI speech endpoint, allowing developers to integrate quickly by simply changing the base URL to https://api.playp94.com/v1.

This approach eliminates the need for custom SDKs or complex integrations, making it easy for engineering teams to adopt our TTS solution into their existing pipelines.

Startup-Focused Design

We understand the constraints of early-stage companies. Our pricing model charges $0.01 per 1,000 characters with no monthly plans or minimum spend, allowing startups to scale costs directly with usage.

Accounts are created per site, with a simple sign-up process via Google or email. This simplicity reduces administrative overhead, letting founders focus on product development rather than vendor management.

Voice Licensing

Sound wave illustration for: Voice Licensing

LingvoRead’s voice synthesis engine relies exclusively on the LibriTTS-R dataset, ensuring consistent and licensable audio quality for commercial and editorial use. Our eight voice presets—ranging from Aria’s warm narration to Orion’s deep documentary tone—are derived directly from these source recordings, maintaining a uniform acoustic profile across all generated audio files.

LibriTTS-R Dataset

The core voice models are trained on the LibriTTS-R dataset, providing a robust foundation for our text-to-speech API.

CC BY 4.0 License

The voice recordings are based on the LibriTTS-R dataset (CC BY 4.0) from LibriVox public-domain audiobook readings.

Public Domain Sources

The underlying recordings originate from LibriVox, which hosts public domain audiobook readings. By utilizing these pre-existing public domain materials, we ensure that the foundational audio assets are free from additional copyright encumbrances. This sourcing strategy minimizes legal overhead for startups and self-publishers who need reliable, royalty-free voice assets for their content localization pipelines.

Voice Licensing

Data Policy

Sound wave illustration for: Data Policy

LingvoRead processes input text exclusively to generate the requested audio file. We do not use your submitted content for model training or to improve our voice synthesis algorithms. Your data remains isolated to the specific synthesis task unless you choose otherwise.

No Training on Input Text

The text you submit is consumed solely for the purpose of creating the audio output. It is not ingested into our training dataset, ensuring that your proprietary content remains distinct from our core model improvements.

No Audio Storage

Generated audio files are returned directly in the response and are not stored on our servers after delivery. This ensures that your final products remain under your control without lingering copies in our infrastructure.

Metadata Retention

We retain request metadata, including timestamp, character count, and status, strictly for billing and usage verification. This data supports accurate invoicing based on the per-character pricing model and helps us monitor API health.

Infrastructure Limits

Sound wave illustration for: Infrastructure Limits

LingvoRead operates as an independent service without binding service level agreements. We do not guarantee specific uptime percentages or financial credits for downtime.

No SLA Guarantee

We do not offer formal SLAs with financial penalties for outages. This allows us to maintain competitive pricing for independent publishers and startups without the overhead of guaranteed 99.9% availability contracts.

No Uptime Promise

Service availability is not contractually guaranteed. While we strive for stability, interruptions may occur due to maintenance or load adjustments. Clients should build retry logic into their applications.

Queue Processing

Requests are processed sequentially. Under high load, synthesis may wait in a queue, increasing latency beyond the typical real-time speed of 25 characters per second.

Requests are processed one after another, so under load a request may wait in a queue.

  • Sequential request processing
  • No dedicated instance guarantees
  • Latency increases during high load
Infrastructure Limits

Support Channels

Sound wave illustration for: Support Channels

LingvoRead maintains a lean operational structure to ensure transparent pricing and direct access for startup teams. Our support model reflects this efficiency, prioritizing clear, asynchronous communication channels that integrate smoothly with developer workflows without the overhead of enterprise-grade help desks.

Email Support Only

All inquiries are handled via email, ensuring a documented trail for technical and billing issues. This approach allows our editorial and engineering teams to address complex API questions with precision, providing detailed responses that can be referenced later during implementation.

No Live Chat

We do not operate live chat widgets, avoiding the common pitfall of rushed, shallow interactions. This ensures that every support ticket receives full attention from a qualified engineer rather than a generalist, maintaining the quality of technical assistance for API integrations.

No Phone Number

There is no dedicated phone line for customer service. This eliminates the friction of hold times and phone-based troubleshooting, aligning with our API-first philosophy where developers prefer written documentation and email exchanges that can be easily copied into issue trackers.

Support Channels

Contact Information

Sound wave illustration for: Contact Information

LingvoRead operates with a lean, direct communication structure to ensure efficient handling of technical and editorial matters. Our team prioritizes clear, documented responses over asynchronous delays, maintaining a strict email-only support model without live chat or telephone lines. This approach aligns with our API-first design, keeping communication channels focused on verifiable records for billing and technical troubleshooting.

Editorial Email Address

For questions regarding voice presets, licensing details of the LibriTTS-R dataset, or content localization strategies, contact [email protected]. We address inquiries about voice characteristics and language support within 48 hours.

API Key Support

For issues related to API key rotation, balance discrepancies, or rate limit anomalies, use [email protected]. Provide your key identifier and request timestamp for faster resolution.

General Inquiries

For business inquiries, partnership discussions, or feedback on the TTS engine, use [email protected]. All general communications are directed to the primary editorial team for initial triage.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Self-publishing lets startups directly monetize their expertise by producing audiobooks for global audiences.

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. IETF RFC 7845: Ogg Opus
  3. Python documentation
  4. FFmpeg documentation
  5. curl documentation
  6. MDN: Web Speech API
  7. LibriTTS-R corpus (OpenSLR 141)
  8. Tether (USDT)
  9. ISO 639 language codes
  10. LibriTTS-R paper (arXiv 2305.18802)
  11. OpenAI API reference: create speech
  12. LibriVox public-domain audiobooks

More on this site