§7a UWG de Alemania: cómo documentar el consentimiento para llamadas
Germany's §7a UWG makes callers document consumer consent to sales calls and keep proof five years after each use. What a consent record should hold.
Respuesta rápida
Section 7a of the German Unfair Competition Act (UWG) requires a business that advertises to a consumer by phone to document the consumer's prior express consent, which § 7 UWG already requires, in an appropriate form when it is given. The proof must be kept for five years from the consent and again after each use, and shown to the authority on request. The Bundesnetzagentur names fines of up to 50,000 euros for missing documentation.
German law already required prior express consent for advertising calls to consumers under § 7 UWG, as the Bundesnetzagentur page notes (Sources, item 2). What § 7a UWG added is a second duty: you must be able to prove it. The Bundesnetzagentur says the provision came with the Gesetz für faire Verbraucherverträge, which took effect on 1 October 2021 (Sources, item 2). For a calling team the practical question is not "do we have consent?" but "what would we hand over if the authority asked today?".
Nuestro Germany page covers the general consent rule and the German calling context. This post goes into the documentation duty and how to build a record that supports it inside a dialer. It is a practical summary and not legal advice.
What § 7a UWG requires
Paragraph 1 says that anyone who advertises to a consumer by telephone call must document the consumer's prior express consent to the telephone advertising in an appropriate form at the time it is given, and keep it as paragraph 2 sets out (Sources, item 1). The duty to have that consent at all comes from § 7 UWG. Three phrases do the work.
- Consentimiento expreso previo ("vorherige ausdrückliche Einwilligung"). The consent has to come before the call, and has to be express. Silence, a pre-ticked box or an assumption from a past purchase does not match the wording.
- In an appropriate form. The statute does not choose a format. A web form log, a signed paper form and a recording of an oral statement could all be formats; whether one is appropriate for your case is a question for counsel.
- At the time it is given. The record is made when consent is given. A record rebuilt later from a CRM note is weaker than one created in the moment.
Retention: five years, and again after each use
Paragraph 2 sets the retention rule. The advertising business must keep the proof for five years from when the consent was given and again after each use of the consent, and on request must show it without delay to the authority competent under § 20 paragraph 3 UWG (Sources, item 1). The Bundesnetzagentur page repeats the point: proof to be kept for five years from the grant and after each use, and presented without delay on request (Sources, item 2).
The "after each use" part changes how long a record lives. The illustrative timeline below shows why.
| Event (illustrative) | Date | Keep the proof until |
|---|---|---|
| Consent given on a web form | 15 March 2026 | 15 March 2031 |
| First sales call using that consent | 10 June 2026 | 10 June 2031 |
| Second call using that consent | 2 February 2028 | 2 February 2033 |
In this example the original consent has to stay available until February 2033, well past five years from the day it was collected. A dialer therefore needs to link each call attempt to the consent that justified it, and to run retention from the latest use, not from the collection date. A scheduled purge that deletes consents five years after creation would break the rule for any consent still being used.
What the Bundesnetzagentur expects
The Bundesnetzagentur publishes a page on proving telephone advertising consents. It says consents must be documented completely from the time they are given ("vollständig dokumentieren"), in an appropriate form, and that the records are to be presented to the agency without delay on request. It also lists the dates that matter: the final interpretation notes ("Auslegungshinweise") were published on 7 July 2022, after a consultation that closed on 30 November 2021 (Sources, item 2).
The page itself does not spell out the fields of a record. That detail is in the interpretation notes, a separate document that I could not read for this post, so I do not summarise it. Read the notes before you finalise your record design. The list in the next section is a design checklist built from the statute's words, and it is not a copy of the authority's list.
Multas
The Bundesnetzagentur page names two levels: up to 50,000 euros for a breach of the documentation duty, and up to 300,000 euros for telephone advertising without prior express consent (Sources, item 2). The fine provision is § 20 UWG. Paragraph 1 no. 1 covers advertising to a consumer by telephone call without prior express consent, and paragraph 1 no. 2 covers a consent under § 7a paragraph 1 that is not documented, or not documented correctly, completely or on time, or not kept, or not kept for at least five years. Both apply to intentional or negligent conduct. Paragraph 2 sets the maximums at 300,000 euros for no. 1 and 50,000 euros for no. 2, and paragraph 3 names the Bundesnetzagentur as the competent authority for both (Sources, item 3). The point for operations is that the two risks are separate: a call can be backed by a real consent and still carry a documentation problem if you cannot show it.
Recorded oral consent and call recording
Many teams collect consent by voice: the agent asks, the consumer says yes, and the call is recorded. Neither the statute nor the authority page we checked says this method is required or forbidden. If you use it, three things need thought:
- The recording is personal data. You need a lawful basis for recording, a notice at the start of the call and a retention period. The guía de cumplimiento para la grabación de llamadas y el GDPR guide for outbound call centres cover the data-protection side.
- Retention can clash. A recording that proves consent may have to be kept five years after the last use, while a general recording policy may delete it after a few months. Decide which recordings are evidence and exclude them from the shorter policy.
- Link, do not copy. Store the consent record with a pointer to the recording, so the proof can be found by consumer and not only by call id.
DialerBee grabación de llamadas supports per-campaign or global recording, and legal hold keeps chosen recordings from automatic deletion. Whether that suits your German evidence rules is a decision for you and your counsel.
Building the record
From the words of § 7a and the authority's page, a consent record that is easy to defend usually answers these questions. Treat it as a design checklist.
| Question the record answers | Campo |
|---|---|
| Who agreed, and to which number? | Consumer id, phone number |
| When, exactly? | Timestamp, created at the moment of consent |
| How? | Channel and act: web form, paper, recorded call |
| To what? | Campaign, product or advertiser the consent covers |
| Under what wording? | Notice text and version |
| Where is the evidence? | Link to form log, document or recording |
| Is it still valid? | Status history, including revocation |
| When was it used? | Every call attempt that relied on it |
| Was the rule bypassed? | Override audit: who, when, why |
The compliance page describes consent records that can be created, updated and revoked, with the history kept and revocation recorded as an event, plus overrides logged with an audit trail. Those map to the status history and override rows above. The consent management post and the glossary entry on gestión del consentimiento explain the workflow. The use log (which calls relied on which consent) is something to confirm in your own configuration, because it drives the "again after each use" retention.
Be clear about scope. DialerBee has calling-rule packs for the UAE, KSA, Jordan and Bahrain only, so German rules are configured by you. These are controles que respaldan el cumplimiento; they do not make a business compliant on their own.
Common gaps teams find
When a calling operation first reads § 7a against its own setup, the same gaps appear again and again. None of them needs new technology to fix, but each needs a decision.
- Consent held only as a flag. A "consent = yes" column tells you nothing about when, how or to what. If that column is all you have, you have a result and no proof. Add the date, the act, the wording version and the evidence link.
- Evidence kept by the lead supplier. If a partner collected the consent, the proof may sit on their systems. Agree in writing that you can obtain it, how fast, and that it stays available for the full period. A promise that "we have it" does not help if you cannot produce it on the day the authority asks.
- One consent, many campaigns. A consumer who agreed to calls about one product has not necessarily agreed to calls about another. Store the scope with the record and have the dialer compare the campaign with the scope before the attempt.
- Revocation handled in the wrong system. If a refusal is typed into a CRM note but never reaches the dialer, the next campaign calls again. Treat a withdrawal as an event that blocks dialling at once, and keep the event in the history.
- Retention by creation date. As the timeline above shows, a fixed purge by age can delete a consent that is still in use.
- Manual edits with no trail. A supervisor who fixes a record by hand should leave a trace of who changed what and why. An override without a name is hard to defend.
Fixing these in order of effort, scope and evidence links first, then the use log, then retention, gives most teams a record that can be exported on short notice.
A quick audit you can run this week
- Pick ten consumers you called last month. For each, can you produce the consent in under a day?
- Check that the consent predates the first call, by timestamp.
- Check that the wording named telephone advertising and your business or advertiser.
- Look at your deletion jobs: do any remove consent data on a fixed age without regard to last use?
- Ask purchased-lead suppliers for the consent evidence and for the right to keep it for the full period.
- Check that every manual override has a named user and a reason.
Preguntas frecuentes
What does § 7a UWG require?
Anyone who advertises to a consumer by telephone must document the consumer's prior express consent to that advertising in an appropriate form at the time it is given. The proof then has to be kept as paragraph 2 sets out, and shown to the competent authority on request. The rule that the consent is needed in the first place sits in § 7 UWG.
How long must the proof of consent be kept?
Five years. Paragraph 2 counts the five years from the date the consent was given and again after each use of the consent. A consent used for a call this year therefore needs to be kept for five years from that call, not only from the day it was collected.
What are the fines?
§ 20 UWG sets fines of up to 300,000 euros for telephone advertising to a consumer without prior express consent (paragraph 1 no. 1), and up to 50,000 euros for failing to document a consent correctly, completely and on time or to keep it for at least five years (paragraph 1 no. 2). The Bundesnetzagentur page names the same two amounts. Ask counsel how they apply to your case.
Does the law say how the record has to look?
The statute says consent must be documented in an appropriate form at the time it is given. The Bundesnetzagentur page we checked says the same and points to its interpretation notes for details, which we did not read for this post. Take the detail from the notes themselves, or from German counsel.
Is a recorded oral consent allowed?
Neither the statute nor the authority page we checked names or bans a method. A recording can be one way to hold proof, but a recording is also personal data and has its own legal basis questions. See our call recording guide, and confirm the approach with counsel.
Who can ask to see the proof?
Paragraph 2 says the proof must be shown without delay on request to the administrative authority competent under § 20 paragraph 3 UWG, and § 20 paragraph 3 names the Bundesnetzagentur. Its page confirms that it can ask for the records, so keep them in a form you can export quickly.
Fuentes
- § 7a UWG, Einwilligung in Telefonwerbung. gesetze-im-internet.de, Federal Ministry of Justice (consultado el 7 de noviembre de 2026)
- Bundesnetzagentur, Nachweis von Telefon-Werbeeinwilligungen. bundesnetzagentur.de, Einwilligungsdokumentation (consultado el 7 de noviembre de 2026)
- § 20 UWG, Bußgeldvorschriften. gesetze-im-internet.de, Federal Ministry of Justice (consultado el 7 de noviembre de 2026)
Lecturas relacionadas
- Germany calling rules
- GDPR for Outbound Call Centers
- Guía de cumplimiento para la grabación de llamadas
- Grabación de llamadas
- Controles de cumplimiento
- Gestión del consentimiento en flujos de trabajo salientes
- ¿Qué es la gestión del consentimiento?
Descargo de responsabilidad: This article is general information, not legal advice. DialerBee does not provide legal advice or guarantee regulatory compliance. It summarises § 7a and § 20 UWG and a Bundesnetzagentur page checked on November 7, 2026, and the law and the authority's views may change. Confirm current requirements with the Bundesnetzagentur and qualified German counsel.
Lecturas relacionadas: Caller ID Rules for Sales Calls to Germany · Is Call Recording Legal in Germany?
Artículos relacionados
Reglas de llamadas de los agentes de recuperación del RBI en India a partir de 2027
9 minutos de lectura
CumplimientoReglas de llamadas de cobranza de la CONDUSEF en México y el REDECO
Lectura de 10 minutos
Operaciones¿Cuántos canales SIP necesito? Dimensionamiento con Erlang B
Lectura de 10 minutos
TecnologíaHow to Measure Call Transcription Accuracy (WER)
Lectura de 11 minutos
¿Listo para ver DialerBee en acción?
Solicite una demostración en vivo de 15 minutos o comience una prueba gratuita de 14 días: sin presentaciones, sin compromiso. Las llamadas empiezan en cuanto su propia troncal SIP o PBX está conectada y aprobada.
Prueba gratuita de 14 días · crédito de IA gratuito · sin tarjeta · 11 idiomas · BYOC · controles que apoyan el cumplimiento