GDPR and voice data: a practical AI-project review Identify personal data, processing purposes, lawful-basis questions and evidence needed before using voice recordings for AI. Includes an illustrative review matrix. Using voice recordings for AI requires a review of the particular people, purposes, processing operations and jurisdictions involved. A recording can contain personal data without every voice application being biometric identification. A supplier’s copyright license does not settle the privacy analysis, and removing a speaker’s name does not necessarily make a recording or model anonymous. This guide explains the questions an engineering, privacy and procurement team can organize for review; it does not certify a dataset or determine a lawful basis for a particular project. Key distinction Personal voice data versus biometric identification Review unit Each processing purpose and responsible party Operational evidence Source, permissions, retention and recipients Scope Project-specific legal assessment Start with the actual processing, not a compliance label A statement such as “GDPR-ready audio” is too broad to tell an engineering team what it may do. Write down the intended operations: receive original recordings, prepare transcripts, train a recognizer, share examples with an annotation partner, distribute weights, or operate a voice product. The people receiving the material and the information exposed can differ at each stage. Also establish why GDPR might apply. The answer is not simply the location of a storage bucket or the incorporation address of the buyer. Ask the responsible privacy reviewer to assess the organizations, people and activities involved. Record the conclusion and its scope instead of treating a commercial vendor’s location as an exemption. Separate identifiable speech from biometric identification [GDPR Articles 4 and 9](https://eur-lex.europa.eu/eli/reg/2016/679) distinguish personal data and biometric processing for unique identification. Voice recordings may identify a person through their voice or the conversation’s content; they are not automatically special-category biometric data merely because they contain speech. For a practical inventory, record whether names, contact details, location references, sensitive discussion topics or identity-related voice features are retained. A transcription project and a speaker-authentication project can use similar files for different purposes. Do not carry a prior assessment across those uses without reviewing the change. Document the selected basis and its limits GDPR Article 6 lists several lawful bases. A written copyright license is not itself a substitute for identifying the appropriate personal-data basis. Where consent is used, the actual information provided to participants and the agreed purpose matter; do not describe every source agreement as consent just because it has a signature. The [EDPB’s Opinion 28/2024](https://www.edpb.europa.eu/system/files/documents/2024-12/edpb_opinion_202428_ai-models_en.pdf) discusses necessity and balancing when legitimate interest is proposed for AI processing. That is an assessment to substantiate, not a shortcut that a dataset invoice establishes. Give reviewers the source context and realistic alternatives, including a smaller collection or less identifying representation. An illustrative voice-data processing matrix The following is an authored example for a proposed customer-support recognizer. It describes questions to answer, not an approved collection or a legal conclusion. Keeping the rows separate reveals where a source proposal is incomplete. Operation Information to record Question before proceeding Source intake Recording source, dates, participant information and original purpose What evidence supports this proposed reuse? Transcript preparation Identifiers in text, annotation partner, access scope Can unnecessary identifying details be excluded without damaging the task? ASR fine-tuning Selected segments, stable IDs, split groups, training location Which assessment covers this purpose and these recipients? Model distribution Weights or hosted access, intended recipients and documented risks Does the review cover distribution as well as internal training? Retention and correction Source versions, derivatives, contact route and operational owner How will a valid request be identified and acted on? Explain what the matrix changes Suppose an archive is cleared for internal recognition research but an annotation subcontractor has not been assessed. The project has a specific unresolved dependency; it is not useful to call the entire archive either “compliant” or “noncompliant.” The next action is to resolve that recipient and handling scope before making the transfer. Likewise, a team may need technical features such as speaker grouping to keep evaluation independent without needing public speaker names. Store the minimal project identifiers and keep any necessary identity mapping separately restricted. This is an operational design choice to discuss with the reviewer, not proof that the audio has become anonymous. Anonymisation and withdrawal need realistic engineering plans The EDPB’s AI opinion treats model anonymity as a case-specific question. Replacing a name with a speaker code is therefore not sufficient evidence that every relevant risk has disappeared. Document the transformation and the residual information rather than promising anonymity based on a filename convention. Create a lineage map from source recording to segments, transcripts and released dataset versions. A correction or deletion process can then locate affected artifacts. Do not promise that removing a source file automatically removes its influence from every existing trained model. The actual response depends on the applicable rights, circumstances and feasible, reviewed procedures. Keep AI Act obligations separate The [EU AI Act](https://eur-lex.europa.eu/eli/reg/2024/1689) contains distinct requirements for different roles and systems. Its general-purpose model provisions include copyright-policy and training-content-summary obligations. A speech-data purchase does not by itself establish which obligations apply to a buyer or satisfy them. Ask the project reviewer to identify the organization’s actual role, applicable provisions and timing. From the data side, retain evidence that can support that review: source descriptions, preparation records, limitations and version history. Avoid selling a generic documentation package as a universal AI Act compliance certificate. What to request before receiving a sample Begin with a high-level source description and a proposed handling plan. A useful review packet exposes open issues without distributing private participant records to everyone evaluating a purchase. Redacted examples and controlled review may be more appropriate than attachments in an initial email. Identify the project purpose, responsible organizations and proposed recipients. State which personal or sensitive information the task needs and why. Describe the source, participant information and supporting documents actually available. Specify retention, access, transfers, security review and a contact for rights requests. Mark unknowns and assign an owner before source access or expansion. Is every voice recording special-category biometric data? No. A recording may be personal data while the biometric-identification analysis depends on the processing and purpose. Its content may also contain other sensitive information. Assess the actual use instead of classifying all speech files under a single label. Does a commercial data license settle GDPR? No. A data license addresses the contractual grant from the supplier. Privacy review also considers the processing, people, parties and applicable obligations. Keep the copyright and personal-data decisions linked but distinct. Can a supplier guarantee that a trained model is anonymous? A broad guarantee is not evidence. Ask what was assessed, what testing or safeguards support the conclusion, and which model and use it covers. The EDPB treats anonymity as a case-specific determination. Research method: Fiund research desk; public sources, explicit worked-example labels and project-specific availability review. Editorial contact: hello@fiund.com. Sources Regulation (EU) 2016/679, GDPR: https://eur-lex.europa.eu/eli/reg/2016/679 Opinion 28/2024 on personal data in AI models: https://www.edpb.europa.eu/system/files/documents/2024-12/edpb_opinion_202428_ai-models_en.pdf Regulation (EU) 2024/1689, consolidated AI Act: https://eur-lex.europa.eu/eli/reg/2024/1689