A speech data license decides what a buyer may do with the delivered audio, and which rights and records support that use. Settle those questions before collection, access or model training begins. A later consent may support future processing if it is valid. It does not retroactively cure collection or processing that lacked a valid legal basis at the time.
This guide is a buying checklist, not legal advice. License scope, data-protection roles, lawful basis, consent wording, biometric use, withdrawal handling, model-related rights and exclusivity all depend on the project and the jurisdiction. Use the questions below to brief qualified counsel, then put the agreed answers in the signed contract.
Read the grant, not the license label
Exclusive and non-exclusive are only starting points. A non-exclusive grant may let a supplier license the same material to others. An exclusive grant limits reuse only as far as the contract says.
Define whether exclusivity covers the exact recordings, speakers, prompts, language, territory, period, use case or derived material. Do not infer any of these from a label on a product page.
For every purchase, confirm the permitted purposes, territory and term. Confirm sublicensing and contractor access, retention and deletion duties, security requirements, onward transfer and audit rights. Confirm the warranties, the indemnities and any restrictions, such as on biometric identification or synthetic-voice generation. A research-only grant does not authorize commercial deployment unless the text says it does.
| Grant field | Verify before signing |
|---|---|
| Permitted uses | Training, fine-tuning, evaluation, benchmarking, and commercial deployment are named expressly; research-only wording is not stretched to production. |
| Model and derivative rights | Ownership and use of trained weights, outputs, synthetic speech, and derived datasets are allocated in the text rather than assumed. |
| Exclusivity scope | Exactly what exclusivity covers: the recordings, speakers, prompts, language, territory, period, use case, or derived material. |
| Sublicensing and access | Affiliates, contractors, and cloud processors are authorized where needed, with any notification or flow-down duties stated. |
| Retention and deletion | Retention limits, deletion triggers, certification duties, and what happens to models trained before termination. |
| Provenance evidence | Consent or notice records, the source chain, and the documentation actually delivered with the data, not just referenced in marketing. |
| Restrictions | Prohibited uses such as biometric identification, voice cloning, or resale are listed and reconciled with the intended roadmap. |
These grant fields apply whether you license an existing corpus or commission a collection. A dataset page such as the Taiwanese Mandarin speech dataset or Russian speech dataset states the starting point, a commercial license for training and evaluation with signed speaker consent; the remaining fields are set in the contract.
Score these fields across competing offers with the free speech data provider scorecard. Its rights and provenance criteria carry the heaviest default weights. Then inspect the specimen data card to see one way provenance fields can be laid out in a delivery.
Spirelight's dataset pages state each dataset's hours, speakers, recording country and price per hour, under a commercial license for training and evaluation. Request samples and the consent records before you buy. For a custom collection, rights, provenance evidence, schedule and price are set in the written quote and contract.
Allocate model and derivative rights expressly
A data license should say which party may train, fine-tune, evaluate, deploy and commercialize models using the delivery. It should deal separately with trained weights, outputs, transcripts, embeddings, synthetic speech and any kept copies of the source audio.
The answer comes from the contract and the project. Do not assume that owning a model, an output or a synthetic voice follows automatically from access to the recordings.
Text-to-speech, voice cloning, speaker identification and biometric authentication call for explicit use restrictions and wording aimed at contributors. Before training begins, ask counsel to align the supplier agreement, the contributor notice or consent, and the intended product use.
Lawful basis, permissions, and provenance are related but distinct
Provenance records where audio came from and how it moved through the supply chain. A license records contractual permission. Free corpora need the same reading, as the LibriSpeech, LJSpeech, and Common Voice breakdown shows corpus by corpus.
GDPR lawful basis governs the processing of personal data. In some projects, consent may be the relevant lawful basis or an additional permission. It is not the only possible Article 6 basis, though, and a license from a supplier does not by itself establish GDPR compliance.
Decide the lawful basis and the notices you need before collection or reuse. If you rely on consent, check that it was freely given, specific, informed and unambiguous, that it can be demonstrated, and that withdrawal can be handled.
Link each record to the contributor and the files closely enough to support the audit trail you intend. If another lawful basis is used, document that assessment and any purpose-compatibility analysis. Do not present a consent form as a substitute.
A later consent can authorize future processing if it is valid. It does not retrospectively legalize earlier collection or processing that lacked a valid basis. Remediation, deletion and the effects on an existing model are fact-specific questions for counsel.
Public availability is not the same as permission to train. For scraped, open, customer-call or repurposed audio, check the actual source for copyright and database rights, contract terms, notices, lawful basis, purpose limitation and any sector-specific recording rules.
When voice data is biometric special-category data
A voice recording is personal data under the GDPR when it relates to an identified or identifiable person. The controller still needs an Article 6 lawful basis. Voice is not automatically special-category data merely because it is audio. Under Article 9, biometric data falls within the special categories when it results from specific technical processing and is used for the purpose of uniquely identifying a person.
If Article 9 applies, the controller needs both an Article 6 basis and an applicable Article 9(2) condition. Explicit consent is one Article 9(2) condition, not the only one. Authentication, speaker recognition, and voiceprint use therefore need a separate assessment from ordinary transcription. The official text is in GDPR Articles 4, 5, 6, 7, and 9 on EUR-Lex.
Ask where contributors were located and who acts as controller or processor. Ask what basis and notices apply, and whether cross-border transfers occur. If biometric identification is intended, ask which Article 9 condition applies. Then ask how access, objection, withdrawal, erasure, retention and model-impact requests will be handled. UK processing needs a separate assessment under UK law.
What the signed agreement and evidence pack should cover
For the specific delivery, name the files or collection scope and the acceptance criteria. Set out the permitted and prohibited uses, territory, term, exclusivity, downstream access, retention, deletion, security and any model-related rights. Ask only for warranties that match evidence the supplier can actually produce.
The evidence pack may include the source and license chain, contributor notice or consent records where they apply, collection instructions, a file-to-contributor mapping, transfer records and the agreed QA documentation.
Spirelight does not assume exclusivity, commercial-use scope, biometric permission or model ownership from a catalogue page. These terms, and the records available for a delivery, must be confirmed project by project in the signed agreement.
Still choosing a supplier to run this diligence against? Compare AI training data companies on the records they can actually produce. Use this guide to frame diligence, then have qualified counsel assess the facts and jurisdictions that apply.