Does my AI phone assistant need a data processing agreement?
Yes, if the provider processes your callers' data on your behalf: it is then a processor, and Article 28(3) GDPR requires a data processing agreement (DPA), in writing or in electronic form. Without one, according to the EDPB's guidelines, both sides infringe the GDPR. Article 28 makes no exception for small businesses.
This article is orientation, not legal advice. For your specific situation the topic belongs with your data protection adviser.
Why there is no exception
The moment the assistant answers a call, personal data arises: phone number, name, request, transcript. You are the controller for it. If the provider processes the data on your behalf, it is a processor (Article 4(8) GDPR), and for that constellation Article 28(3) GDPR requires a contract or other legal act that binds the provider to you: the data processing agreement (DPA). It has to be in writing, which includes electronic form (Article 28(9)). If it is missing, the European Data Protection Board (EDPB) treats that in its Guidelines 07/2020 as an infringement of the GDPR. Both sides are responsible for ensuring that a contract exists, and the supervisory authority can fine both (para. 103; Article 83(4)(a) GDPR). Article 28 contains no exception by business size: it applies to the one-person trade business just as it does to the corporation.
Whether a provider is only a processor depends on what it actually does. If, in breach of the GDPR, it determines the purposes and means of the processing itself, for instance by using your callers' data for model training of its own that you did not instruct, it is treated as a controller for that processing (Article 28(10)). That is one more reason to read the contract closely.
In practice the provider supplies a ready-made DPA, and you review and conclude it before real calls come in. That does not end your own check: under Article 28(1) you may only use providers that give sufficient guarantees of appropriate technical and organisational measures.
What Article 28 requires in the contract
Article 28(3) GDPR sets the minimum content:
- Subject matter and framework (first sentence): the subject matter and duration, nature and purpose of the processing, the type of data, the categories of data subjects, and your obligations and rights as the controller.
- Bound by instructions (point (a)): the provider processes only on your documented instructions, including for transfers to third countries. If it considers an instruction unlawful, it has to tell you immediately (Article 28(3), second subparagraph).
- Confidentiality (point (b)): whoever processes the data is committed to confidentiality or under a statutory obligation of confidentiality.
- Security (point (c)): the provider takes all measures required under Article 32 GDPR.
- Sub-processors (point (d) with paragraphs 2 and 4): further processors only with your prior specific or general written authorisation. Under a general authorisation the provider informs you of any intended addition or replacement, and you can object. Every sub-processor is bound by contract to the same data protection obligations, and the provider remains liable to you for it.
- Assistance (points (e) and (f)): with requests from data subjects, and with security, data breach notification and data protection impact assessments (Articles 32 to 36 GDPR).
- Deletion or return (point (g)): when the service ends, the provider deletes the data or returns it, at your choice, unless a legal obligation requires storage.
- Evidence and audits (point (h)): the provider makes available the information you need to demonstrate compliance and allows for audits, including inspections.
What the EDPB recommends beyond that
The EDPB's Guidelines 07/2020 describe what a contract should be measured against if it is to be more than a copy of the law:
- Specific, not copied out: the contract should describe how the requirements are met, not merely restate Article 28 (para. 112).
- Security measures you can assess: the contract should include or reference the measures, in enough detail for you to judge whether they are appropriate (para. 126). That can be an annex of technical and organisational measures, for example.
- Sub-processors with location and role: a list with each sub-processor's location, what it does and its safeguards (paras. 152 and 154), plus a timeframe for your objection and what happens when you object (para. 158).
- Data breaches with a notification route: the provider notifies you of a breach without undue delay (Article 33(2) GDPR); the contract can set a specific timeframe in hours and a point of contact (para. 136).
- Deletion with confirmation: the provider should confirm to you that the deletion has been completed (para. 141).
Where the DPA sits — and what scoco.ai discloses
The GDPR does not say whether a provider has to publish its DPA or may send it on request. What matters for your review is that you can read the full text with all its annexes before real calls come in; what you are not shown beforehand, you cannot review.
At scoco.ai, as of 15 November 2026:
- DPA: public at scoco.ai/de/avv (German only; the German version is binding), linked in the footer of every page of the website. It is concluded when the account is created, together with the terms, so in the trial too it is in place before the first call.
- Sub-processors: public at scoco.ai/de/subprozessoren (in German), with each one's role, seat or region of processing, the data processed and the transfer basis. scoco.ai announces changes by email to the stored administrator address at least 30 days in advance. You can object in text form within 14 days; the DPA requires an important data protection reason for it, which you have to state. If no remedy is found, you can terminate the affected service for cause, and so can scoco.ai if continuing without the new sub-processor is unreasonable for it (DPA § 6).
- Technical and organisational measures: a separate, versioned document (Annex 2). It is not public; you receive the current version by email on request.
- Data breaches: notification without undue delay, at the latest 48 hours after scoco.ai becomes aware (DPA § 8). The DPA does not specify a particular contact route for this notification.
- Data subject requests: in the dashboard you search calls, delete individual calls with their transcript and summary, retrieve transcripts and export the call list. A complete export of the data held on one person is produced by scoco.ai on your instruction; scoco.ai provides help beyond the self-service against reimbursement of reasonable effort (DPA § 7).
- End of contract: the data stays available for export for 30 days; the deletion is announced at least 14 days ahead, and proof of it is provided on request (DPA § 10).
- No training, no content for its own purposes: call content is not used by scoco.ai or by its sub-processors to train or fine-tune AI models, and scoco.ai does not use it for purposes of its own (DPA § 13(2)). Aggregated operating data without call content and without phone numbers, such as the number and length of calls or error rates, scoco.ai does process as a controller in its own right, among other things to develop the service, for 24 months at most (DPA § 13(6)).
If you are bound by professional secrecy under § 203 of the German Criminal Code (StGB), as a medical practice, a law firm or a tax adviser for example, a criminal law duty comes on top: under § 203(4), second sentence, point 1 StGB, anyone who has not ensured that a person assisting them was bound to secrecy is also liable if that person discloses a secret without authority. So ask your provider how it binds itself and its sub-processors to secrecy. Whether an AI phone assistant may be brought in as an assisting person in your profession, how further parties are to be bound, and which professional rules come on top, has not been conclusively settled — clarify it for your case with your professional chamber or your data protection adviser.
The first review checklist
- Do you have the full text, with every annex it refers to (technical and organisational measures, sub-processor list)?
- Does it cover every point in Article 28(3), and does it describe specifically how the provider meets each one?
- Does the sub-processor list give each one's location of processing, its role and, for third countries, the transfer basis (Articles 44 et seq. GDPR)?
- How do you learn of new sub-processors, how long do you have to object, and what follows from an objection?
- Is it ruled out that the provider uses call content for its own purposes, model training in particular? And what may it do with aggregated operating data?
- Is there a notification deadline and a point of contact for data breaches?
- Does the contract state the deletion periods during the term and the procedure at the end of the contract concretely?
- Does the DPA match the product? Does it describe the same types of data the product creates, such as transcripts but no audio recordings? If not: ask.
A complete, prompt answer to follow-up questions tells you more here than any marketing page.
Honestly: the DPA is necessary, but it is not a seal of quality
There are two things the DPA does not do. First, it does not make the processing lawful: the legal basis (Article 6, and for health data Article 9 GDPR as well), informing callers (Article 13), your privacy notice and, where Article 30 GDPR obliges you to keep one, your record of processing activities remain your jobs. For informing callers scoco.ai offers non-binding wording help in the help centre ("Informing callers"), explicitly not legal advice; the duty stays with you. Second, a signed DPA does not prove the provider abides by it. Article 28(3)(h) gives you rights to evidence and audits for that, and substance shows in whether the technical and organisational measures match the reality you can observe, and whether the provider answers awkward questions precisely.
Part of that reality at scoco.ai: servers in Germany (Hetzner, Falkenstein); speech recognition and the language model in the EU; speech output can run through a US provider that receives only the assistant's reply texts (no caller audio). Calls are not recorded; the DPA states that in standard operation call audio is processed only transiently in memory and not stored (§ 13(5)). What is stored is transcripts and summaries, with deletion periods you choose yourself (Data retention).
Frequently asked questions
Is it enough if the provider has "GDPR compliant" on its website?
No. A marketing line is not a contract. Article 28(3) GDPR requires a contract or other legal act with the content listed there, in writing or in electronic form (Article 28(9)). Whether it is any good, you judge by its contents, not by the slogan.
Who has to supply the DPA — me or the provider?
The GDPR does not say. According to the EDPB's Guidelines 07/2020, both sides are responsible for ensuring that a contract exists (para. 103). In practice the provider supplies its own, because it knows its processing and its sub-processors; you review it, or have it reviewed, and conclude it.
Does the DPA obligation apply during a free trial too?
Article 28 GDPR attaches to processing on someone's behalf, not to payment. As soon as real calls with real caller data come in, the provider is processing on your behalf, in a trial as well. So conclude the DPA before the first real call. At scoco.ai that happens when the account is created, together with the terms.
What is the difference between a data processing agreement and the technical and organisational measures?
The data processing agreement is the contract. The technical and organisational measures under Article 32 GDPR describe how the provider protects the data. Article 28(3)(c) requires the contract to bind the provider to those measures; the EDPB recommends describing them in the contract or referencing them, in enough detail for you to assess them (para. 126). At scoco.ai they are a separate document (Annex 2 of the DPA) that you receive by email on request.
My provider is based abroad — do I still need a DPA?
Yes, if it processes on your behalf: Article 28 attaches to the role, not to where the provider sits. If data goes to the provider or its sub-processors in a country outside the EEA, that transfer also needs a basis under Articles 44 et seq. GDPR, such as an adequacy decision of the European Commission or standard contractual clauses.
Status & sources
As of 2026-11-15.
- Not legal advice
- Regulation (EU) 2016/679 (GDPR): Article 4(8), Articles 6, 9, 13, Article 28(1)–(4), (9) and (10), Articles 30, 32, Article 33(2), Articles 44 et seq., Article 83(4)(a)
- European Data Protection Board (EDPB): Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.1, adopted 7 July 2021 (paras. 103, 112, 126, 136, 141, 152, 154, 158)
- § 203 StGB (professional secrecy; paragraph 3, second sentence, and paragraph 4, second sentence, point 1: assisting persons)
- scoco.ai: data processing agreement (German), as of 15 November 2026 (§§ 6, 7, 8, 10, § 13(2), (5) and (6), Annexes 2 and 3), and sub-processor list, as of 29 October 2026
- Product details for scoco.ai: as of 2026-11-15