Meet Tsuno at Sirha Lyon 2027 · Stand S.57Learn more
EN FR
Try the demo
Menu

Team and management

Voice data at work: what to keep and for how long

At work, keep as little as possible: audio rarely, text briefly, confirmed actions as long as traceability requires. Every period is written down in advance.

Published on

On a desk, next to an open notebook, a small device and a light earpiece rest on a privacy notice.

For a voice assistant at work, the rule is to keep as little as possible and to write it down beforehand. The audio often has no reason to be kept once the request is handled. The text of questions is kept briefly, for a specific purpose. The confirmed action (a task done, a log entry) follows the traceability period of the activity. Each period appears in the notice given to staff, and each employee can ask what has been kept about them. This article gives pointers under EU law and French practice, not legal advice.

Thursday, 4:30 p.m., the "retention" line is blank

Fabrice runs two bakery cafés. He is drafting the privacy notice before offering a voice assistant to his teams. Everything is filled in except one line: "Retention period for voice data". Bintou, the production lead, reads over his shoulder.

"What does voice data mean? My voice, or what I asked?"

Fabrice realises there are at least three things behind that phrase, and he does not know the retention period for any of them. Fictional scene and people.

Why retention is the question everyone forgets

You choose a tool for what it does

In a demo, you watch the answer, the speed, the clarity. Nobody asks what happens to the sentence once the answer is given. Yet that is what remains when the tool is switched off.

"Voice data" covers three things

Audio is the recorded voice. Text is the transcript of the request ("what is the cleaning procedure for the dough sheeter?"). The recorded action is what the person confirmed: a ticked task, a logged reading, a reported fault. The three differ in sensitivity and in usefulness.

A voice says more than the question

A voice can identify someone, and it carries tiredness, an accent, sometimes a nearby conversation. It is the most intrusive of the three, and often the least useful once transcribed. If it is processed with specific technical means to identify a person, it becomes biometric data, under the stricter regime of GDPR Article 9.

The principles, in plain terms

  1. A period proportionate to the purpose. Article 5 of the GDPR requires that data is not kept longer than necessary for its purpose. The French data protection authority, the CNIL, describes a three-stage cycle in its practical guide to retention periods (in French): the active base (day-to-day use), intermediate archiving when a legal obligation or possible dispute justifies it, then deletion or anonymisation.
  2. Minimisation. Collect and keep only what serves the purpose. If the purpose is helping a commis find a procedure, recording their voice is not needed once the request is understood.
  3. One period per type of data. Audio, text and action serve different purposes; they need not share a period.
  4. A careful benchmark. In its guidance on listening to and recording calls in the workplace (in French), the CNIL sets, for call recordings made for training or assessment, a maximum of six months for recordings and one year for analysis documents. That is not the rule for a voice assistant, but it is a useful ceiling: an assistant used neither to train nor to assess has no reason to go further.
  5. Prior notice. The period, or the criteria that set it, appears in the notice given to employees (GDPR, Article 13; in France, Labour Code article L1222-4). In 2026 the CNIL published a reference framework on HR retention periods (in French) that helps fill in the register for standard HR processing.
  6. The right of access. Anything kept can be requested by the employee (GDPR, Article 15), including the audio and text of their requests. What is not kept does not have to be retrieved: one more reason to keep little.

The table to fill in with your vendor

The periods below are starting points for discussion, not standards. As the controller, it is up to you to set and justify them.

Type of dataPurposeReasonable period to discussQuestion for the vendor
Audio of the requestUnderstanding the sentenceNot kept beyond processing, unless a written purpose requires itIs the audio kept? Where, for how long, who listens to it?
Text of the requestAnswering, fixing a bad answerShort, weeks rather than yearsIs the text stored? Can the manager read it?
Answer givenChecking which source was readAligned with the text of the requestDoes the answer record which sheet was used?
Confirmed actionTraceability (task, log entry, fault report)That of the activity concernedWhat does the log keep, and for how long?
Account and sessionOpening a session, applying access rightsLength of employmentWhat happens to the account when someone leaves?
Usage countersRunning the toolNo limit if truly aggregated and anonymousCan the statistics be traced back to a person?

One column is deliberately missing: "who can access it". Add it. For each row, the answer should be a list of roles, not "the admins".

Five questions an employer must ask

  1. Is the audio kept? If so, why, and can it be turned off?
  2. Is the text of requests kept, and for how long?
  3. Where is this data stored, and which subprocessors handle it, in which countries?
  4. Who can read it: the employee, the manager, head office, the vendor? The employee's side is covered in can your manager read your questions to an assistant?
  5. How is it deleted when the contract ends, and how do we answer an employee's access request?

Ask for written answers, and copy them as they are into your register and your notice.

Common mistakes

  • Writing "as long as necessary" in the notice. That is not a period.
  • Keeping the audio "just in case". A recording with no purpose is data too many, and one more access request to handle.
  • Using the text of questions to assess an employee. That changes the purpose, and ends trust in the tool.
  • Mixing up the action log and conversation history. The first serves traceability; the second does not have the same justification.
  • Forgetting the end of the vendor contract. A retention period without a deletion date is still just a promise.

What to measure

  • The number of rows in the table without a written period: none before launch.
  • The response time to an employee's access request, against the GDPR's one-month deadline.
  • The date of the last review of retention periods with the vendor, to repeat whenever a feature changes.

What Tsuno publishes, and what we cover in a meeting

Tsuno San is the smart voice assistant for teams. San Voice is available as a demo; San Audio, the hands-free mode, is being explored and tested. On retention, here is what our Trust and data page says, with nothing added:

  • the app and its data are hosted in the European Union, in Germany;
  • the AI models (assistant, voice note transcription) come from providers based in the United States, and the privacy policy details these transfers and their safeguards;
  • in the public demo, questions and transcripts are not kept, and only aggregated technical counters are recorded;
  • clock-in check photos are deleted seven days after they are taken;
  • the action log keeps who, when and what, with the state before and after;
  • when your subscription ends, your data stays available to you for thirty days, in a standard format;
  • for your teams, Tsuno acts as a processor, on your instructions.

For the audio and text of requests made to San in real use, the Trust page sets no retention period: ask us in a meeting and we will answer in writing, so you can copy that answer into your record of processing. San is presented on the Tsuno San page.

Further reading

The overall frame is in AI, voice and privacy at work: the guide. For the CNIL rules on listening and impact assessments, read a microphone at work: what the law says in France. For what must never be written about an employee, even briefly, see MCP and sensitive data: what AI must never record about an employee.

Key takeaway

Audio, text and actions are not kept the same way: the voice as little as possible, the question briefly, the action as long as traceability requires. A period that is not written in the notice does not exist for the employee reading it.

Frequently asked questions

How long can employers keep employees' voice recordings under the GDPR?

The GDPR sets no single period: retention must be proportionate to the purpose and set in advance. For call recordings made for training or assessment, the French data protection authority (CNIL) sets a maximum of six months for the recordings. For a voice assistant, the audio often does not need to be kept at all once the request is handled.

Should audio, text and actions be treated separately?

Yes. Audio is the voice itself, text is the transcript of the request, and the action is what the person confirmed (a task, a temperature log). They are not the same data or the same purpose, so they do not get the same retention period.

Can an employee ask for recordings of their voice?

Yes, if they are kept. The GDPR right of access covers all data about them, including the audio and text of their requests. The employer answers within one month, extendable by two months for complex requests.

What should the privacy notice say about retention?

The retention period, or the criteria used to set it, for each type of data. A line saying "to be completed" or "as long as necessary" is not enough: employees must know what is kept and for how long.

Are voice assistant usage statistics personal data?

As long as they can be traced back to a person, yes. Truly aggregated, anonymous counters fall outside the GDPR, but a table of questions asked per employee is still personal data.