Guides

GDPR and the AI Act: how to use AI voice agents compliantly in Spain

A practical guide to GDPR and the AI Act for AI voice agents in Spain: disclosure, call recording, health data, retention, LOPDGDD and a pre-launch checklist.

Foxy in a detective cap with a magnifying glass, reviewing data protection rules

Putting an AI voice agent on the phone means processing personal data (voice, name, phone number, the reason for the call) with a technology EU law watches closely. The good news: complying with GDPR and the AI Act for AI voice agents doesn't need a legal department, just getting a handful of specific things right. This guide sets them out for business owners in Spain: what each rule says, what the platform does by default and what's up to you.

Note: this article is for information only and is not legal advice. Every business should check its case with its adviser or data protection officer.

The rules that apply

  • GDPR (Regulation (EU) 2016/679): legal bases, information, minimisation, retention, rights, processors, transfers.
  • LOPDGDD (Organic Law 3/2018): Spain's implementation of the GDPR, including advertising opt-out systems.
  • AI Act (Regulation (EU) 2024/1689): transparency duties and risk categories.
  • General Telecommunications Act, if you make outbound marketing calls (covered in AI outbound calls).
  • Law 10/2025 on customer service, if your company is within its scope.

1. Transparency: say it's an AI from the first second

Article 50 of the AI Act has applied since 2 August 2026. Systems that interact directly with people must be designed so those people know they're dealing with an AI, clearly and from the first interaction, unless it's obvious (European Commission). On the phone it isn't obvious: a good synthetic voice is easy to mistake for a person.

What CallSmarter does: the first sentence of every call handled by an agent says it's an AI assistant and that the conversation is recorded. It's platform text, in each of the 9 call languages, that customers can't remove in their settings. On the website button, the notice also appears in writing before the call starts, with a link to your privacy policy.

2. Controller and processor: who's responsible for what

Your business decides what your customers' data is used for, so you're the controller. CallSmarter processes that data on your behalf to provide the service: we're the processor, under a data processing agreement per Article 28 GDPR, which you can read in our data processing agreement.

In practice, it's up to you to:

  • have a legal basis for each processing activity;
  • inform people (Articles 13 and 14 GDPR);
  • set retention periods beyond the platform defaults;
  • handle access, erasure and objection requests, with our help.

When a customer calls to book or make an appointment, the usual basis is taking steps at their request prior to a contract, or performing one, or legitimate interest in handling their request. Recording has its own purpose (quality, evidence of what was agreed) and must be disclosed. The AEPD stresses that callers should be told at the start who the company is and what the call is for, and that any clear objection must be respected (AEPD).

What you need to prepare: a privacy policy that mentions the AI agent, the recording and its purpose, the processors (including the voice-model provider) and retention periods. The website button lets you link it in the consent window.

4. Minimisation: ask only for what you need

An agent could ask anything. Whether it should is another matter. Our templates are written to ask for the minimum:

  • Restaurant: name, party size, date and time, phone, allergies in the caller's words.
  • Dental clinic: name, whether they're a patient, reason in their words, preferred times. No medical history, ID or health card.
  • Home services: name, address and access, equipment, symptom.
  • None of them: bank or card details.

Health data: extra care

The reason for a dental visit is health data, a special category under Article 9 GDPR. It requires an exception under Article 9(2) and stronger safeguards. If that's your case, check the applicable basis with your adviser and consider a data protection impact assessment (DPIA). The AEPD's guide on processing that embeds AI (in Spanish) is a good start. More context in our guide to dental clinic phone answering.

5. Retention and erasure

  • Recordings: 90 days by default on the platform, then deleted or anonymised. You can request earlier deletion.
  • Other data (requests, contacts, transcripts in the CRM): kept as long as you need them, with dashboard tools to delete them.
  • When the service ends: deletion or return of the data, as you choose, within the periods in the processing agreement.

6. Providers and international transfers

To be clear: speech is processed by an OpenAI voice model, acting as sub-processor, which may process data outside the European Economic Area (USA). In that case the transfer relies on GDPR Chapter V safeguards: an adequacy decision where applicable, or standard contractual clauses with any supplementary measures. The list of sub-processors and their locations is in the processing agreement, and we notify you in advance of any change.

7. Security and access

Some measures the platform applies by default:

  • Alerts without full contact details. Telegram or email alerts carry a masked name and number plus a dashboard link, unless a user with permission to see phone numbers decides otherwise for that channel.
  • Role-based permissions: not everyone on your team sees full phone numbers or can listen to recordings.
  • Tamper-evident activity log of dashboard actions, and two-factor sign-in.
  • Signed webhooks, so your system can verify an alert came from us.
  • Locked-down tools: the agent can only act on the contact of the current call, reducing the risk of someone manipulating it to obtain other customers' data.

8. Automated decisions and high risk

Article 22 GDPR restricts decisions based solely on automated processing that have legal or similarly significant effects. Our agents don't make such decisions: they don't accept or reject anyone, confirm bookings or appointments, or set prices. They record; your team decides.

As for the AI Act, Annex III lists as high-risk, among others, systems that evaluate and classify emergency calls or prioritise the dispatch of emergency services, and emergency patient triage systems. An agent handling bookings or appointments generally isn't on that list. That's precisely why our agents don't do emergency triage: if life may be at risk, they tell the caller to hang up and call 112. The urgency levels they assign (a water leak versus a routine service, say) organise your company's workload; they don't dispatch emergency services.

9. The right to talk to a person

Spain's Law 10/2025 bars companies within its scope (essential services and large companies) from using bots as the only customer service channel and requires access to a human at any time (BOE, Article 8). Even outside its scope it's good practice: with CallSmarter, when a caller asks for a person, the agent logs it as high urgency and your team is alerted to call back.

GDPR and the AI Act: checklist before launching a voice agent

  • [ ] The agent identifies as AI and mentions recording at the start.
  • [ ] Your privacy policy covers the agent, recording, processors and retention.
  • [ ] The data processing agreement is signed.
  • [ ] The agent collects only the minimum fields.
  • [ ] If you process health data, you've checked the Article 9(2) exception and considered a DPIA.
  • [ ] You've decided who sees full details and who sees summaries only.
  • [ ] You've defined what happens when someone asks for a person.
  • [ ] For outbound marketing calls, you have consent or a legal basis and you check opt-out registers.
  • [ ] You know how to handle a request to delete a recording.

Bottom line

Compliance isn't a brake on using AI on the phone; it's what makes customers trust it. To hear what a good AI disclosure sounds like, talk to Foxy: she introduces herself before saying anything else. And if you'd like to review your case, get in touch; we'll show you the processing agreement and sub-processor list before you sign anything.

Frequently asked questions

Do I have to tell callers the agent is an AI?

Yes. Article 50 of the EU AI Act, applicable since 2 August 2026, requires people to know they're interacting with an AI system from the first interaction, unless it's obvious. With CallSmarter the notice is always given at the start and can't be switched off.

Who is the data controller: my business or CallSmarter?

Your business is the controller for your customers' data and calls. CallSmarter acts as processor and signs a data processing agreement with you under Article 28 GDPR.

How long are recordings kept?

90 days by default, then deleted or anonymised, and you can request earlier deletion. Other retention periods are yours to set as controller.

Is an AI voice agent for my business a high-risk AI system?

Generally, an agent that handles bookings, appointments or enquiries is not among the high-risk uses in Annex III of the AI Act. Systems that evaluate and classify emergency calls or triage emergency patients are. That's why our agents don't do emergency triage: if life may be at risk, they tell the caller to call 112.

Is this legal advice?

No. It's an information guide based on official sources. Every business should check its own case with its adviser or data protection officer.

Sources

  1. Regulation (EU) 2024/1689, the AI Act (DOUE, BOE)
  2. European Commission: transparency obligations under Article 50 of the AI Act
  3. AI Act, Annex III: high-risk AI systems
  4. Regulation (EU) 2016/679, General Data Protection Regulation (DOUE, BOE)
  5. Spanish Organic Law 3/2018 on data protection and digital rights, LOPDGDD (BOE)
  6. AEPD: GDPR compliance of processing that embeds artificial intelligence (guide, Spanish)
  7. AEPD: how are my data protection rights guaranteed when I receive a call?
  8. Spanish Law 10/2025 on customer service (BOE)