What your privacy notice must say when an AI answers the phone
If an AI assistant answers your calls, Article 13 GDPR requires you to inform your callers. Your privacy notice then needs the processing with purpose and legal basis, the provider as recipient, third-country transfers, retention periods and data subject rights. A provider's wording help is a starting point; have it checked, because informing callers is your duty as controller.
This article is orientation, not legal advice. Your privacy notice belongs in the hands of your data protection adviser.
Why the notice you already have is not enough
Your privacy notice describes what happens to personal data in your business. The AI assistant adds a new kind of processing that is not in there yet: a service provider answers calls, produces transcripts and summaries, and stores callback numbers. If you use the service as processing on your behalf, as with scoco, you remain the controller for calls to your number. Where data is collected from the callers themselves, Article 13 GDPR requires you to tell them, at the time of collection, among other things the purposes, the legal basis, the recipients, the retention period and their rights. So check whether an existing section on "contacting us by phone" already covers this: the service provider, the conversion into text, the retention periods.
At scoco this duty is also in the contract: under § 7(5) of the terms (AGB), you as the controller inform your callers, including about the use of artificial intelligence. In addition, the new activity belongs in your record of processing activities (Article 30 GDPR) if you have to keep one. By its wording, the exemption for businesses with fewer than 250 employees (Article 30(5)) does not apply where, among other things, the processing is not occasional; whether it applies to you is something to settle with your data protection adviser. A broadening of this exemption is being negotiated at EU level, but as of 15 November 2026 it has not been adopted.
Section 1: describe the processing
Article 12(1) GDPR requires clear and plain language. So the new section says plainly what happens: calls are answered by an AI assistant; this produces call transcripts, summaries and the details callers give (name, callback number and the request, for example); the purpose is dealing with the request and calling back. Describe honestly what really comes into existence: if no audio recordings are stored, write exactly that. At scoco there are no audio recordings, only text; if a call is in another language, the transcript is also translated.
The legal basis belongs with it (Article 13(1)(c)), and where you rely on legitimate interests, those interests too (point (d)). Which legal basis fits is for you to decide with your data protection adviser. scoco's wording help gives, as an example, Article 6(1)(b) GDPR for calls that concern a contract and point (f) otherwise, as a placeholder you fill in yourself. If your calls involve health data or professional secrets, Article 9 GDPR and § 203 StGB (professional secrecy) come into play as well; the wording help expressly does not cover that.
Section 2: name the recipients and the processor
Article 13(1)(e) GDPR requires the recipients or categories of recipients. According to the transparency guidelines of the European data protection authorities, these will generally be the named recipients; if you give only categories, describe them as specifically as possible. So name the assistant's provider, with its name and registered office, as your processor (Article 28 GDPR).
If the provider transfers data to a third country, Article 13(1)(f) requires that too, together with the adequacy decision or the safeguards the transfer relies on. At scoco the servers are in Germany (Falkenstein); speech recognition and the language model run in the EU; speech output can run through a US provider that receives only the assistant's reply texts (no caller audio). The public list at scoco.ai/en/subprocessors (in German) names every service provider with its location, processing region and transfer mechanism; you can quote from it or refer to it instead of guessing.
Section 3: retention periods and deletion
The notice has to state how long the data is stored or, where that is not possible, the criteria used to determine that period (Article 13(2)(a)). According to the transparency guidelines, a generic "as long as necessary" is not sufficient, and different periods should be stated separately. Copy across the periods your assistant is actually set to, not the ones you would like to have: set them first, then write them in. At scoco there are two periods, one for transcripts and one for calls with their summaries, both under Settings > Data & privacy (data retention in the help centre). Encrypted backups may still contain deleted data for up to six months; contacts stay until you delete them. Statements that contradict day-to-day practice inform no one.
Section 4: data subject rights and the complaints route
The notice has to name access, rectification, erasure, restriction, objection, data portability and the right to complain to a supervisory authority (Article 13(2)(b) and (d)). Those rights are probably in your notice already. Check that they also cover the new processing, and that the process behind them works: you have to tell the person what action you have taken on a request without undue delay and in any event within one month; that deadline can only be extended under the conditions of Article 12(3). Can your team find and delete a transcript on request? In scoco, the owner and admins can delete a single call from the inbox at once, with its transcript, summary and history.
The provider's wording help: a starting point, subject to review
Ask your provider whether it supplies wording help for your privacy notice. At scoco it is in the help centre under Informing callers: it states the facts about scoco (no call recordings, conversion into text, the reference to the list of service providers) and leaves placeholders for your phone numbers, your retention periods and everything only you can decide, such as the legal basis. It is non-binding and not legal advice; under § 7(5) of the terms, informing your callers remains your task.
That comes with a caveat: a general text does not know your business. It does not know which retention periods you have set, which legal basis fits your case, or what the rest of your notice already covers. If you use further features, such as text messages to callers, WhatsApp or a calendar connection, describe those too. So never adopt the template unchecked. It is raw material for your data protection adviser, not a finished product.
On the phone itself, the greeting says that an AI is speaking; Article 50(1) of the EU AI Act requires this of the provider of the system. At scoco you can reword this notice but not remove it. More on this in the article "Must the AI say it is an AI?".
Frequently asked questions
Isn't the announcement on the call enough information?
No. The disclosure that an AI is speaking is what Article 50(1) of the EU AI Act requires of the provider of the AI system; it does not contain everything Article 13 GDPR requires, such as recipients, retention period and rights. The transparency guidelines of the European data protection authorities (WP260 rev.01, para. 38) recommend a layered approach on the phone: the most important points during the call, namely who the controller is, the purposes, the existence of the rights and anything that could surprise the caller, and the rest by other means, for example the privacy notice. What you add to the greeting beyond the AI disclosure is something to settle with your data protection adviser.
Do I have to name the provider?
Article 13(1)(e) GDPR requires the recipients or categories of recipients. According to the transparency guidelines, naming the recipients will generally be the most meaningful information; if you give only categories, describe them as specifically as possible, with activity, industry and location. The level of detail is a decision for you and your data protection adviser.
What about cookies and tracking?
That is a separate topic: § 25 TDDDG governs when information may be stored on, or read from, a user's device, for example by cookies on your website. scoco's phone assistant embeds nothing on your website, so it changes nothing in the cookie sections of your website.
Do I also need a data protection impact assessment?
A DPIA (Article 35 GDPR) is mandatory where processing is likely to result in a high risk to the rights and freedoms of the people concerned. In their list under Article 35(4) (DSK, version 1.1 of 17 October 2018), the German supervisory authorities include, as no. 11, the use of artificial intelligence "to steer the interaction with the data subjects", with the typical use case "customer support by means of artificial intelligence". Whether your deployment falls under it is something to settle with your data protection adviser, all the more so with health data. scoco supports you under § 9 of its data processing agreement, which promises a template DPIA on request once it has been approved.
How quickly does the notice have to be updated?
Article 13(1) GDPR requires the information at the time the data is collected, so from the first call the assistant answers, including during the trial. The update therefore belongs in the setup, before you switch on call forwarding, not on the to-do-later list.
Status & sources
As of 2026-11-15.
- Not legal advice. Sources: GDPR (Regulation (EU) 2016/679) Art. 6, 9, 12, 13, 28, 30, 35 — unamended since entry into force (as of 15 November 2026; the amending proposals COM(2025) 501 and COM(2025) 837 have not been adopted)
- EU AI Act (Regulation (EU) 2024/1689) Art. 50(1), applicable since 2 August 2026 (Art. 113; not postponed for paragraph 1 by the Digital Omnibus, Regulation (EU) 2026/1744, OJ of 24 July 2026)
- § 25 TDDDG
- § 203 StGB (professional secrecy)
- 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 (Endorsement 1/2018); paras 36 and 38 and the annex on Art. 13(1)(e) and 13(2)(a)
- Datenschutzkonferenz (DSK, the German supervisory authorities): list of processing operations requiring a DPIA (Art. 35(4) GDPR, private sector), version 1.1 of 17 October 2018, no. 11 (German)
- Product details for scoco.ai: as of 15 November 2026 (help centre pages "Informing callers", "Data retention" and "Greeting"; AGB § 7(5) and AVV § 9, both as of 15 November 2026; sub-processor list)