Privacy by Design for Voice AI: Data, Notice and Retention
How to build privacy into a phone voice agent from the start: map the data a call creates, give notice, collect less, mask sensitive numbers and set retention.
A voice agent hears things people would not type into a form. Callers give their names, addresses, health worries, account details and sometimes their anger. Because the agent turns speech into recordings, transcripts and summaries, a single call can leave several copies of personal data in several places.

Privacy by design is the habit of deciding, before launch, what you collect, why, who sees it and when it goes away. This guide turns that idea into practical steps for a phone voice agent. It complements GDPR and Call Recording, Handling Personal Information on Calls and Data Retention for Calls.
Map the data a call creates
You cannot protect what you have not listed. Walk through a single call and note every item of data it produces.
Typical data from one voice-agent call
- Audio recordingThe sound of the call, if recording is on.
- TranscriptText of both sides, which may include spoken card or account numbers.
- Summary and tagsA shorter record, plus topics or sentiment where used.
- Caller detailsThe phone number, name and anything captured by the agent.
- Logs and metadataTime, duration, line and results, plus any edits made later.
Ask of each item: why do we have it, who can see it, where is it stored, who else receives it and when is it deleted? The answers become your privacy plan.
Principles that guide the design
- Collect less. Ask only for what the task needs. If you do not need a date of birth, do not ask for it.
- Say what is happening. Tell callers early that an automated assistant is answering and that the call may be recorded, where that applies.
- Limit access. Not everyone needs to hear every call. Give access by role.
- Mask the sensitive. Hide card and phone numbers in transcripts shown to staff by default.
- Keep it only as long as needed. Set retention periods and stick to them.
- Be ready to answer requests. People may ask what you hold about them, or ask for deletion.
Notice and consent
A clear opening is the simplest privacy measure. A sentence naming the business, stating that an automated assistant is answering and mentioning recording gives the caller a fair chance to continue or ask for a person. Rules on recording consent vary a great deal between countries and sometimes between states or provinces; see Call Recording Consent and Two-Party Consent in Call Recording. Disclosure of automation is covered in Should You Disclose That an AI Is Answering?.
A privacy-aware call opening
- Name the businessSay who is answering.
- Say it is automatedState that an automated assistant is on the line.
- Mention recordingWhere required or sensible, say that the call may be recorded and why.
- Offer a personTell the caller they can ask for a person.
- Then ask your first questionDo not collect details before this notice.
Collect and expose less
Ask for the minimum
Every extra question is extra data you must look after. Design each capture step around a purpose. A message-taking flow might need a name, a reason and a way to reach the caller, and nothing more.
Avoid taking payment or card details by voice
Card numbers read aloud end up in recordings and transcripts, and sensitive fields deserve special care. Call does not take payments. If a caller starts to read a card number, the agent should steer them to a proper payment route. See Taking Payments by Phone Safely for the issues involved.
Mask in what staff see
Staff who review calls rarely need to see full card or phone numbers. Showing a masked transcript by default and requiring an explicit step to unmask limits exposure.
Be careful with special categories
Health, financial and other sensitive details attract stricter rules in many places. Keep them out of free-form chat where you can, and have a person handle them. See HIPAA and Phone Calls: The Basics for one example.
Access and retention
| Question | Good practice |
|---|---|
| Who can listen to recordings? | Only the people on the call and managers or admins who need it |
| Who can read transcripts? | Role-based access, with masked numbers by default |
| How long do we keep audio? | As short as the purpose allows, set by a written schedule |
| How long do we keep transcripts and summaries? | Their own schedule, usually no longer than needed |
| What happens at the end? | Permanent removal, tested with a preview first |
| Who is told about changes? | Staff and, where needed, callers through your notice |
Retention is easy to postpone and hard to retrofit. Decide on periods at launch and revisit them when your needs change. Shorter periods reduce the harm of a breach and the work of responding to requests.
Vendors and where data goes
A voice agent usually involves several services: a telephony carrier, a recogniser, a language model and a voice provider. Find out which of them receive the audio or text, in which countries, whether they keep it and whether they use it to train models. Put that information in your privacy notice and your vendor records. Avoid assumptions; ask in writing. The checklist in Contact Center Vendor Checklist helps.
A hypothetical example shows how the plan fits together. A small physiotherapy clinic uses an agent to take messages after hours. Its data map shows audio, a transcript and a summary for each message. The team decides that the summary and the caller's number are enough to follow up, shortens how long the audio and transcript are kept, masks numbers in the staff view and tells callers at the start that an automated assistant is taking a message. The clinic also decides that clinical questions are never answered by the agent but passed to a clinician. None of this needed special software; it needed decisions made early and written down.
Revisit the plan whenever the agent's job grows. A new question flow, a new line or a new integration changes what data is collected and where it goes, and the privacy plan should change with it.
Privacy settings in Call
In Call, a governance area shows how long each kind of data is kept, what is due for removal and when the last purge ran; the platform operator sets the number of days, can preview a purge with a dry run and then remove data past its period permanently. Turn-by-turn conversations are kept for a limited number of days, or less when your transcript retention rule is shorter. In the call history, the transcript can be shown with card and phone numbers masked, and a view shows what would be hidden from a customer asking for their data. Recording rules can be set per queue, campaign or agent. Only people allowed to play recordings can read live transcripts. Review these settings with the person responsible for privacy in your business before you go live.
Privacy-by-design checklist for launch
- Data map written for audio, transcript, summary and details
- Opening notice states automation and recording where appropriate
- Only necessary questions are asked
- Card and phone numbers masked for staff
- Access limited by role
- Retention periods set and tested with a preview
- Vendors and data locations recorded
- A route exists for data requests
Frequently asked questions
What does privacy by design mean for a voice agent?
It means deciding what data the agent collects, who can see it and how long it is kept before launch, and building those choices into the design rather than adding them afterwards.
Do I have to tell callers it is recorded?
Many places require some form of notice or consent for recording, and the rules vary. Check the law where you and your callers are, and take advice if unsure.
Is a transcript personal data?
Often yes, since it may contain names, numbers and other details that identify a person. Treat transcripts, summaries and recordings with similar care.
How long should I keep call data?
Only as long as you need it for the purpose you stated, and as the law requires. Write a schedule, apply it consistently and review it regularly.
Should the agent take card numbers?
It is better to avoid taking payment details by voice. Direct callers to a proper payment route instead. Call does not take payments.
Can I rely on a vendor to handle privacy for me?
No. You remain responsible for how you use the service. Ask each vendor where data goes, whether it is kept and how it is used, and record the answers.