Editorial Team, Data Policy, and Voice Licensing for Our TTS API

By VerdictRead editorial team · Updated 2026-11-18

This page details the editorial standards, data retention policies, and voice licensing for the VerdictRead TTS API, designed specifically for legal departments managing high-volume case files and briefs. We provide a transparent overview of our independent structure, ensuring that your team understands exactly who manages the service and how our voices are sourced from public domain recordings.

Readers will find precise information on our data privacy practices, confirming that input text is not used for training and generated audio is not stored long-term. We also outline our technical limitations and support channels, offering a clear, factual basis for integrating our API into your firm’s strict compliance and auditing workflows.

Editorial Team, Data Policy, and Voice Licensing for Our TTS API

Frequently asked questions

Who runs this website?

VerdictRead operates as an independent storefront for the VerdictRead text-to-speech API. We are a dedicated entity serving legal departments, distinct from other brands. Our platform provides API access to audio synthesis services, managed independently without affiliation to major tech providers or voice licensing aggregators.

Are the voices licensed for commercial use?

Yes. Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. These sources permit commercial usage, allowing legal teams to generate audio for internal briefs, case files, and client communications without additional licensing fees.

Do you store my input text after generation?

Input text is used only to produce the audio and is not used for training. Generated audio is returned in the response and not stored. We retain request metadata, such as time, character count, and status, strictly for billing and usage verification purposes.

How can I contact support?

Support is available via email only. We do not offer a phone number, live chat, or on-site contact form for direct voice interaction. Email support is the sole channel for inquiries regarding API usage, billing, or technical issues within our legal-focused text-to-speech service.

Is this site affiliated with OpenAI?

No. We are not affiliated with OpenAI, despite our API endpoint shape matching their speech model. We use the same request structure for compatibility with OpenAI SDKs, but our infrastructure, voices, and pricing are entirely separate. We are an independent provider of TTS services.

What is the CC BY 4.0 license?

CC BY 4.0 is a Creative Commons license allowing commercial use with attribution. Our voice presets derive from LibriTTS-R, which uses this license. This permits our API to legally synthesize audio from these sources for commercial clients, including legal departments, without restricting downstream usage of the output.

Do you have an SLA for uptime?

No. We do not provide a Service Level Agreement (SLA) or uptime guarantee. Our infrastructure processes requests sequentially, and under load, requests may queue. We strive for reliability but do not contractually guarantee specific availability percentages or compensation for downtime in our standard terms.

Can I upload my own voice?

No. We do not offer custom voice cloning or the ability to upload your own voice recordings. Our eight presets (Aria, Nova, Luna, Sage, Felix, Milo, Atlas, Orion) are fixed. Users cannot design new voices or clone existing ones through our API or dashboard.

Do you offer custom voice cloning?

No. Custom voice cloning is not offered. We provide eight fixed voice presets based on licensed recordings. There is no feature to train a new voice model on your data, nor is there a voice design tool. All users access the same set of eight standard voices.

Is there a phone number for support?

No. We do not have a phone number for support. All customer service interactions are conducted via email. This applies to technical queries, billing questions, and account management. We do not offer live chat or direct voice support lines for our API services.

Do you have certifications like SOC 2?

No. We do not hold SOC 2, HIPAA, or GDPR certifications. We do not provide enterprise contracts or on-premise installations. Our data handling is described in our privacy policy, but we do not maintain third-party audit certificates for our cloud-based text-to-speech API infrastructure.

How do you handle data privacy?

Input text is used solely for audio generation and is not used for training models. Generated audio is returned in the response and not stored. We retain request metadata (time, characters, status) for billing purposes.

Can I get a refund if I am unhappy?

Failed requests are refunded automatically in full. If synthesis fails, the charge is returned.

Where are your servers located?

We do not specify data-center locations or offer region selection. Our infrastructure is cloud-based and managed by us. We do not provide on-premise installation options. Data is processed in our cloud environment, and we do not guarantee specific geographic jurisdictions for data storage or processing.

Editorial Team and Site Management

Sound wave illustration for: Editorial Team and Site Management

VerdictRead operates as an independent storefront for the VerdictRead TTS API. Our editorial and technical teams manage this specific domain, playtko7.com, separately from other network sites. Each site maintains its own account structure and key issuance process, ensuring that editorial content remains tailored to our specific operational context without relying on external corporate directives.

We do not claim to be the official provider for any major technology brand. Our team independently verifies all product details, pricing, and technical specifications before publication. This separation ensures that our documentation reflects the actual behavior of the API endpoints and voice presets without the influence of larger parent companies or marketing departments.

Independent editorial team

Independent editorial team

The editorial team consists of technical writers and legal-focused content managers who maintain this site. We handle all updates to the API documentation, pricing pages, and voice descriptions. Our process involves direct verification of API responses and voice samples to ensure accuracy. We do not outsource our core product narrative to third-party agencies.

Each network site, including playtko7.com, is managed independently. This means our editorial decisions regarding tone, focus, and technical detail are made in-house. We prioritize precision over broad marketing appeals, ensuring that legal professionals reading our content receive specific, verifiable information about the VerdictRead API.

  • In-house technical verification of API endpoints
  • Independent content management for playtko7.com
  • Dedicated editorial team for legal-focused documentation

No affiliation with major brands

No affiliation with major brands

We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, or Microsoft. While our API endpoint structure mirrors the OpenAI speech endpoint for compatibility, we operate as a distinct entity. Our voices, pricing, and infrastructure are entirely separate from these larger brands. We use brand names only for technical comparison or compatibility context, never to imply endorsement.

Our independence allows us to offer a focused solution for legal departments without the overhead of a large corporate structure. We do not inherit the brand associations or contractual obligations of the companies we compare ourselves to. This clarity helps legal teams understand exactly who they are contracting with and who holds their data.

  • Distinct from OpenAI, despite endpoint similarity
  • No endorsement from major tech brands
  • Independent infrastructure and billing

Honest product representation

Honest product representation

We present the VerdictRead API exactly as it functions. We do not use superlatives like "best" or "fastest" unless supported by specific, verifiable metrics. Our pricing of $0.01 per 1,000 characters is stated plainly, with no hidden fees or subscription traps. We explicitly list limitations, such as the 4096-character input limit and the lack of SSML support, so legal teams can plan their workflows accurately.

We avoid hype and focus on concrete facts. If a feature exists, we document it with precise technical details. If it does not, we state that clearly. This approach ensures that legal departments can trust our documentation for compliance and technical integration purposes. Our reputation relies on accuracy, not marketing volume.

  • No superlative claims without data
  • Explicit listing of technical limitations
  • Plain pricing with no hidden fees

Voice Licensing and Sources

Sound wave illustration for: Voice Licensing and Sources

We use licensed voice recordings from the LibriTTS-R dataset, sourced from LibriVox public-domain audiobook readings. This ensures our eight voice presets are grounded in established, high-quality speech data suitable for legal document narration.

LibriTTS-R license

LibriTTS-R license

The underlying voice models derive from LibriTTS-R, a structured dataset designed for speech synthesis research. We utilize these licensed recordings to power our tts-1 and tts-1-hd models, ensuring consistent audio quality across all generated legal briefs and case files.

LibriVox public domain source

Our voices originate from LibriVox, a platform hosting public-domain audiobook readings. By leveraging this vast archive, we access a diverse range of professional narrations that form the basis of our eight preset voices, from calm instructional tones to energetic promo styles.

CC BY 4.0 compliance

We adhere to the Creative Commons Attribution 4.0 International license. This compliance allows us to incorporate these public-domain recordings into our commercial API service while respecting the original creators' rights. Each generated audio file may carry an inaudible watermark marking it as synthetic speech.

Data Privacy Policy

Sound wave illustration for: Data Privacy Policy

The API is designed for legal departments handling sensitive case files. We ensure that input text is processed strictly for audio synthesis and is not used to train our models. This guarantees that your briefs and documents remain confidential and are not repurposed for model improvement.

Input text not stored for training

Your text is used solely to produce the requested audio file. We do not retain your input data to refine our voice engines. This policy ensures that privileged information in your legal texts remains isolated from our training datasets.

Generated audio not stored

Once the audio file is returned in the response, it is not stored on our servers. The generated audio is transient and exists only for your immediate use. This reduces the attack surface for long-term data retention and aligns with strict legal hold requirements.

Metadata kept for billing

We retain request metadata, including timestamp, character count, and status, exclusively for billing and usage verification. This data is necessary to accurately calculate costs and process top-ups. It is not used for training or marketing and is kept only as long as required for financial records.

Technical Limitations

Sound wave illustration for: Technical Limitations

Our API processes requests sequentially, meaning high-volume batches may queue during peak usage. Each request is limited to 4,096 characters; longer case files must be split and joined client-side. Audio generation is not real-time streaming, taking a few seconds per short phrase or roughly real time on long texts.

No streaming or WebSocket

The endpoint returns a complete audio file upon completion. There is no WebSocket connection for partial audio chunks, and no real-time streaming is available. This ensures reliable, auditable delivery of each synthesis job.

No SSML or custom lexicons

The API does not support SSML tags or custom pronunciation dictionaries. Pronunciation is determined automatically by the engine based on the input text and optional language code. Pronunciation is determined automatically by the engine based on the input text and optional language code.

  • No SSML support
  • No custom lexicons
  • Automatic pronunciation

Fixed voice presets only

Users select from eight fixed voice presets (e.g., atlas for news, luna for storytelling). There is no voice cloning or custom voice design. Each voice is based on licensed recordings from LibriVox public-domain audiobook readings.

  • 8 fixed presets
  • No voice cloning
  • Licensed source material
Technical Limitations

Support and Contact

Sound wave illustration for: Support and Contact

Our support model relies entirely on asynchronous communication to ensure accurate documentation of each case. This approach allows our technical team to provide detailed, written responses that legal departments can easily archive for compliance and audit trails.

Email support only

All inquiries, from API integration questions to billing disputes, are handled exclusively via email. This ensures every interaction is logged and traceable.

No phone or live chat

We do not maintain a phone line or live chat widget. This eliminates wait times and ensures that support interactions are documented rather than ephemeral.

Response times vary

Response times vary. Support is by email only.

Company Structure and Independence

Sound wave illustration for: Company Structure and Independence

VerdictRead operates as an independent storefront for the same text-to-speech API, distinct from major cloud providers. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our editorial team maintains honest product representation without implying official status for external brands.

We do not offer SLAs, uptime guarantees, or enterprise contracts. Our service is provided on a standardized basis with fixed pricing per character. Large legal teams can scale usage directly through account top-ups without negotiating bespoke contracts or requiring dedicated account managers.

Not affiliated with OpenAI

Our API endpoint and SDK compatibility mimic the OpenAI speech endpoint structure, but we are not OpenAI. We do not use their infrastructure, branding, or governance. The similarity allows legal departments to use familiar OpenAI SDKs by simply changing the base URL, but our engine, voices, and pricing are entirely separate.

  • Independent infrastructure and billing
  • Separate voice engine
  • No brand confusion

Independent storefront

This site is an independent storefront for the same text-to-speech API. We manage our own editorial content, pricing, and customer support. Unlike multi-brand platforms, we do not resell third-party TTS engines. Our team directly oversees the API's stability and updates, ensuring consistent performance for legal document processing.

  • Direct editorial control
  • Single API source
  • Transparent pricing

No enterprise contracts

We do not offer SLAs, uptime guarantees, or enterprise contracts. Our service is provided on a standardized basis with fixed pricing per character. Large legal teams can scale usage directly through account top-ups without negotiating bespoke contracts or requiring dedicated account managers.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence.

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-node on GitHub
  3. Tether (USDT)
  4. IETF RFC 7845: Ogg Opus
  5. LibriVox public-domain audiobooks
  6. OpenAI API reference: create speech
  7. LibriTTS-R paper (arXiv 2305.18802)
  8. Creative Commons Attribution 4.0
  9. FFmpeg documentation
  10. TRON developer hub: TRC-20
  11. MDN: Web Speech API
  12. curl documentation

More on this site