AI receptionists in Europe: recording, data location and AI disclosure
Check AI disclosure, call recording, subprocessors and data retention before choosing an AI receptionist for an EU business.
Before an AI receptionist answers your business calls, establish what callers will be told, which data the service processes and who can access it. Ask the provider to put those answers in writing.
“EU-hosted” describes part of the setup. You still need to understand the voice provider, recordings, transcripts, support access and any services that receive call summaries.
This guide focuses on EU deployments and breaks down the main questions to ask before buying. It provides general information, checked on 6 November 2026. You need to assess how national recording rules and sector-specific requirements apply to your business.
Keep four decisions separate
| Decision | What you need to establish |
|---|---|
| AI disclosure | How the caller learns that they are speaking with AI |
| Personal-data processing | Why information is processed, the applicable legal basis and what the caller is told |
| Recording | Whether audio is retained, for what purpose, and under which applicable rules |
| Supplier access and retention | Which organisations receive the data, where, and for how long |
An AI disclosure does not settle whether a recording is lawful. A recording notice does not explain every use of personal data. A data processing agreement does not choose the legal basis for your business.
You need answers for the actual call flow you intend to use.
Tell callers when they are speaking with AI
The Commission’s AI Act timeline identifies 2 August 2026 as the general application date, with exceptions.
Under Article 50(1), providers must design systems intended to interact directly with people so those people are informed they are interacting with AI, unless this is obvious in the circumstances. Article 50(5) requires the relevant information to be provided clearly and accessibly by the first interaction or exposure.
For a phone service, ask how the provider satisfies that requirement at the start of the AI interaction. Do not assume a natural-sounding voice makes the disclosure unnecessary. Distinguish the provider’s obligations from your own responsibilities as the business deploying the service.
A short introduction could be:
I’m the AI assistant for Harbour Heating. I can take a callback request or help you reach the office.
That is an illustrative introduction for a fictional business, not a complete privacy or recording notice. Offer only actions that exist in the configured service.
Check the introduction in every caller language you support. Also check what callers hear when they are transferred into the AI branch after a keypad menu.
Decide why you need each piece of information
A callback request might need a name, phone number and broad reason for calling. It may not need a complete conversation recording.
List each purpose separately: answering a question, booking an appointment, documenting a request or reviewing service quality. Identify the legal basis for each relevant processing activity and the information you must provide.
GDPR Article 6 provides several possible lawful bases. Consent is one of them, not an automatic answer to every processing question. Article 13 addresses information given when collecting data from a person. Article 9 adds requirements for special-category data, including health information. GDPR text.
For example, a caller seeking an appointment may volunteer sensitive details even when your script asks only for a date. Decide how the service should respond, what it should avoid collecting and when a staff member should take over.
Have the relevant legal or privacy adviser assess your intended use, especially in healthcare or other sensitive settings.
Check what “recording off” changes
Recording usually refers to retaining the call’s audio. A conversational service may still process speech during the call, and may separately create text, summaries or operational logs.
Ask about each data type:
| Data type | Questions to ask |
|---|---|
| Live audio | Which providers receive it during the call? Do they retain any copy? |
| Stored audio | Is retention enabled? Who can listen to or download the audio? |
| Transcript | Is one created when audio recording is off? How long is it kept? |
| Summary and extracted fields | Where are they sent? Can a wrong detail be corrected? |
| Call metadata | Are the caller’s number, call time, destination and outcome retained? |
| Backups and provider logs | What is the deletion schedule, including after account closure? |
The absence of a saved audio file does not establish that no personal data is processed. Assess the full data flow.
If you enable recording, define its purpose and review the rules applying to your business and callers. A sentence saying a call may be recorded does not by itself establish valid consent where consent is required.
Give the team a clear procedure for callers who object or ask for another way to contact you. Confirm that the proposed alternative is available.
Map the supplier chain
Ask the provider to show the route from the caller to the final business record. A useful map may include:
- The telephone carrier.
- The call-routing service.
- The speech and AI providers used for a conversational branch.
- Audio or transcript storage.
- Calendar, customer-system or email destinations.
- Support and backup systems with access to the data.
Mark which steps are used on every call and which are activated only for selected tasks. Record data locations and organisations, rather than using a single country label for the whole service.
A company can host its application in Germany while another provider processes voice elsewhere. Ask about access as well as storage.
Identify the controller, processor and subprocessors
The controller decides the purposes and means of processing. A processor handles personal data on the controller’s behalf and in accordance with its instructions. A subprocessor performs part of that processing for the processor.
Your business will often be the controller for its customer call handling, but roles depend on the actual processing. The supplier may have separate controller responsibilities for other activities. Ask it to identify those distinctions.
The relationship needs an appropriate contract covering the processing and responsibilities. Check what the contract says about assistance with data-subject requests, security, deletion or return of data, and the use of subprocessors. The EDPB’s guide to controllers and processors explains those roles and contractual duties.
Request the subprocessor list before signing. Ask how you will hear about changes and what options you have if a proposed change is unacceptable.
Examine international transfers
Processing outside the European Economic Area is a separate question from the location of the main application server.
Ask whether personal data is made available to another organisation outside the EEA, including through provider access. Where a transfer occurs, request the applicable transfer mechanism and the supporting assessment or safeguards relevant to the arrangement.
The EDPB explains that transfers may use an adequacy decision or appropriate safeguards, with limited derogations in some circumstances. Those transfer requirements sit alongside the other GDPR obligations. EDPB guidance on international transfers.
Avoid treating a contract reference or a data-centre location as the whole answer. The processing chain and the legal arrangements need to match.
Choose retention periods by purpose
Create a small retention table before activating the service.
For each data type, record its purpose, who can access it, how long it is kept and how it is deleted. Check whether deleting a call in the dashboard also deletes copies held by other providers. Ask how backups are handled.
Keep recordings, transcripts and callback records in separate rows. Their uses may differ, and a single “30-day retention” label may apply to only one of them.
The GDPR’s data-minimisation and storage-limitation principles require attention to what is necessary and how long it remains necessary. Longer storage needs a reason. GDPR Article 5.
Test a deletion or correction request using test data. Confirm who receives the request and how they identify the relevant records without revealing another caller’s information.
Questions to send an AI receptionist provider
You can copy these questions into procurement notes or use the vendor checklist.
| Question | Evidence to request |
|---|---|
| What does the caller hear at the first AI interaction? | The exact greeting and configuration |
| What data is processed with recording disabled? | A data-type inventory |
| Who receives live speech, text and summaries? | A data-flow diagram and subprocessor list |
| Where does each provider process or access the data? | Processing-location and access information |
| What roles does each organisation have? | The contract and data processing agreement |
| What happens when a caller asks for another way to contact the business? | A tested alternative workflow |
| Which data is used for model improvement or training? | Contractual terms for each relevant provider |
| What are the separate retention periods? | Audio, transcript, metadata and backup schedules |
| How do deletion and correction requests work? | A documented procedure and test result |
| What happens after a breach or subprocessor change? | Notification commitments and contact details |
A provider’s willingness to give specific answers is useful. If it displays a broad compliance badge, ask what the badge covers and what evidence supports it.
How this applies to Double Menu
Double Menu publishes details of its operator, hosting arrangements, subprocessors and recording controls on its security and data page. The application, database and voice servers run in Germany; the page also describes arrangements for subprocessor processing outside the EEA.
On a keypad-only call, caller speech is not sent to an AI provider. A conversational AI branch has a different data path. Recording is off by default, and retained audio has separate controls from other call information.
The data processing agreement is Schedule 1 of the terms. Read it alongside the planned configuration, and ask about any processing your intended workflow adds.
Before activation, put the greeting, data flow, retention choices and responsible contacts in one place. Use those details when testing the service and when explaining it to your callers.