If you collect data about people in Europe, consent is not a box you tick out of caution: it is what makes the processing lawful, and it has to be provable. Eventleash gives you the tools to collect it and keep the evidence; the decisions about what to ask for stay yours, because you are the data controller.
How they work
A privacy consent is a checkbox that appears on your landing pages. You define it once at account level, then switch it on for the events that need it.
You configure them under Privacy consents, in the account section. The administrator role is required.
Creating a consent
Each consent has a name — which only you see, to recognise it in the list — and a description, which is the text a guest reads next to the checkbox.
Then there is the type:
| Type | When to use it |
|---|---|
| Internal (custom text) | You write the notice right here. Handy for short, event-specific consents |
| External (link) | You point at the notice you already publish on your website. The right choice when you have an official company notice |
The external form is usually preferable when your legal team has already approved a document: it stops two versions of the same text drifting apart over time.
Switching them on for an event
A consent you have defined appears nowhere until you enable it. You do that in the event, on its consents tab: pick which ones to show for that event.
That way the same account can ask different things depending on the occasion — a private dinner and a large open event rarely have the same needs.
What gets recorded
When a guest submits the form, each consent is stored as given or refused, with the time, and with the version of the text they were answering. That is the part that matters the day somebody asks for proof.
Which is why editing the text of a consent already in use does not rewrite the past: whoever answered earlier stays tied to what they read at the time.
Unsubscribing
Every email Eventleash sends carries an unsubscribe link. It is not optional and cannot be removed: it is a legal requirement and, at the same time, the main defence of your sending reputation. Somebody who cannot find the unsubscribe link clicks "report as spam" instead, and that one really does damage.
What happens when somebody unsubscribes:
- The contact stays in the address book, with the status updated.
- They stop receiving any communication from your whole account, not just from that event.
- They stay excluded from later campaigns even if you add them as a guest to a new event.
Anyone who changes their mind can resubscribe from the same page: the link keeps working and offers the opposite action.
Your role and ours
For the data of your contacts and guests, you are the data controller. Eventleash is the processor: it handles that data on your behalf and on your instructions.
The relationship is governed by the DPA, which you accept along with the terms of service, and which also lists the providers we use to deliver the service.
If a data subject asks you for access or erasure, you carry it out directly in the application: a contact's data is exported and deleted from the address book. If you need a hand, write to us.