AInora
EU and UK · General information, not legal advice

Webinar Registration Form Consent Checklist for the EU and UK

Webinar registrant consent is the separate, channel-named permission a person gives on the registration form, and it is what satisfies the prior-consent requirement in Article 13(1) of the ePrivacy Directive for that channel. It is one of four gates a call has to pass, and the only one a registration form can win. This page is the checklist for writing that form.

This page describes EU and UK law only, and it sets out the form wording, not the legal analysis. The statute-by-statute treatment of the other three gates - and the country-by-country picture - lives on is it legal to call webinar registrants in the EU and UK. It is general information, not legal advice. It is the form layer under our AI webinar attendance system, and the honest version of the offer is this: we run the follow-up your registration form authorised, and we tell you when your form does not authorise it yet.

Art. 13(1)
ePrivacy: automated marketing calls allowed only with prior consent
Source: Directive 2002/58/EC, Article 13
Art. 7(2)
GDPR: the consent request must be clearly distinguishable from the other matters
Source: GDPR, Article 7
Art. 4(11)
GDPR: consent must be specific - a purpose the form never named is not covered by it
Source: GDPR, Article 4
2 Aug 2026
EU AI Act Article 50 disclosure applies from this date
Source: Regulation (EU) 2024/1689, Article 113
Art. 7(2)
Its Own Box, Not The Terms
Art. 4(11)
One Channel, One Tick
11 items
The Form Checklist
Art. 7(1)
Logged So You Can Produce It

What Is Webinar Registrant Consent, and What Does the Form Have to Do?

Webinar registrant consent is the separate, channel-named permission a person gives on the registration form, and it is what satisfies the prior-consent requirement in Article 13(1) of the ePrivacy Directive for that channel. It is one of four gates a call has to pass, and the only one a registration form can win. It is not the registration itself, and it is not the fact that they typed a phone number into a field. The registration is the event sign-up. The consent is a distinct thing that either sits next to it on the form or does not exist.

That distinction is the whole page. It is also why the useful question is never "can we call webinar registrants?" but "what did the form ask them, and can we produce it?"

The caveat that governs everything below

Our compliance research covers twenty-seven EU states plus the UK, but it was built to answer a different question: whether cold outreach is lawful. It does not analyse the consented-registrant case anywhere. Everything on this page is therefore an application of the same statutes to a different set of facts, not a settled conclusion about that fact pattern. We have quoted the statutory text and linked the source in every case so you can check it. This is general information, not legal advice, and it is not a substitute for your own counsel signing off a campaign.

Where Does This Checklist Stop and the Legal Analysis Start?

Four independent rule sets sit between a registration and a call that connects: the ePrivacy Article 13 channel consent, the GDPR rules on lawful basis and purpose, national numbering and caller-identification law, and the EU AI Act Article 50 disclosure duty from 2 August 2026. A registration form can win the first and, if it names the purpose, the second. It has no effect on the third or the fourth. This page covers only what the form itself has to say; the four gates, the statutory wording behind each of them and the country-by-country picture for Lithuania, Germany, France, Spain, Poland, Italy and the UK are set out in full on is it legal to call webinar registrants in the EU and UK.

What Does a Webinar Registration Not Buy You?

Three things, and every vendor pitch that skips them is selling you a risk you did not price. This is the part of the conversation most likely to save you money, so it goes near the top rather than in a footnote.

Registration is not consent

Handing over a phone number in order to attend something is an act of signing up, not an act of agreeing to be marketed to. GDPR Article 4(11) defines consent as a freely given, specific, informed and unambiguous indication of the person's wishes. Article 7(2) requires that, where the request sits inside a wider declaration, it be presented in a manner "clearly distinguishable from the other matters". Article 7(1) puts the burden on the controller: you must be able to demonstrate the person consented.

The soft opt-in almost certainly does not reach it

ePrivacy Article 13(2) is written around a sale: it applies where a person obtains contact details from "its customers ... in the context of the sale of a product or service". A free webinar registration is not a sale. In Germany the exception in § 7(3) UWG is expressly limited to advertising "unter Verwendung elektronischer Post" - electronic mail - so it never reaches an automated calling machine at all. Poland has no soft opt-in to reach for: article 398 of the Prawo komunikacji elektronicznej (Dz.U. 2024 poz. 1221) prohibits automatic calling systems for direct marketing unless the subscriber or end user consented in advance, and contains no such exception.

Registration does nothing at the numbering layer

The rules that decide whether a call physically and lawfully lands are consent-agnostic. In France the trigger for ARCEP's caller-ID restrictions is automated mode, not the recipient's state of mind, and the derogation runs to verified polyvalent numbers you have to procure from a French operator. In Spain the 400 range is reserved as the origin of outbound commercial calls and enumerates no consent exception. In Germany § 120 TKG obliges providers to transmit a complete, genuine German number and to suppress the display where a foreign-originated call presents one. A perfect registration form changes none of it.

5 years
Germany: consumer consent to telephone advertising documented and the proof retained, § 7a UWG
Source: UWG § 7a
3 years
Germany: maximum prison term for recording non-public spoken word, § 201 StGB
Source: StGB § 201
400
Spain: the range reserved exclusively as the origin of outbound commercial calls
Source: BOE-A-2026-8409
Email only
Germany: the § 7(3) UWG exception is expressly limited to electronic mail
Source: UWG § 7

Which Gate Can a Registration Form Never Open?

The numbering one, and it is worth knowing before you spend a week on form wording. In France, ARCEP décision n° 2022-1583 of 1 September 2022 provides that certain territorialised numbers - geographic numbers, polyvalent numbers and ten-digit mobile numbers - may not be used as the caller identifier presented to the called party for calls issued by automated calling and message-sending systems (source). The decision grants a derogation to numéros polyvalents vérifiés - roots 0162, 0163, 0270, 0271, 0377, 0378, 0424, 0425, 0568, 0569, 0948, 0949 (09475-09479 in the DOM) - which is why running France means procuring a number from a French NPV operator. The trigger is automated mode, not consent.

In Germany, § 120 TKG obliges providers to transmit a complete, genuine German number and to suppress the display where a foreign-originated call presents one (source). In Spain, the Resolución of 14 April 2026 reserves the nine-digit NXY=400 range exclusively as the origin of outbound commercial calls and gives operators six months to make it operational, so around mid-October 2026; the duty to use it sits upstream in Ley 10/2025 and Orden TDF/149/2025, which we have not read in full - we assume it applies, because assuming otherwise is the expensive mistake (source). In Italy, AGCOM delibera 106/25/CONS requires operators to block calls arriving from abroad with a spoofed Italian caller identity, for fixed lines from 19 August 2025 and for mobile from 19 November 2025 (source).

What this means in practice

Owning a number is not the same as being allowed to present it. A call originated outside the destination country carrying that country's national caller ID is exactly the pattern these measures are written against, and none of them contains a consent exception. Where a market requires domestically originated or specially allocated numbering, that has to be solved with a local operator before a campaign starts - it is a procurement problem, not a compliance sentence. The full treatment of this layer, market by market, is on the EU and UK legality page.

Which Purposes Does Your Registration Form Have to Name?

All of the ones you intend to run, and the sales follow-up is the one most often missing. Confirming attendance, or reminding someone about a session they asked to join, serves the purpose they registered for. Working the attendee and no-show list afterwards to book a sales call is a different purpose, and the form is the only place it can be authorised in advance.

Consent has to be specific. Article 4(11) defines it as a specific indication of the person's wishes, and Article 5(1)(b) requires purposes to be specified and explicit at the point of collection (source). A consent given to receive webinar information is therefore not a consent to a sales follow-up call. Article 6(4)'s compatibility test is written about whether the further processing has its own consent or Member State law footing - and Recital 50 goes further, allowing further processing "irrespective of the compatibility of the purposes" where the data subject has consented (source). Which is exactly why the consent has to name the purpose in the first place: the escape route runs through the consent, and a consent that never mentioned the follow-up cannot carry it. If the form did not name it, you ask again.

The leg you want to runDoes the form have to name it?What that means for the wording
Confirm attendance, remind before the sessionIt is the purpose they registered forName it anyway. We run it on the registrant's consent rather than treating it as exempt, because whether a reminder is "direct marketing" is unresolved
Ask why they registeredYes - it is qualification and researchArticle 130(1) of the Italian Codice Privacy expressly covers automated calling for "il compimento di ricerche di mercato", so in Italy this sits inside the regime. Name it on the form, or do not ask it on the call
Call attendees and no-shows to book a sales callYes - this is a new purposeThe form has to say, before they submit it, that the follow-up may be about arranging a sales conversation. "We may contact you" does not name a purpose

Read together with the demonstrability duty in Article 7(1), there is only one design that holds up: the registration form names the follow-up purpose and the channels up front. That is not fine print we are hiding at the bottom of a contract. It is the first deliverable, and it is the reason we look at the form before we look at the list.

It is also, in several markets, the only route that exists. Where national law requires prior express consent for automated calls - Germany being the clearest case - a well-built registration form is not a nice-to-have. It is the single place that consent can realistically be captured, which is why we treat the form audit as the first piece of work rather than a disclaimer bolted onto the last one. If your post-webinar follow-up plan needs a consent your current form does not collect, we would rather tell you in week one.

Does the Form Have to Change per Market?

The checklist below is written to satisfy the strictest of the markets we cover, so the wording itself travels. What does not travel is the surrounding law: in Germany the consent is the only route there is (§ 7(2) UWG); in Poland the same is true and there is no soft opt-in at all (article 398 of the Prawo komunikacji elektronicznej); in Spain the consent rule sits in Ley 11/2022, article 66.1.a); in Italy an entry in the opposition register revokes telephone consents expressed earlier, so the consent date on your form is load-bearing; and in the UK the equivalent is regulation 19 of PECR. We apply the rules of the country we are calling into, and the market-by-market reading - including what we could and could not verify - is set out on is it legal to call webinar registrants in the EU and UK.

What About Recording the Calls?

Here we publish product behaviour rather than legal conclusions, and we want to be explicit about why. When we searched our own compliance research for substantive national treatment of call-recording consent, we found effectively none outside Germany. Rather than invent a position, we describe what the system does and leave the legal question where it belongs.

Recording is off by default. Where a client enables it, the agent announces it at the start of the call and consent is captured before recording begins; recordings are retained for a defined period and deleted afterwards. Retention periods are set per client and per market - outside Germany we will not publish a number we cannot ground.

Germany is the exception, and it is a criminal one

§ 201 StGB provides that whoever, without authority, records another person's non-publicly spoken word on a sound carrier is liable to imprisonment for up to three years or a fine (source). A sales call is non-publicly spoken word. There is no data-protection balancing argument that cures this, which is why calls in Germany are recorded only with the participants' agreement.

Where Does Our Knowledge Stop?

A compliance page that only lists what it knows is a sales page, so here is the short version for this one. Our research was built on cold outreach and never analyses the consented-registrant case; whether a confirmation or reminder call counts as "direct marketing" is unresolved and we do not build the offer on a service-message theory; and one national gap is still open - we could not retrieve the consolidated Lithuanian transposition text, so the Lithuanian national detail stays marked unconfirmed rather than papered over. The full list of open questions, with the position we take on each and why, is on is it legal to call webinar registrants in the EU and UK.

What Does Your Registration Form Actually Have to Say?

This is the artifact the rest of the page exists to produce. Take it to whoever owns your registration form. Every item maps to a provision quoted above, and the whole list is short enough to fix in an afternoon - which is the point, because fixing it afterwards is not an option that exists.

1

Ask for the phone number, and say on the form what it is for

The most common blocker we meet is not a legal one. Large webinar platforms collect a name and an email address and nothing else, so there is no number to call and no consent attached to it. If a phone leg is part of the plan, the field and its stated purpose belong on the registration form from day one.

2

Put the consent request in its own box, not inside the terms

GDPR Article 7(2): where consent is given inside a written declaration that also concerns other matters, the request must be presented in a manner clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language. In practice that is one labelled box of its own, in the same plain language as the rest of the form.

3

Leave it unticked, and do not make the webinar conditional on it

Article 4(11) requires consent to be freely given and unambiguous, and Article 7(4) requires utmost account to be taken of whether the performance of a service is made conditional on consent to processing that is not necessary for that service. Attending the webinar cannot be made to depend on agreeing to a sales call, and a pre-ticked box is not an unambiguous indication of anything.

4

Name the channels separately: phone call, SMS, email

Consent under Article 4(11) has to be specific. One tick that silently covers three channels is the claim most likely to fall over when someone asks what exactly the person agreed to. We collect and record consent per channel, and where a person consents to email but not to calls, the call leg does not run for that person.

5

Name who will be contacting them

The person should be able to read the form and know which organisation will be calling. Where the webinar host and the caller are different entities, the form has to say so. This is the same requirement that makes every message we send identify on whose behalf it is sent.

6

Name the purposes - including the sales follow-up, if that is the plan

GDPR Article 5(1)(b) requires personal data to be collected for specified, explicit and legitimate purposes. Confirming attendance is the purpose the person registered for. Calling a no-show to book a sales call is a different purpose, and consent has to be specific under Article 4(11): a consent that never mentioned the follow-up cannot carry it. If the form does not name it, add it before the campaign, not after.

7

Say that the call may be placed by an AI assistant

From 2 August 2026, Article 50 of Regulation (EU) 2024/1689 requires that people be informed they are interacting with an AI system, and Article 50(5) requires the information to reach them at the latest at the time of the first interaction. Our agents state it at the top of the first turn, in the language of the call, on every call. Saying it on the form as well costs nothing and removes the surprise.

8

Log the consent so you can produce it later

Article 7(1) puts the burden of demonstrating consent on the controller. That means keeping what was on screen, which boxes existed, which were ticked, and when. In Germany, § 7a UWG requires consent to telephone advertising given by a consumer to be documented in an appropriate form and the proof retained for five years from the giving of consent and after each use of it; we apply the same documentation standard more widely as our own policy rather than because it governs every case.

9

Check that your platform can actually store and export what you captured

A consent you cannot produce is a consent you do not have. Before anything dials, confirm that the registration platform records the wording that was shown, the state of each box, the timestamp and the channel, and that it exports them alongside the registration row. This is the item that fails most often in practice, and it fails silently.

10

Make withdrawal as easy as the tick, and make it work across every channel

Article 7(3): it shall be as easy to withdraw consent as to give it. Article 21(3) is absolute - where the person objects to processing for direct marketing purposes, the personal data shall no longer be processed for those purposes, with no balancing test. Article 21(4) requires that right to be brought to their attention explicitly, at the latest at the first communication. An objection given on the phone has to stop the SMS and the email too, which is why we run one shared suppression list across all three.

11

Re-read the form against every market you will call into

A form is drafted once and used everywhere, which is where it breaks. In Italy an entry in the opposition register revokes telephone consents expressed earlier, so the consent date is load-bearing; in Germany the consent is the only route there is. We apply the rules of the country we are calling into, and the country-by-country reading sits on our EU and UK legality page rather than here.

What we do with it

We read your registration form before we touch your list, and we tell you what it authorises: which channels, which purposes, and whether the sales-follow-up leg is covered or needs a form change first. Then we run only the follow-up the form supports. As your processor under a GDPR Article 28 agreement, acting on your documented instructions, that is also the only follow-up we are permitted to run.

What Do We Commit To on Every Campaign?

These are statements about what the system does, with the provision each one answers to. They are not statements about what the law permits in your particular case - that remains yours and your counsel's to settle.

  • We contact only people who registered themselves and who, on the registration form, clearly agreed to be contacted by phone, SMS or email - and we hold the record of that agreement.
  • Every call, SMS and email identifies on whose behalf the contact is made and carries a working way to opt out.
  • From 2 August 2026, in line with Article 50 of Regulation (EU) 2024/1689, we state at the start of the conversation that the caller is an AI assistant - and we do it before that date too.
  • When someone asks not to be contacted again, the number goes onto a suppression list across every channel immediately and is not used for marketing again (GDPR Article 21(3)).
  • We call from a genuine, non-suppressed, non-manipulated number, and where a market requires specific numbering we solve that with a local operator rather than working around it.
  • We consult the advertising exclusion systems in the markets that operate them, including the Lista Robinson in Spain and the opposition register in Italy, and we honour exclusions.
  • On personal data we act as your processor under a GDPR Article 28 data processing agreement, only on your documented instructions, with sub-processors disclosed. You remain the controller and you own the form wording and the privacy notice.
  • Recording is off by default; where it is enabled the agent announces it and consent is captured before recording begins. In Germany, calls are recorded only with the participants' agreement.

Frequently Asked Questions

Six things, and all of them are wording rather than technology: a phone field with its purpose stated on the form, a consent request presented separately from the registration itself (GDPR Article 7(2)), the channels named one by one because consent has to be specific (Article 4(11)), the organisation that will be doing the calling, the purposes including any sales follow-up, and a stored record of all of it that you can produce later (Article 7(1)). The full checklist, with the provision each item answers to, is on this page. This is general information and not legal advice.
It has to be clearly distinguishable within it. GDPR Article 7(2) provides that where consent is given in the context of a written declaration which also concerns other matters, the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language. In practice that means its own labelled, unticked box on the registration form - not a line inside the terms, and not a pre-ticked default.
We do not run on one. Consent under GDPR Article 4(11) has to be specific, and a single tick that silently covers three channels is the claim most likely to fall over when someone asks what exactly the person agreed to. We collect and record consent per channel, and where a person consents to email but not to calls, the call leg does not run for that person. It also makes the record easier to produce, because each channel has its own answer.
Name it. Consent has to be specific under GDPR Article 4(11), and Article 5(1)(b) requires purposes to be specified and explicit at the point of collection, so a consent given to receive webinar information is not a consent to a sales follow-up call. Recital 50 allows further processing "irrespective of the compatibility of the purposes" where the data subject has consented - which is exactly why the consent has to name the purpose in the first place. A consent that never mentioned the follow-up cannot carry it, and the fix is a form change before the campaign rather than an argument afterwards.
We ask for it. From 2 August 2026, Article 50 of Regulation (EU) 2024/1689 requires people to be informed they are interacting with an AI system, and Article 50(5) requires that information at the latest at the time of the first interaction - and our agents state it at the top of the first turn on every call regardless. Putting it on the form as well costs nothing, removes the surprise, and in the markets where the consent has to name what it authorises it is plainly the safer wording.
For as long as you rely on it, and in Germany there is a number: § 7a UWG requires consent to telephone advertising given by a consumer to be documented in an appropriate form and the documentation retained for five years from the giving of consent and after each use of it, and produced to the authority on request. Outside Germany our compliance research grounds no specific retention period and we will not invent one. What has to survive is the whole picture - the wording shown on screen, which boxes existed, which were ticked, and when.
Then there is no phone leg yet, and that is a form problem rather than a legal one. It is also the single most common blocker we meet: large webinar platforms collect a name and an email and nothing else, so there is no number to call and no consent attached to one. If a phone leg is part of the plan, the field, its stated purpose and the per-channel consent have to be on the registration form from day one - and the platform has to be able to store and export that record alongside the registration.
You do, and it matters. Your registrants, your registration form, your privacy notice, your lawful basis: you are the controller. AInora acts as your processor - GDPR Article 28(3) requires processing by a processor to be governed by a contract and requires the processor to process personal data only on documented instructions from the controller, and that is how we operate, with sub-processors disclosed. That division is also the commercial protection on both sides: the answer to "what did the form actually say" lives with the party that wrote the form, and our job is to run only the follow-up that form authorised.
JB
Justas Butkus

Founder & CEO, AInora

Building AI digital administrators that replace front-desk overhead for service businesses across Europe. Previously built voice AI systems for dental clinics, hotels, and restaurants.

View all articles

Send Us Your Registration Form First

Before any list, any script and any call. We will tell you what your form authorises - which channels, which purposes, which markets - and what would have to change before the follow-up you want is the follow-up you are allowed to run. If the answer is that your form is not there yet, you will hear it from us on the first call rather than from someone else later.