scoco.ai
Law & data protection

Recording or transcript? The legally decisive difference

Whether a call leaves an audio file or only text is a core question for any AI phone assistant. In Germany, unauthorised audio recording is an offence (§ 201 StGB), and Germany's data protection authorities accept it, as a rule, only with consent; a transcript is the more data-frugal design. Ask each provider: "Do you record calls as audio?"

This article is orientation, not legal advice. For your specific situation the topic belongs with your data protection adviser.

The difference in one minute

On every call with an AI assistant the spoken word is processed technically — without speech recognition there is no conversation. What matters is what is left afterwards:

  • Recording: the audio is stored as an audio file. Your caller's voice sits on a server and can be played back — with everything a voice carries.
  • Transcript: the audio is processed only during the call, for recognition, and is not stored. What is stored is text: transcript and summary.

Both are personal data, both need a legal basis, information for callers and retention periods. But the legal stakes are different: with an audio recording, German criminal law comes into play, and the German data protection authorities consider it permissible, as a rule, only with consent.

§ 201 StGB in plain terms: the confidentiality of the spoken word

§ 201(1) no. 1 of the German Criminal Code (StGB) punishes anyone who, without authorisation, records the non-publicly spoken word of another person onto an audio medium (a Tonträger). A call between a caller and a business is not addressed to the public. Anyone who records one without authorisation therefore risks not just a GDPR fine but criminal liability — from the moment of recording, regardless of whether anyone ever listens to it. Using such a recording or making it available to a third party is covered separately (§ 201(1) no. 2).

What makes a recording "authorised", the provision does not say. On the data protection side, the German Data Protection Conference (DSK), the body of Germany's federal and state supervisory authorities, has a clear line: in its decision of 23 March 2018 it holds that recording telephone calls is, as a rule, permissible only with the consent of the external party to the call as well. Asking before a recording is therefore not politeness but consent mechanics — a mere notice is not enough, as the next section shows.

For an AI assistant that stores only text, two questions are open. First: text is not an audio medium — but whether the brief technical processing of the audio during speech recognition can itself be "recording" within § 201(1) no. 1 has not been decided by any court. Second: § 201(2) no. 1 covers anyone who uses a listening device to eavesdrop on a spoken word not intended for their knowledge. The caller learns from the greeting that an AI is speaking; Article 50(1) of the EU AI Act requires that of the system's provider (more in the article "Must the AI say it is an AI?"). So the caller speaks to it knowing that. Whether that also means the technical service providers who process the audio for speech recognition are not "eavesdropping" has not been decided by any court either. Clarify both for your situation with your data protection adviser.

Why an audio recording needs elaborate machinery

Anyone who wants to record has to build the machinery properly — and operate it. The DSK decision names the building blocks: the caller is asked before the recording starts whether they agree, and confirms it unambiguously, for instance with a spoken "yes" or a key press. On that view, a mere notice with an option to object, followed by carrying on with the call, is not enough. The business must be able to demonstrate the consent (Article 7(1) GDPR), the caller can withdraw it at any time (Article 7(3)), and anyone who says no needs a way to get their request across anyway — otherwise it is questionable whether the consent was freely given (Article 4(11), Article 7(4)). For the business's own staff, the DSK notes, special requirements apply.

Then there is the material itself: audio carries voice, mood and background noise, and it is harder to search, redact and partially delete than text. Every stored hour of audio is more that can leak in a security incident.

All of that is doable, and service operations that record work this way. But it is ongoing effort, and it is your business, as the controller, that answers for the processing being lawful (Article 5(2), Article 24 GDPR).

Transcript: data minimisation as an architectural decision

The alternative is not to create an audio file in the first place: the audio serves only recognition during the call, and what is stored is text. The GDPR requires data to be limited to what is necessary for the purpose (Article 5(1)(c), "data minimisation"); anyone who stores an audio recording has to be able to justify what they need it for. For the transcription of video conferences, the Bavarian data protection authority (BayLDA) singled out live captions without permanent storage as the data-frugal form — and noted at the same time that transcription is itself processing that needs a legal basis, whether or not audio is stored as well (15th activity report 2025, section 13.1).

Text also makes your callers' rights easier to meet: a transcript can be searched, disclosed in extracts (Article 15 GDPR) and deleted in a targeted way (Article 17). What matters is that the architecture really delivers that. So also ask whether recording exists as an option that can be switched on, and who could activate it.

app.scoco.ai/inboxscoco.aiInbox4 neueMBNotfall0171 234 56 78 · K. Berger07:42 UhrNotfall erkannt — an die hinterlegte Nummer durchgestellt ✓Termin0621 89 76 54 · M. Schröder09:15 UhrTermin gebucht: Donnerstag, 14:30 Uhr — im Kalender bestätigtRückruf0152 998 87 76 · L. Yilmaz10:02 UhrRückruf erbeten — Nummer Ziffer für Ziffer bestätigtFrage06221 44 55 66 · R. Weber10:19 UhrÖffnungszeiten beantwortet — Antwort aus der Wissensbasis
Sample data. Every call becomes a structured entry in the team inbox — a transcript and a summary instead of a tape to play back.

Honestly: when a recording can be legitimate

There are cases in which businesses record deliberately or have to — to secure evidence when contracts are concluded over the phone, for quality assurance in a large service operation, or because a statute requires it, as § 83(3) of the German Securities Trading Act (WpHG) does for certain calls of investment firms. Anyone with requirements like that needs a sound basis for the recording, a legal obligation or consent, and should build the machinery with legal advice, not from templates. For the typical use of an AI phone assistant — take down the request, enable a callback, book an appointment — text is usually enough: the request, the name and the callback number are in the transcript and the summary. Both are machine-generated and can contain errors.

scoco.ai produces no call recordings, and there is no switch for them: what is stored is transcripts and summaries. You choose the periods yourself (transcripts 7 to 90 days, calls and summaries 12 to 36 months), deletion runs automatically every night, and encrypted backups expire after six months at the latest. The details are in the help centre under "Data retention".

Frequently asked questions

Is a transcript not a "recording" within the meaning of § 201 StGB?

§ 201(1) no. 1 StGB covers recording the non-publicly spoken word onto an audio medium without authorisation; text is not an audio medium. No court has decided how the brief technical processing of the audio during speech recognition is to be classified. The transcript remains personal data to which the GDPR applies (legal basis, information, deletion). Clarify your specific case with your data protection adviser.

Does the caller have to consent to the transcript?

Consent is one of several possible legal bases. Article 6(1)(b) GDPR may also apply, where the call concerns a contract or 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, and which basis holds, is a question for your data protection adviser. If calls contain health data, at a medical practice for instance, an exception under Article 9(2) GDPR is needed in addition. Informing callers is needed in every case (Article 13).

How can I tell whether a provider really does not record?

Ask in writing and in these words: "Do you record calls as audio — yes or no? Is there a recording function that can be switched on, and who could activate it?" Get the answer in writing, in the contract documents or the published product documentation, not only in an email.

May my business record calls for training purposes?

Only on a sound basis. According to the German Data Protection Conference, recording telephone calls is, as a rule, permissible only with the consent of the external party as well: obtained before recording starts, given unambiguously (a "yes" or a key press, for instance), demonstrable and revocable. Special requirements apply to your own staff; if you have a works council, check its co-determination right under § 87(1) no. 6 of the German Works Constitution Act (BetrVG). No business should introduce this without legal advice.

Further reading

From now on, someone
always picks up.

Call our demo business and hear for yourself what your reception sounds like.

We only use your address for your access. Privacy

4-week free trial. Or call the demo right now: +49 621 490799-22