Enterprise AI CallcenterOn-premises
EU AI Act and GDPR for an on-premises AI call centre
With the Enterprise AI Callcenter on your own servers, you are the deployer under the AI Act and the controller under the GDPR, and no external processor sits in the call path. The agent tells every caller that it is an AI at the start of the call, as Art. 50 requires since 2 August 2026. High-risk duties only arise if you use it for a purpose listed in Annex III.
- GDPR by design
- Runs on your own servers
- 24/7 operation and support
- A team of 5 in Sofia, EU
Already running in production at organisations in Bulgaria — names under NDA.
Your role and ours
| Topic | You (deployer, controller) | AI Fortis (provider) |
|---|---|---|
| Telling callers they talk to an AI | Keep the disclosure on in your scenarios | Builds the agent so that it informs callers (Art. 50(1)); on by default |
| Marking synthetic audio | No duty | Provider duty (Art. 50(2)) |
| Purpose of the calls | You decide; listed purposes make it high-risk | Documents what the system is built for |
| Call audio, recordings, transcripts | Processed on your own infrastructure | Access only as agreed for support |
| Information to callers (GDPR Art. 13) | Your notice at call start and your privacy text | Recording notice built into the greeting |
| Retention and deletion | Your policy | Retention settings and the audit log in the platform |
Sources: EU AI Act (Regulation (EU) 2024/1689), Art. 3(3); EU AI Act (Regulation (EU) 2024/1689), Art. 3(4); EU AI Act (Regulation (EU) 2024/1689), Art. 50(1); EU AI Act (Regulation (EU) 2024/1689), Art. 50(2); GDPR (Regulation (EU) 2016/679), Art. 13
AI disclosure since 2 August 2026
An AI system that interacts directly with people must be designed so that they are informed they are interacting with an AI, at the latest at the first interaction (Art. 50(1) and 50(5)). The Commission reads the exception for obvious cases narrowly, so a voice agent should say it is an AI, not leave the caller to guess.
In the Enterprise AI Callcenter, the greeting includes the AI disclosure and the recording notice, both on by default. You can adapt the wording per scenario and language.
Sources: EU AI Act (Regulation (EU) 2024/1689), Art. 50(1); EU AI Act (Regulation (EU) 2024/1689), Art. 50(5)
When a call centre use becomes high-risk
Answering questions, booking appointments, reminders and surveys are not listed in Annex III. Some uses are: deciding creditworthiness (point 5(b)), pricing life and health insurance (5(c)), classifying emergency calls (5(d)) and monitoring or evaluating the performance of workers (4(b)). For these, the deployer duties of Art. 26 apply from 2 December 2027, among them human oversight, keeping logs for at least six months and informing workers' representatives before use at the workplace.
Inferring the emotions of employees at work is prohibited outright, except for medical or safety reasons (Art. 5(1)(f)). Set up the call centre so that the AI serves callers and does not score your staff.
Sources: EU AI Act (Regulation (EU) 2024/1689), Annex III, point 5(b); EU AI Act (Regulation (EU) 2024/1689), Annex III, point 5(c); EU AI Act (Regulation (EU) 2024/1689), Annex III, point 5(d); EU AI Act (Regulation (EU) 2024/1689), Annex III, point 4(b); EU AI Act (Regulation (EU) 2024/1689), Art. 26(6); EU AI Act (Regulation (EU) 2024/1689), Art. 26(7); EU AI Act (Regulation (EU) 2024/1689), Art. 5(1)(f); Digital Omnibus on AI (Regulation (EU) 2026/1744)
GDPR on your own servers
- Legal basis per call type: contract for service calls, legal obligation where a law requires the call, legitimate interest only after a balancing test (Art. 6(1)).
- Caller information at the start of the call, with a link or number for the full notice (Art. 13).
- A data protection impact assessment before large-scale use of new technology (Art. 35).
- Security of processing: encryption, access control, restoring availability after an incident (Art. 32). The platform has role-based access, two-factor sign-in and an audit log.
- Health data in patient calls is a special category (Art. 9); a voice used to identify a person is biometric data (Art. 4(14)).
Sources: GDPR (Regulation (EU) 2016/679), Art. 6(1); GDPR (Regulation (EU) 2016/679), Art. 13; GDPR (Regulation (EU) 2016/679), Art. 35; GDPR (Regulation (EU) 2016/679), Art. 32; GDPR (Regulation (EU) 2016/679), Art. 9; GDPR (Regulation (EU) 2016/679), Art. 4(14)
Outbound campaigns
Marketing calls by an automated system without human intervention need the person's prior consent (ePrivacy Directive Art. 13(1)). Payment reminders and calls a customer asked for are a different case, but national rules on calling hours and recording still apply. The platform enforces your do-not-call list, calling hours and attempt limits on every campaign.
Sources: ePrivacy Directive (Directive 2002/58/EC), Art. 13(1); ePrivacy Directive (Directive 2002/58/EC), Art. 5(2)
Frequently asked questions
Is an on-premises AI call centre GDPR-compliant?
The GDPR applies to your processing wherever it runs. On-premises, call audio and recordings stay on your infrastructure and no external processor is in the call path, which makes the data flows simpler to document.
Does the AI agent have to say it is an AI?
Yes. Since 2 August 2026, callers must be informed at the latest at the first interaction (AI Act Art. 50(1) and 50(5)). Our agent says it at the start of every call.
Is our AI call centre a high-risk AI system?
Only if you use it for a purpose listed in Annex III, such as deciding creditworthiness or classifying emergency calls. For customer service, bookings and reminders it is not.
Do we need a DPIA for AI voice agents?
Usually yes when you use new technology at scale (GDPR Art. 35). The provider's documentation of the system helps you prepare it.
Can the AI make sales calls?
Only to people who gave prior consent: automated marketing calls need it in every Member State (ePrivacy Directive Art. 13(1)).
Ask about Enterprise AI Callcenter
Tell us which calls you want to automate and which rules your legal team worries about. We reply personally, usually within one business day.
- GDPR by design
- Runs on your own servers
- 24/7 operation and support
- A team of 5 in Sofia, EU
Already running in production at organisations in Bulgaria — names under NDA.
Pick a time for your call
Choose a slot that suits you. You get a confirmation with a video link.
30 minutesMon – Fri 09:00–17:00 (Eastern European Time)Google Meet
Open the calendar in a new tab →
Prefer not to pick a calendar slot? Tell us your preferred time instead.
Prefer the phone? Call +359 888 899 932. Or write to office@aifortis.com.