UK GDPRICOPECRDPA 2018AI ReceptionistCompliance

AI Receptionist UK GDPR & ICO Compliance Guide (2026)

JB
Justas ButkusFounder, AInora
··Updated ·14 min read

Yes, a UK business can use an AI voice agent for outbound calls, but PECR decides which calls. A marketing call made by an automated system needs the person's prior, specific consent; numbers are screened against the TPS and CTPS registers; the caller says who is calling and lets the person opt out. Service calls that market nothing, such as appointment reminders, sit outside the PECR marketing rules, while UK GDPR applies to every call. The full answer, with the regulation text, is in the first section below.

AInora, the publisher of this guide, runs AI voice agents that answer calls, book appointments on the call and call back new leads for UK and Irish businesses, so the team can serve more customers with the same staff. You can talk to an AInora agent in your browser, no sign-up, or book a walkthrough of how it is set up for UK GDPR, ICO and PECR obligations.

Post-Brexit UK Data Protection

Since Brexit, the UK operates its own data protection framework. The UK GDPR (retained EU law) runs parallel to the EU GDPR but is now an independent regulation enforced by the ICO. The EU has granted the UK an adequacy decision, enabling data flows between the UK and EU. However, the UK is diverging from EU rules in areas including AI regulation, creating a distinct compliance landscape that AI receptionist providers must navigate.

67M+
UK Population
5.5M+
UK Businesses
ICO
Data Protection Authority
GBP 17.5M
Max PECR Fine (or 4% of turnover)
Source: ICO, 5 Feb 2026

The UK operates its own independent data protection framework after Brexit, comprising the UK GDPR (retained EU law), the Data Protection Act 2018, and PECR. The Information Commissioner's Office (ICO) enforces these rules and can impose fines up to GBP 17.5 million or 4% of global turnover under UK GDPR. Since the Data (Use and Access) Act 2025, the same ceiling applies under PECR: the ICO can now fine up to GBP 17.5 million or 4% of global turnover for PECR breaches, where the old cap was GBP 500,000. For AI receptionists, the most critical distinction from EU GDPR is that the EU AI Act's mandatory disclosure requirement does not apply in the UK, though ICO transparency principles create an equivalent expectation in practice.

With over 5.5 million businesses and a service-heavy economy, the UK is one of the largest markets for AI voice technology in Europe. The post-Brexit framework creates a unique compliance environment that diverges from EU rules in areas including AI regulation, calling rules, and transfer mechanisms.

This guide covers what AI receptionist providers and businesses deploying AI voice systems in the UK need to know. The UK GDPR, the Data Protection Act 2018, PECR, ICO guidance, and the emerging UK AI regulatory framework all interact to create the compliance requirements described here.

For EU-focused GDPR compliance, see our comprehensive GDPR compliance guide. For our UK country landing page, see AI receptionist for UK businesses, and for how the vendors themselves line up against these rules, see the top AI receptionist platforms for the UK compared.

Yes, within the Privacy and Electronic Communications Regulations 2003 (PECR). Marketing calls made by an automated system are allowed only to people who have given prior, specific consent to those calls. Live marketing calls must not go to numbers registered with the TPS (individuals) or CTPS (companies), or to anyone who has told you not to call, unless that person has said they do not object to your calls. Every marketing call has to say who is calling and show a number the person can call back. Calls that promote nothing, such as an appointment reminder, fall outside the PECR marketing rules, but UK GDPR still applies to the personal data in every call.

What decides the answer is how PECR defines an automated call. Regulation 19 covers a system capable of "automatically initiating a sequence of calls to more than one destination" and of "transmitting sounds which are not live speech". The ICO's telephone marketing guidance describes an automated call as one made by an automated dialling system that plays a recorded message, says consent "must specifically cover automated calls", and does not mention AI or synthesised voices by name (checked 11 October 2026). An AI voice is not live speech, so the safe reading is to treat an AI marketing call as an automated call and get specific consent first. The ICO's enforcement points the same way: in September 2025 it fined two energy firms £550,000 for "automated marketing calls" in which agents abroad played lines recorded by voice actors through avatar software.

Outbound callWhat PECR saysWhat to do
AI marketing call to a consumerRegulation 19: only to a subscriber who has previously notified you that they consent to such callsCall only people who asked; make the consent cover an automated or AI call; keep the record
AI marketing call to a businessRegulation 19 applies to every subscriber, companies includedSame as above: consent first, then call
Live (human) marketing callRegulation 21: not to a number on the regulation 26 register (TPS, CTPS) or to someone who objected, unless they told you they do not objectScreen against TPS and CTPS; keep your own do-not-call list
Callback a lead asked forSolicited, but still marketing if it promotes your servicesTreat the request as the consent and say on the form that an AI assistant may call
Service call (appointment reminder, delivery update)Not direct marketing, so the PECR marketing rules do not applyUK GDPR transparency and a lawful basis still apply

Four practical rules follow from the regulations and the ICO guidance:

  • Screen every list against TPS and CTPS. The ICO advises screening against both registers for business calls too, because sole traders and some partnerships register with the TPS while companies register with the CTPS. A number listed for under 28 days is not yet a breach (regulation 21(3)).
  • Say who is calling, and say it is an AI. PECR requires the caller to identify itself and to display a contactable number. No UK statute requires the words "I am an AI", but the ICO's transparency and fairness principles under UK GDPR point the same way, and disclosure at the start of the call removes the doubt.
  • Make opting out easy and final. A subscriber can withdraw consent or an earlier "do not object" notice at any time, and after that "the caller shall not make such calls on that line" (regulation 21(5)). The ICO says automated marketing calls must stop when consent is withdrawn.
  • Fines are now at UK GDPR level. The ICO says the Data (Use and Access) Act 2025 gives it the power to fine up to GBP 17.5 million or 4% of global turnover under PECR (ICO, 23 June 2026). Its PECR guide still shows the old GBP 500,000 cap and notes that the guidance is under review.

How AInora Handles PECR on Outbound Calls

AInora is a voice AI platform whose agents answer a business's calls, book on the call and call back new leads, including for UK and Irish businesses. On outbound calls in the UK it works to these rules:

  • Consented callbacks only. AInora calls people who asked to be called, for example a lead who filled in a web form, sent an enquiry or asked for a callback.
  • No cold marketing calls to consumers.
  • Numbers screened against TPS and CTPS before a call goes out.
  • AI disclosure in the first sentence. The agent says it is an AI at the start of the call.
  • Opt-outs honoured. A person who asks not to be called again is not called again.

The business keeps its existing +44 number through call forwarding, the agent speaks British and Irish English and 90+ languages in all, and it switches language mid-call when the caller does. Data is stored on servers in Germany and Finland. In the standard setup, calls are processed in the EU and the US under GDPR (EU-US Data Privacy Framework, standard contractual clauses). A full-EU setup, with all processing in the EU, is available on request. The subprocessor list is in the DPA. See how the lead callback works for UK businesses on AI lead callback (UK), or the inbound side on AI receptionist UK.

What Is the UK Data Protection Framework After Brexit?

The UK's data protection framework after Brexit consists of three primary pieces of legislation:

  • UK GDPR: The EU GDPR was retained in UK law through the European Union (Withdrawal) Act 2018 and adapted for the UK context. It mirrors the EU GDPR in most substantive provisions but is now an independent UK regulation.
  • Data Protection Act 2018 (DPA 2018): The UK's primary data protection statute, which supplements and gives effect to the UK GDPR. It contains UK-specific provisions on law enforcement processing, intelligence services, and national security.
  • Privacy and Electronic Communications Regulations 2003 (PECR): The UK's implementation of the ePrivacy Directive, which governs electronic communications including telephone calls, automated calling systems, and marketing communications.

The Data Protection and Digital Information Bill named in earlier versions of this guide never became law. The Data (Use and Access) Act 2025 did: it received Royal Assent on 19 June 2025, and most of its remaining data protection provisions came into force on 5 February 2026. It amends UK GDPR, the DPA 2018 and PECR, including the PECR fine ceiling, and the ICO is reviewing its PECR guidance as a result.

How Does UK GDPR Differ From EU GDPR?

While the UK GDPR started as a copy of the EU GDPR, several differences have emerged since Brexit and more are expected.

AreaEU GDPRUK GDPR
Supervisory authorityNational DPAs per member stateICO (Information Commissioner's Office)
International transfersAdequacy decisions, SCCs, BCRsUK adequacy decisions, UK SCCs, UK BCRs
Representative requirementEU representative for non-EU controllersUK representative for non-UK controllers
AI regulationEU AI Act (binding)Pro-innovation framework (non-binding, evolving)
Cookie/consent rulesePrivacy Directive (strict)PECR (some relaxation proposed)
DPO requirementsMandatory for certain controllersSame in principle (check ICO guidance updated for the Data (Use and Access) Act 2025)
FinesUp to EUR 20M / 4% turnoverUp to GBP 17.5M / 4% turnover

What Does the ICO Require for AI Voice Systems?

The ICO has published guidance relevant to AI systems, including its guidance on AI and data protection, the Employment Practices Code, and various technology-specific guidance documents. For AI receptionists, the ICO's key expectations are:

Transparency

The ICO requires that individuals are informed about how their data is processed. For AI receptionists, this means callers should be told they are speaking with an AI system. While the EU AI Act's disclosure requirement does not apply in the UK, the ICO's transparency requirements under UK GDPR Articles 13 and 14 effectively create a similar obligation. If the caller would not reasonably expect to be speaking with an AI, failing to disclose this undermines the fairness principle.

Lawful Basis

For inbound AI receptionists handling business calls, legitimate interest under UK GDPR Article 6(1)(f) is the appropriate lawful basis. The ICO's three-part test for legitimate interest requires demonstrating: (1) a legitimate purpose, (2) that the processing is necessary for that purpose, and (3) that the individual's interests do not override the legitimate interest. Document this assessment using the ICO's LIA template.

Data Protection by Design

UK GDPR Article 25 requires data protection by design and by default. For AI receptionists, this means building privacy into the system from the start: collecting only necessary data, retaining data for the minimum period, restricting access to call recordings, and implementing technical security measures. The ICO has stated that data protection by design is not optional - it is a legal requirement.

DPIA Requirements

The ICO requires a Data Protection Impact Assessment for processing that is likely to result in high risk. AI voice systems processing personal data through telephone calls - especially at scale - are likely to meet this threshold. The ICO's screening checklist includes criteria such as "innovative technology" and "automated decision-making with significant effects," both of which apply to AI voice agents.

PECR Automated Calling Rules

PECR is the UK regulation that specifically governs automated calling, and it is where the UK's rules diverge most significantly from a simple "apply GDPR and you're done" approach.

Regulation 19: Automated Calling Systems

PECR Regulation 19 prohibits the use of "automated calling systems" for direct marketing purposes unless the called subscriber has notified the caller that they consent to such communications. Regulation 19(4) defines an automated calling system as one capable of automatically initiating a sequence of calls to more than one destination and of transmitting sounds which are not live speech. Consent must be specific, active (opt-in), and freely given. It cannot be implied by silence.

The critical question is whether an AI receptionist constitutes an "automated calling system" under PECR. For inbound AI receptionists that answer calls initiated by the customer, Regulation 19 does not apply - the customer initiated the call. For outbound AI calls (appointment reminders, follow-ups), the answer depends on whether the call constitutes "direct marketing." Non-marketing service calls (appointment confirmations, delivery updates) fall outside Regulation 19.

Regulation 21: B2B Calling

PECR Regulation 21 covers live marketing calls to businesses and consumers alike. An unsolicited B2B marketing call is permitted without prior consent only if the number has been screened against the Corporate Telephone Preference Service (CTPS) and is not registered there, and the business has not told the caller to stop calling. A registered number may be called only if the subscriber has told that caller it does not object to such calls. Calls made with an automated calling system fall under Regulation 19 instead, so automated B2B marketing calls need prior consent.

Inbound AI Receptionists and PECR

PECR's automated calling restrictions apply to outbound calls, not inbound call handling. An AI receptionist that answers calls initiated by customers or prospects does not trigger PECR Regulation 19 or 21. The PECR analysis becomes relevant only if the AI makes outbound calls for marketing purposes.

DPA 2018 Obligations for AI Receptionists

The Data Protection Act 2018 supplements the UK GDPR with provisions specific to the UK context. Several DPA 2018 sections are relevant to AI receptionists:

Section 14: Automated Decision-Making

DPA 2018 Section 14 provides safeguards for automated decision-making, mirroring GDPR Article 22. If the AI receptionist makes decisions that produce legal or similarly significant effects - such as deciding whether to schedule an appointment, prioritizing calls, or flagging callers - Section 14 safeguards apply. The individual has the right to obtain human intervention, express their point of view, and contest the decision.

Section 170: Unlawful Obtaining of Personal Data

DPA 2018 Section 170 creates a criminal offense for knowingly or recklessly obtaining, disclosing, or retaining personal data without the consent of the controller. This is relevant if AI voice recordings or transcripts are accessed by unauthorized individuals or disclosed improperly.

Section 171: Re-identification of De-identified Data

If AI voice data is anonymized or pseudonymized, DPA 2018 Section 171 makes it a criminal offense to re-identify the data without consent of the controller. This protects against re-identification of anonymized call data.

When Can You Record Calls Without Consent in the UK?

The UK has a more permissive approach to call recording than Germany, France, or Austria. Under the Regulation of Investigatory Powers Act 2000 (RIPA) and the Telecommunications (Lawful Business Practice) (Interception of Communications) Regulations 2000, a business can record calls without the consent of the other party for certain legitimate business purposes.

When Recording Without Consent Is Permitted

  • Evidence of business transactions: Recording calls to establish facts relevant to business transactions.
  • Regulatory compliance: Recording calls to ensure compliance with regulatory requirements.
  • Quality control and training: Recording for the purpose of quality control or staff training.
  • Crime prevention: Recording to prevent or detect crime.

When Consent Is Required

If the recording will be shared with third parties who are not part of the business (for example, shared with an AI provider for model training), two-party consent is generally required. Additionally, while RIPA permits recording without consent, UK GDPR transparency requirements mean the caller should be informed about recording. The ICO's position is that informing callers about recording is best practice and supports the fairness principle even when consent is not legally required.

Recommended Approach for AI Receptionists

Even though the UK permits single-party recording, the recommended approach for AI receptionists is to inform callers about recording at the start of the call. This satisfies UK GDPR transparency requirements, builds trust, and avoids disputes about whether recording was appropriate. If the caller objects, best practice is to continue without recording.

TPS and CTPS Compliance

The Telephone Preference Service (TPS) and Corporate Telephone Preference Service (CTPS) are the UK opt-out registers kept under PECR regulation 26. Ofcom kept that register until 30 December 2016; the duty has since moved to the information regulator.

  • TPS: Covers individual/consumer phone numbers. Businesses must not make unsolicited marketing calls to TPS-registered numbers unless the individual has specifically consented to calls from that business.
  • CTPS: Covers business phone numbers. Businesses must not make unsolicited marketing calls to CTPS-registered corporate numbers.

For inbound AI receptionists, TPS and CTPS do not apply - the caller is initiating contact. For live outbound marketing calls, numbers registered with the TPS or CTPS must not be called without the person's agreement, so call lists are screened first; for marketing calls that use an AI or other automated voice, prior specific consent is required under Regulation 19, and screening is a sensible extra check.

UK AI Regulation: Current and Upcoming

The UK has taken a different approach to AI regulation than the EU. Rather than enacting a comprehensive AI Act, the UK government published a "pro-innovation" AI regulation framework that delegates regulatory responsibility to existing sector-specific regulators.

Current Position

  • The EU AI Act does not apply in the UK. There is no legal requirement to disclose AI nature to callers under AI-specific legislation.
  • However, UK GDPR transparency requirements and the ICO's fairness principles effectively create a disclosure expectation for AI systems that interact with individuals.
  • Ofcom, as the communications regulator, may issue guidance specific to AI in telecommunications.
  • The Financial Conduct Authority (FCA) has issued AI guidance for financial services that may affect AI voice agents in that sector.

Expected Developments

The UK government has signaled that binding AI regulation may follow the initial pro-innovation phase. The Department for Science, Innovation and Technology (DSIT) is monitoring the effectiveness of the sector-specific approach. For AI voice agent providers, the prudent approach is to comply with EU AI Act disclosure requirements even in the UK - it costs nothing, builds trust, and positions the business for whatever UK regulation eventually requires.

Cross-Border Data Transfers: UK-EU

The EU has granted the UK an adequacy decision, meaning personal data can flow freely from the EU to the UK without additional safeguards. This adequacy decision was initially for four years (until June 2025) and has been extended. However, the decision can be revoked if the UK diverges too far from EU data protection standards.

For AI receptionist providers serving both UK and EU markets:

  • EU to UK transfers: Currently permitted under the adequacy decision. No additional transfer mechanism needed.
  • UK to EU transfers: The UK recognizes all EEA countries as adequate. Data flows from the UK to the EU are unrestricted.
  • UK to US transfers: The UK has its own UK-US Data Bridge (equivalent to the EU-US Data Privacy Framework). Transfers to certified US organizations are permitted.

The risk factor is adequacy revocation. If the UK diverges significantly from EU standards, for example through the reforms in the Data (Use and Access) Act 2025, the EU could revoke or modify the adequacy decision, which would require additional transfer mechanisms for UK-EU data flows.

GDPR-Compliant AI Voice Agent Suppliers in the UK and Ireland

A GDPR-compliant AI voice agent supplier for UK and Irish customer service calls is one that states where call data is stored and processed, signs a data processing agreement (DPA) that covers UK GDPR as well as EU GDPR, and lets the agent say it is an AI. The suppliers below appear when UK and Irish businesses ask for one. AInora is listed first because it publishes this guide; the others follow in alphabetical order. Every fact about another supplier comes from its own site, checked on 11 October 2026; "Not stated" means we did not find it there, not that the supplier cannot do it. Ask every supplier, including us, for the DPA and the subprocessor list before you sign.

SupplierBased inData location (as the supplier states it)UK GDPR / DPA statementPublished price (checked 11 Oct 2026)Live demo in the browser
AInoraSource: AInora securityVilnius, LithuaniaStored on servers in Germany and Finland; standard setup processes calls in the EU and the US (DPF, SCCs); full-EU setup on requestUK GDPR and EU GDPR; subprocessor list in the DPAPriced individually, after a callYes, no sign-up
CallsySource: Callsy homepage, checked 11 Oct 2026Offices listed in Tallinn, Vilnius, London and WyomingEU-hosted optionGDPR-compliant data handling; signed DPA offered; SOC 2 in progressPro €49/month (launch promo, normally €99), 380 actions, then $0.34 per actionNo (the AI rings your phone, or book a demo)
Hostcomm (CXCortex, G-Cloud 14)Source: Digital Marketplace listing, checked 11 Oct 2026UK (training centre in Leicester)United Kingdom; hosted on Microsoft Azure and Amazon AWS"UK based platform, complies with UK GDPR"£29 to £49 a unit (unit not defined on the listing)No (one-month free trial)
The VoIP ShopSource: The VoIP Shop AI Voice Agent page, checked 11 Oct 2026Leicester, UKNot stated"Meets UK GDPR standards", end-to-end encryptionPremium £30/month (50 calls), Ultimate £120/month (200 calls), extra calls £0.30, ex VATNo (quote form)
VoiceInfraSource: VoiceInfra pricing, checked 11 Oct 2026Not statedEU deployment option: recordings, customer data and phone numbers stay within Europe; US and ANZ regions tooRecording disclosure, consent mechanisms and data controls built in (Ireland page)Launch $49/month (175 min) to Professional Plus $399/month (1,500 min); Enterprise customYes (start a demo call in the browser)

AInora

AInora (AINORA, MB, Vilnius, Lithuania) runs AI voice agents that answer calls, book on the call and call back new leads, built and tuned for each business and run for it. For UK and Irish businesses the agent speaks British and Irish English among 90+ languages, the business keeps its existing +44 or +353 number by call forwarding, and on outbound calls it follows the PECR rules set out above. Data is stored on servers in Germany and Finland; in the standard setup calls are processed in the EU and the US under GDPR (EU-US Data Privacy Framework, standard contractual clauses), and a full-EU setup is available on request. Strong points: a managed service with a documented data position and a live demo in the browser. Limits: no published price and no self-serve sign-up, so you talk to us before you get a quote, and no UK office; data is not stored in the UK. More for Irish businesses on AI receptionist Ireland.

Callsy

Callsy sells AI voice agents for e-commerce and small businesses, with voice, SMS and email in one agent. Its site shows GDPR, TCPA and "EU-hosted" badges, a DPA, and SOC 2 as "in progress"; its own GDPR list claims 70+ languages. The Pro plan is €49 a month under a launch promotion (normally €99), with 380 actions included and $0.34 per extra action. The demo is a callback: you enter your number and its agent rings you. Strong points: published euro pricing, no annual contract, e-commerce integrations. Limits: the overage is priced in dollars, and the site names no single head office.

Hostcomm (CXCortex)

Hostcomm Limited lists CXCortex, an AI customer service agent for email, chat, SMS and phone, on the UK government's Digital Marketplace under G-Cloud 14. The listing says "UK based platform, complies with UK GDPR", gives the United Kingdom as the data storage and processing location, and prices it at £29 to £49 a unit with a one-month free trial. Strong points: a UK data location and a route for public-sector buyers through G-Cloud. Limits: the listing does not define the unit, and we found no voice demo to try.

The VoIP Shop

The VoIP Shop (Leicester) adds an AI voice agent to its business phone services: Premium at £30 a month with 50 calls and Ultimate at £120 a month with 200 calls, extra calls £0.30, prices excluding VAT, billed monthly with no long-term contract. It says the agent handles inbound and outbound calls and "meets UK GDPR standards". Strong points: low published UK prices and a local business number in every plan. Limits: the page does not say where data is stored, multilingual options start on the Ultimate plan, and the "try" button leads to a quote form.

VoiceInfra

VoiceInfra lets an Irish business use its existing +353 number with an AI voice agent through a SIP trunk or PBX extension. Its homepage offers an EU deployment in which recordings, customer data and phone numbers stay within Europe, its Ireland page lists built-in recording disclosure, consent mechanisms and data controls and claims 30+ languages, and its pricing runs from $49 a month (175 minutes) to $399 (1,500 minutes) with a free trial. You can start a demo call in the browser on the homepage. Strong points: an EU data option and a self-serve trial. Limits: prices in US dollars, and the site does not say where the company is based.

UK Compliance Implementation Checklist

1

Identify applicable UK regulations

Determine which regulations apply: UK GDPR for data processing, PECR for any outbound calling, DPA 2018 for automated decision-making. If serving financial services, check FCA requirements.

2

Complete a DPIA using ICO guidance

Use the ICO's DPIA template and screening checklist. Document the processing, risks, and mitigation measures. Publish the DPIA summary if appropriate.

3

Document your lawful basis

Complete a legitimate interest assessment for inbound call handling. Document it using the ICO's LIA template. Keep it available for ICO inspection.

4

Implement transparency measures

Inform callers they are speaking with an AI (even though not legally required by AI-specific legislation). Inform callers about recording. Provide access to the privacy notice.

5

Configure call recording compliance

While the UK permits single-party recording for business purposes, inform callers about recording as best practice. If recordings will be shared with third parties, obtain consent.

6

Screen against TPS/CTPS for outbound

If the AI makes any outbound calls, screen numbers against TPS (consumer) and CTPS (business) registers. Document screening compliance.

7

Establish data retention policies

Define retention periods for recordings, transcripts, and metadata. Implement automated deletion. The ICO expects retention to be limited to what is necessary.

8

Prepare for data subject rights

Build capability to handle UK GDPR data subject requests: access (provide recordings/transcripts), erasure (delete specific data), objection (stop processing), and portability (provide data in structured format).

9

Execute a UK-specific DPA

If using an EU-based AI provider, ensure the DPA covers UK GDPR requirements. The DPA should reference UK GDPR, not just EU GDPR, and specify the ICO as the relevant supervisory authority.

10

Monitor regulatory developments

Track ICO guidance updates for the Data (Use and Access) Act 2025, including the PECR guidance under review, and Ofcom communications. The UK regulatory landscape is evolving faster than the EU's post-AI Act environment.

Frequently Asked Questions

Yes, within PECR. Marketing calls made by an automated system, which an AI voice is safest treated as, need the person's prior, specific consent (Regulation 19). Live marketing calls must not go to numbers registered with the TPS or CTPS, or to people who objected, unless they said they do not object (Regulation 21). Every marketing call must say who is calling and show a contactable number. Service calls such as appointment reminders fall outside the PECR marketing rules, but UK GDPR applies to all calls. Since the Data (Use and Access) Act 2025, the ICO can fine up to GBP 17.5 million or 4% of global turnover under PECR.

AInora calls only people who asked to be called, such as a lead who requested a callback; it makes no cold marketing calls to consumers; numbers are screened against TPS and CTPS; the agent says it is an AI in its first sentence; and opt-outs are honoured.

Suppliers UK and Irish businesses come across include AInora (data stored in Germany and Finland, full-EU setup on request), Callsy (EU-hosted option), Hostcomm's CXCortex on G-Cloud (UK data location), The VoIP Shop (Leicester) and VoiceInfra (EU deployment option). Ask each for its DPA and subprocessor list, and check the data location in writing before you sign.

No. The EU AI Act does not apply in the UK after Brexit. The UK has adopted a pro-innovation approach to AI regulation that delegates to sector-specific regulators rather than enacting comprehensive AI legislation. However, UK GDPR transparency requirements effectively create an expectation to disclose AI nature to callers, and complying with EU AI Act disclosure is recommended as best practice.

PECR (Privacy and Electronic Communications Regulations 2003) governs electronic communications in the UK, including automated calling. For inbound AI receptionists that answer customer-initiated calls, PECR does not impose restrictions. PECR becomes relevant for outbound calls - automated marketing calls require prior specific consent under Regulation 19, and live marketing calls must not go to numbers registered with the TPS or CTPS unless the person has agreed (Regulation 21).

Yes, for certain business purposes. The Telecommunications (Lawful Business Practice) Regulations 2000 permit recording without consent for purposes including evidence of transactions, regulatory compliance, quality control, and crime prevention. However, UK GDPR transparency requires informing callers about recording. If recordings are shared with third parties, consent is generally needed.

The ICO (Information Commissioner's Office) is the UK's independent data protection authority. It enforces UK GDPR, DPA 2018, and PECR. The ICO can issue enforcement notices, conduct audits, impose fines up to GBP 17.5 million or 4% of turnover under UK GDPR and, since the Data (Use and Access) Act 2025, the same ceiling under PECR (the old PECR cap was GBP 500,000). The ICO also provides guidance and conducts investigations based on complaints.

Most organizations processing personal data must pay a data protection fee to the ICO unless exempt. The fee is based on organization size and turnover. If you are deploying an AI receptionist that processes caller personal data, you likely need to be registered with the ICO and have paid the current fee.

The EU has granted the UK an adequacy decision, allowing personal data to flow freely from the EU to the UK. The UK also recognizes all EEA countries as adequate. For AI voice providers operating across both markets, data can flow freely in both directions without additional safeguards, as long as the adequacy decision remains in effect.

TPS (Telephone Preference Service) is the UK's consumer do-not-call register. CTPS (Corporate Telephone Preference Service) is the equivalent for business numbers. Businesses must not make unsolicited marketing calls to registered numbers. These apply to outbound calls, not inbound AI reception. If the AI has any outbound calling capability, screen against both registers.

Yes. DPA 2018 Section 14 provides safeguards for automated decision-making, including the right to human intervention. If the AI makes decisions with significant effects on callers, these safeguards apply. Section 170 creates a criminal offense for unlawful data access, and Section 171 prohibits re-identification of anonymized data.

Likely yes. The ICO's screening checklist includes criteria such as innovative technology and automated decision-making that AI voice agents typically meet. A DPIA should be completed before deployment using the ICO's guidance and template. Even if not strictly required, the ICO recommends DPIAs for any processing that could pose risks to individuals.

Possibly. The UK government has stated that binding regulation may follow if the pro-innovation approach proves insufficient. The Data (Use and Access) Act 2025 has already changed data protection and PECR rules, and the ICO is updating its guidance. Ofcom may issue telecommunications-specific AI guidance. The safest approach is to comply with the highest standard now - EU AI Act disclosure plus UK GDPR transparency - so that future regulation does not require system changes.

JB
Justas Butkus

Founder & CEO, AInora

Building AI voice agents that let businesses serve more clients with the same team. The agents call back every new lead, re-contact past customers and take the calls the team cannot get to, and the work lands in the client's own CRM.

View all articles

Ready to try AI for your business?

Hear how AInora sounds handling a real business call. Try the live voice demo or book a consultation.