← All articles
Blog

Audio Datasets for AI: Types, Sources and What to Check

Audio datasets power speech recognition, voice assistants, call analytics, speaker identification, sound event detection and, increasingly, multimodal models that listen as well as read. Building a good model depends on audio that matches the real conditions it will face: accents, background noise, domain vocabulary and natural conversation. This guide explains the main types of audio datasets, how they are annotated and sourced, and what to check before using them.

Types of audio datasets

Read speech

Speakers read prompted text. The transcripts are clean and the coverage is controlled, but the speech is less natural.

Conversational speech

Natural dialogue between two or more people, such as phone calls, meetings or interviews. It is harder to transcribe, and much closer to real use.

Call-centre and customer-service audio

Conversations between agents and customers, often linked to outcomes such as resolution, sale or complaint. Valuable for analytics and agent-assist tools, and highly sensitive.

Domain-specific speech

Speech from particular fields, such as engineering, logistics, healthcare or legal, with specialised vocabulary.

Multilingual and accented speech

Coverage across languages, dialects and accents to reduce performance gaps.

Non-speech audio

Environmental sounds, machinery, alarms and music, used for sound event detection and industrial monitoring.

How audio datasets are annotated

  • Transcription: verbatim or clean, with conventions for disfluencies.
  • Timestamps: word or segment alignment.
  • Speaker diarisation: who spoke when.
  • Speaker attributes: where consented and lawful, such as accent or language.
  • Intent and outcome labels: for conversational data.
  • Sound event labels: start and end times of non-speech events.
  • Quality flags: noise, overlap and recording issues.

See what is data annotation.

Technical characteristics to check

  • sample rate and bit depth
  • mono or stereo, and channel separation for calls
  • codec and compression
  • signal-to-noise range
  • recording devices and environments
  • total hours, speaker count and balance
  • distribution across accents, ages and languages

Where audio datasets come from

  • Open datasets: many speech corpora are available under open licences. Check the licence terms for commercial use.
  • Specialist vendors: commission custom collection with consented speakers.
  • Licensed archives: broadcasters, podcasters and media owners.
  • Business recordings: call recordings, meeting recordings and voice notes, licensed from businesses, with consent and privacy issues resolved.
  • Synthetic speech: text-to-speech for augmentation, with limits. See synthetic vs real data.

Consent, privacy and rights

Audio is personal data when it relates to identifiable people, and a voice can itself identify someone. Biometric uses such as speaker identification bring additional legal requirements in many places. Before using audio datasets, check:

  • Consent and notice: were speakers told how the recordings would be used? Call recordings made for "training and quality purposes" may not cover AI model training by a third party.
  • Lawful basis: under the applicable privacy law, for each intended use.
  • Third parties: customers in call recordings did not contract with the licensee.
  • Sensitive content: health, financial or other special category information spoken aloud.
  • Redaction: removing names, card numbers and addresses from both audio and transcripts.
  • Licence scope: training, evaluation and commercial use. See data licensing agreements.
  • Provenance: documented chain of custody. See data provenance.

Linking audio to business context

Audio becomes more valuable when it connects to records, for example a support call linked to the ticket, the order and the resolution. That lets a model learn not just what was said, but what happened as a result. Maevar's focus on linked workflows applies here too.

How Maevar helps

Maevar introduces record owners to vetted buyers, typically AI teams looking for business records, including communication data where rights and privacy allow, linked to the cases they relate to. The buyer pays our introduction fee. The owner and the buyer agree terms, preparation and how personal details are handled, directly. Tell us your task and the sectors that matter. Discuss your use case.

Common pitfalls

  • Training and testing on recordings from the same speakers, which inflates accuracy
  • Unbalanced coverage, for example few speakers of particular accents or ages
  • Inconsistent transcription conventions between annotators
  • Losing the metadata that links recordings to calls, tickets or meetings
  • Assuming open datasets allow commercial use

Splitting audio datasets

Split by speaker, and where relevant by recording session or organisation, so the test set measures generalisation to new voices and conditions. Keep a held-out set that reflects the target deployment, such as telephone-quality audio for a call-centre product.

Storage and security

Audio files are large and sensitive. Store them encrypted, restrict access, log every use, and make sure deletion obligations can be met. Transcripts and audio should be governed together, because redacting one but not the other leaves personal data exposed.

Business audio linked to outcomes

In many businesses, the most useful audio is not a stand-alone recording but part of a case. Examples are a site call about a delayed delivery, a support call that led to a replacement part, or a sales call that preceded a quotation. When recordings are linked to the case records, models can learn to connect what was said with what was decided.

FAQ

What is an audio dataset?

A collection of audio recordings, usually with transcripts or labels, used to train or evaluate AI models.

Where can I find audio datasets?

From open corpora, specialist vendors, licensed media archives and businesses that license their recordings.

Are call recordings usable for AI training?

Only where consent, notice and lawful basis cover that use, and personal data is handled appropriately.

How many hours of audio do I need?

It depends on the task and the base model. Fine-tuning a strong base model can need far less than training from scratch.

What makes audio data high quality?

Accurate transcripts, varied speakers and conditions, clear documentation and clean rights.

Maevar privacy notice

21 October 2026

Who we are

Maevar is operated by Marcias Limited, company number SC653353. Marcias Limited is responsible for the personal information covered by this notice.

Registered office: 51 Watt Road, Hillington, Glasgow, G52 4RY, United Kingdom.

For privacy questions or requests, email hello@maevar.com.

This notice covers this website and enquiries sent to Maevar. Any proposed introduction of a record owner to a buyer, or any sale or licence they agree, requires a separate review of the relevant rights, privacy requirements and agreed terms.

Enquiries and information you provide

The enquiry fields help you prepare an email containing your work email address, organisation, task summary and any optional format or timing details. The draft is prepared on your device. The website does not submit or store it: you choose whether to open, review and send it using your email app. There is no file-upload facility.

Please provide only a non-confidential summary. Do not include datasets, personal records, passwords or other sensitive information.

When you send an email, we receive the message, your contact details and any other information you choose to include. Richard McKay handles enquiries. Authorised service providers and connected tools, including AI-assisted tools, may support the handling of correspondence.

Why we use your information

We use enquiry information to respond, understand your requirements, assess whether we can help and discuss relevant business opportunities. We rely on our legitimate interests in managing business enquiries and developing appropriate business relationships, while considering your rights and reasonable expectations.

We also have a legitimate interest in keeping the website and email services secure and reliable. Where we must retain or disclose information to meet a legal obligation, we rely on that obligation.

Website and email services

We use OpenAI's ChatGPT Sites to host this website, Cloudflare for website delivery, security and email routing, and Google Workspace to receive and manage email enquiries. These services process information needed to deliver and protect the website and email service. This can include IP addresses, browser information, access times and technical or security logs, as well as email information when you contact us.

Optional analytics is controlled separately from necessary hosting and security services. Cloudflare uses a bot-protection cookie called __cf_bm, which normally expires after 30 minutes of inactivity. More information is available in Cloudflare's cookie documentation.

Optional analytics and your choice

Google Analytics loads only after you accept analytics. Rejecting keeps optional analytics off.

We load Google Analytics only after you accept it. Rejecting does not stop you using this website or contacting us. Necessary hosting, delivery and security services continue to operate, including their technical logs.

With your permission, analytics measures page visits and limited website interactions. We use fixed page information without search queries or URL fragments. We do not send your name, email address, organisation, enquiry text, form answers or the contents of email-draft links to Analytics. Analytics is not a record of the contents of your enquiry.

The email preparation tool may record that an email draft was prepared, without any of its contents. This is an expression of interest only: the website cannot tell whether you send the email. It is not counted as a submitted enquiry.

No Google Ads, Meta or LinkedIn advertising tags are activated by these controls. Advertising storage, advertising user data and ad personalisation remain disabled. We do not use enhanced conversions or upload contact details to Analytics.

Your privacy choice is stored on this website in your browser for up to six months. If you accept analytics, Google Analytics may set first-party cookies named _ga and _ga_ followed by the property identifier. Our code sets a maximum cookie lifetime of six months; your browser may apply a shorter limit. Google processes the analytics information and may process it outside the UK. See Google’s privacy policy. Our Google Analytics property retains user-level and event-level data for two months, without restarting that retention period when you return. This setting does not limit how long Google retains standard aggregated reports. Optional Google data sharing, Google Signals, user-provided data collection, granular location and device collection, and advertising personalisation are switched off.

Use Cookie settings in the footer to change your choice. Withdrawing analytics consent stops new measurement and reloads the page into a no-analytics state, so save any unfinished enquiry first. It also removes the relevant first-party analytics cookies where the browser permits. This does not erase information already sent to Google. We do not replay interactions that happened before you consented.

Our service providers may process information outside the UK. Their published data-processing terms describe the applicable international-transfer safeguards, including recognised adequacy arrangements and contractual safeguards:

Contact hello@maevar.com if you would like further information about these arrangements.

How long we keep information

We review unsuccessful enquiries 12 months after the last substantive contact and delete them unless there is an ongoing business or legal reason to retain them. For example, information may still be needed for an active discussion, to meet a legal obligation, or to establish, exercise or defend legal claims. Where we retain information longer, we keep it only for as long as that reason applies.

Enquiries that lead to a business relationship and related contract records are kept according to the needs of that relationship and applicable legal requirements. The 12-month enquiry review period is not a guarantee that every provider's security log or backup is erased on the same date; those records are subject to the relevant service's retention and deletion arrangements.

Your rights and complaints

Depending on the circumstances, you may ask to access, correct or delete your personal information, restrict its use, or receive a portable copy. You may also object to processing based on legitimate interests. These rights are subject to applicable conditions and exceptions.

Email hello@maevar.com to make a request or raise a concern. You can also complain to the Information Commissioner's Office through ico.org.uk/make-a-complaint.

Changes to this notice

We will update this notice when our website or information-handling arrangements change. The date above identifies the version you are reading.