GDPR and AI on the phone: what your business must sort out
When an AI answers the phone for your business it processes your callers' personal data. Under the GDPR your business is the controller; the provider processes on your behalf. Five points need settling: the data processing agreement, informing callers, checking the AI disclosure in the greeting (that duty falls on the provider), retention periods and the record of processing activities.
This article is orientation, not legal advice. For your specific situation the topic belongs with your data protection adviser.
Five points your business has to settle
1. Put a data processing agreement in place — Article 28 GDPR. The provider processes your callers' data on your behalf. Article 28(3) GDPR requires a contract with a set minimum content for that, and you may only use providers that give sufficient guarantees of appropriate technical and organisational measures (Article 28(1)). Read the agreement and its annexes before you sign, above all the technical and organisational measures and the list of sub-processors.
2. Inform your callers — Article 13 GDPR. Whoever collects data from the person concerned has to tell them, among other things, the purposes and legal basis, the recipients, any intended transfer to a third country and the storage period. For your callers that means: your privacy notice describes call answering by the AI service — what data it produces (transcripts, callback numbers, for instance), who processes it and how long it is kept. Wording supplied by the provider can make the start easier, but it does not replace your own review: the decisions, such as the legal basis, stay with you.
3. Check the AI disclosure in the greeting — Article 50 of the EU AI Act. Since 2 August 2026, AI systems that interact directly with people have to be designed so that those people are told they are talking to an AI, unless that is obvious from the circumstances (Article 50(1)). That duty falls on the provider of the system. For you it still means: check that the greeting contains the disclosure by default — and whether it can be switched off (it should not be possible to switch off). More on this in the article "Must the AI say it is an AI?".
4. Settle retention and deletion — Article 5(1)(e) and Article 17 GDPR. Transcripts and summaries may be kept only as long as the purpose requires. In practice that means defined retention periods, a deletion route that actually works (including when a caller asks for deletion) and ideally self-service in the dashboard.
5. Update your record of processing activities — Article 30 GDPR. Call answering by the AI service is a processing activity with its own purposes, data and recipients. The exemption for organisations with fewer than 250 employees (Article 30(5)) does not apply where, among other things, the processing is not occasional; the German Data Protection Conference gives the regular processing of customer data as an example. The conference publishes a template for controllers (in German). A relaxation of Article 30(5) has been proposed at EU level (procedure 2025/0130(COD)); as of 15 November 2026 the European Parliament has not yet voted on it, and it has not been adopted. The current text applies.
Recording or transcript — the underrated difference
The most delicate question in this category is not where the servers are. It is: what actually comes into existence during the call?
- Call recording (audio): the spoken word is stored as an audio file. In Germany, recording another person's non-public spoken words onto a sound carrier without authorisation is an offence under § 201(1) no. 1 of the Criminal Code (StGB), and under data protection law the German Data Protection Conference considers recording telephone calls permissible, as a rule, only with the caller's consent.
- Transcript: the audio is processed only during the call, for recognition; what is stored is text (transcript plus summary). This is the more data-frugal architecture: less sensitive material, a smaller attack surface, simpler deletion.
Ask every provider in these words: "Do you record calls as audio — yes or no?" At scoco.ai the answer is no: no call recordings are produced, only transcripts and summaries, and there is no switch for recordings. Which questions § 201 StGB leaves open for speech recognition is covered in the article "Recording or transcript?".
Server location, place of processing, sub-processors: three questions
"Servers in Germany" describes the hosting, not every service that processes call data. Three more precise questions tell you more:
- Where does processing happen? Ask where speech recognition, the language model and speech output run, and which data goes to each.
- Who is involved? Ask for the sub-processor list: every service provider involved, with its location, its role and the basis for any transfer to a third country. The provider may engage further processors only with your prior written authorisation; under a general authorisation it informs you of every intended change, and you can object (Article 28(2) GDPR). Service providers in the US are not automatically unlawful — but a transfer needs a basis under Articles 44 et seq. GDPR, such as an adequacy decision or standard contractual clauses, and your callers learn about it in your privacy notice (Article 13(1)(f)).
- Do the documents match? The processing agreement, the sub-processor list and what the provider's website says should name the same service providers. Where they differ, ask.
How scoco.ai answers these points
Servers in Germany (Hetzner, Falkenstein) · speech recognition and language model in the EU; speech output can run through a US provider that receives only the assistant's reply texts (no caller audio) · processing agreement and sub-processor list publicly available, the technical and organisational measures on request · no call recordings, only transcripts and summaries · retention periods you choose yourself (transcripts 7 to 90 days, calls and summaries 12 to 36 months), with automatic deletion every night · the AI disclosure is in every greeting: you can reword it, but not remove it · for your privacy notice, non-binding wording in the help centre under "Informing callers", expressly not legal advice; informing your callers remains your task · scoco.ai does not supply a template for your record of processing activities.
Frequently asked questions
Do I need consent from every caller?
Consent is one of several possible legal bases. Article 6(1)(b) GDPR may also apply, where the processing is necessary for a contract with the caller or for pre-contractual steps at the caller's request, and so may point (f), legitimate interests after a balancing test; callers can then object (Article 21). For the transcription of video conferences, the Bavarian data protection authority states that it is "not only possible with consent". Whether that carries over to your calls is a question for your data protection adviser; informing callers is needed in every case (Article 13). Where you process health data or other special categories of personal data (Article 9(1)), a basis under Article 6 alone is not enough; you also need an exception under Article 9(2). For audio recordings, the German Data Protection Conference requires consent as a rule.
What has to be in the greeting?
That an AI is speaking: Article 50(1) of the EU AI Act obliges the provider to design its system so that callers are told. For the information under Article 13 GDPR, the transparency guidelines endorsed by the European Data Protection Board recommend a layered approach on the phone: first, generally, the purpose, who the controller is, that data subject rights exist and anything that could surprise the caller (that the call is written down as text, for instance), the rest by other means such as a pointer to your privacy notice (WP260 rev.01, para 38). How much of that your greeting itself has to say is a question for your data protection adviser.
Is a provider with ISO 27001 automatically GDPR compliant?
No. ISO/IEC 27001 certifies an information security management system, not the lawfulness of any processing. Check the substance: the processing agreement, the technical and organisational measures, the sub-processor list, the deletion policy — with or without a certificate. scoco.ai holds no such certificate.
How long may transcripts be stored?
Only as long as the purpose requires (Article 5(1)(e) GDPR); the GDPR names no fixed number. In practice: defined periods per data type, then automatic deletion. Ask the provider whether the periods can be set and where they are documented.
Who is liable if the provider loses data?
Under Article 82 GDPR, data subjects can claim compensation from the controller or from the processor. The processor is liable only where it has breached its own GDPR obligations or acted against your instructions (Article 82(2)); where both are responsible, each is liable for the entire damage (Article 82(4)), and Article 82(5) governs recourse between them. Which is another reason to ask the provider about backups, encryption and how it notifies you of a breach (Article 33(2)).
Status & sources
As of 2026-11-15.
- Not legal advice. GDPR (Regulation (EU) 2016/679) Art. 5(1)(e), 6(1)(b) and (f), 9, 13, 17, 21, 28, 30, 33, 44 et seq., 82
- EU AI Act (Regulation (EU) 2024/1689) Art. 50(1), applicable since 2 August 2026 (Art. 113; paragraph 1 not postponed by the Digital Omnibus, Regulation (EU) 2026/1744)
- § 201 StGB (German Criminal Code, violation of the confidentiality of the spoken word)
- German Data Protection Conference (DSK): decision of 23 March 2018 on recording telephone calls (in German)
- Article 29 Working Party: Guidelines on transparency under Regulation 2016/679, WP260 rev.01 (last revised 11 April 2018, endorsed by the European Data Protection Board on 25 May 2018), para 38
- German Data Protection Conference (DSK): short paper no. 1 on the record of processing activities, Art. 30 GDPR, as of 17 December 2018 (in German)
- German Data Protection Conference (DSK): template for controllers under Art. 30(1) GDPR, as of February 2018 (in German)
- Bavarian State Office for Data Protection Supervision (BayLDA): 15th activity report 2025 (presented March 2026), section 13.1 on transcribing video conferences (in German)
- European Parliament, Legislative Observatory: procedure 2025/0130(COD) (Omnibus IV, proposal COM(2025) 501, proposing among other things an amendment of Art. 30(5) GDPR), as of 15 November 2026: the text agreed in interinstitutional negotiations approved in committee (2 July 2026), Parliament's first-reading position pending, plenary indicatively scheduled for 23 November 2026
- Product details for scoco.ai: as of 2026-11-15 (help centre "Data retention", "Informing callers", "Change the greeting"; DPA Annex 2)