Privacy, consents and unsubscribes

Updated on 2026-10-22

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

The landing subscribe form asks two things, with standard wording managed by Eventleash and tied to your default privacy policy: the acknowledgement of the policy, required, and the consent to invitations and to open and click measurement, optional. You do not write or pick them: see The checkboxes on forms. The privacy notice is always there; the second checkbox can be removed from a single landing, in its form fields.

If you need to ask anything else — for example consent to share data with a partner or to be photographed — add additional consents, required or not: the account ones appear on every landing, those of an event only on its landings. On each landing you can switch off the optional ones you do not need.

The default privacy policy and the account's additional consents are configured under Privacy consents, in the account section: the administrator role is required. Those of an event, on the event's consents tab.

Creating an additional consent

Each additional 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:

TypeWhen 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

Description, link and notice text are written in every active language, switching language with the IT/EN button inside the fields: the landing page shows them in the event language and falls back to the main one where a translation is missing.

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.

Finally, choose whether it is required: if so, whoever does not tick it cannot sign up.

Account and event consents

The additional consents created under Privacy consents appear on every landing of the account. Those needed by a single event are created in the event, on its consents tab: they appear only on its landings.

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. The privacy notice and the required consents are always there anyway, on all of them; the invitations checkbox and the optional consents are switched off landing by landing, in the form fields.

What gets recorded

When a guest submits the landing form, their answers to the event's privacy consents are saved on the guest, consent by consent. The choices about the person in general — having read the privacy notice, invitations, measurement — are kept on the contact instead, each with its status and the dates it was last accepted and last refused: see The contact's choices.

For the event's consents only the yes or no is kept, not the text the person had in front of them. Which is why you should not edit the text of a consent already in use: if you need to change it, create a new one, so that whoever answered earlier stays tied to what they read at the time.

Open and click measurement

Knowing whether an email was opened and whether somebody clicked a link takes two things inside the message: an invisible image, which loads when the email is opened, and rewritten links, which record the click before taking the reader on. People who consented to the measurement, including contacts who were already receiving your emails with measurement before 1 April 2026 (see below) until they opt out, are measured individually: for each recipient you see whether they opened and whether they clicked.

Consent comes from the checkbox on the landing form or on the invitation answer page, or from the email preferences page: see The checkboxes on forms. Eventleash looks at the person's consent when the email leaves and again when it is opened or clicked.

People who did not consent

For everybody else you decide, following the rules that apply to your organisation, in the Measurement of opens and clicks section of the Privacy page of the account settings:

ModeWhat email they receiveWhat you see
Not measuredWithout the invisible image and with the links as you wrote themNothing: their opens and clicks are not recorded
AnonymousWithout the individual invisible image: an image and links identical for every recipient of the campaign, leading to the same pagesOnly how many times the campaign was opened and clicked, not by whom
Individual for everyoneThe same email as people who consentedFor each recipient, whether they opened and whether they clicked, regardless of the consents

When you create the account the mode starts from the billing country: not measured in the European Union, the European Economic Area, the United Kingdom, Switzerland and California, where the rules on tracking pixels are those of the GDPR or similar; anonymous elsewhere. You can change it whenever you like. Individual measurement for everyone is turned on only by confirming the declaration in which you take responsibility for operating under a legal regime that allows it; in this mode the preferences page and the forms no longer ask about the measurement.

With anonymous measurement the image and the links are the same for every recipient of the campaign: an open or a click only increases the campaign counters and there is no way to know who it was. The link goes through Eventleash only to take the person to the right page, even when it is personal like the invitation reply link, without keeping it. That is why opens and clicks are counted, not people: someone opening three times counts three. While the Privacy page shows the anonymous count as not active yet, people who did not consent are not measured in this mode.

In the campaign statistics, opens and clicks add individual and anonymous measurement together: see Sending statistics.

All this applies to Eventleash's own measurement. Invisible images from other services that you put in the body of an email (third-party tracking pixels) measure opens on their own, regardless of consents: the editor points them out before saving. See Third-party tracking pixels.

Legacy contacts without the proof of email (see below) also lost, with the November 2026 update, the individual opens and clicks recorded in the past, which are no longer counted in the campaign statistics. Individual measurement for everyone is the exception. Individual opens and clicks are kept for 24 months from sending, then deleted.

The contacts you already had

For contacts who had already received at least one email from Eventleash before 1 April 2026, the measurement is processing already in progress: it stays individual, unless they opt out, if they receive your invitations. What counts is the proof of the email, not just being in the address book: someone who was in it before that date but never received an email from Eventleash is not measured individually until they consent, and their consents box shows the source "Legacy contact". They must be informed with a dedicated email about tracking pixels, from which they can opt out at any time on the preferences page while still receiving the emails. Whoever opens the preferences page from that email and leaves the measurement on confirms it: in the consents box the source becomes "Confirmed from the email about open tracking".

Everybody else is measured individually only if they give consent; otherwise as your account's mode says.

Your default privacy policy

Under Privacy consents, in the account section, you set the account's default privacy policy, in one of the two forms of the consents:

FormWhat you enter
External (link)The address of the page on your website holding your policy
Internal (custom text)The text of the policy, written there. Eventleash publishes it on a page of its own, whose address appears below the editor once saved

The default policy does several things:

  • it lets you publish landings with the subscribe form: the form ties it to the first of the two default checkboxes, so without it a landing with the form cannot be published. Landings already published stay online;
  • it makes the two default checkboxes appear on the forms;
  • it is linked on the forms, on the invitation answer page, on the email preferences page and at the bottom of your emails.

The link and the text are written in every active language, switching with the IT/EN button as in the additional consents: emails, landings and public pages use the language of the contact or of the event and, where a translation is missing, the main one.

If before October 2026 you used a required account consent to point to your privacy policy, Eventleash turned it into the default policy, translations included: you no longer find it among the additional consents, because the two default checkboxes take its place, and whoever had accepted it shows as having received the policy.

Every change you save to the default policy, whether to the link, the text or switching from one to the other, creates a new version, numbered and dated at the moment of saving: the date cannot be chosen or changed. The version in force, with the date it applies from, is shown next to the title of the policy in Privacy consents and at the bottom of the public page of the text, and the earlier versions stay available, with the period they were in force. When a person accepts the policy or changes a choice, Eventleash also records the version in force at that moment, which you see in the Consents box of the contact. Consents that come from an import show no version: they were collected outside Eventleash, on a text we cannot know.

The content of the privacy policy is yours, as the data controller: Eventleash neither prepares nor checks it. Have your adviser review it, including the part on the open and click measurement described above.

Unsubscribing and email preferences

Unsubscribing 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 a way out clicks "report as spam" instead, and that one really does damage.

The links at the bottom of your emails open the recipient's email preferences page. It is personal, needs no login, and its address does not contain the person's email. It is the same whichever email it is opened from, for whichever event: the choices belong to the person, not to one invitation. It offers two independent choices, with buttons of equal weight, and the privacy notice at the bottom:

ChoiceWhat it changes
Invitations to new eventsKeep receiving your account's invitations and other campaigns, or stop. It applies to the whole account. Whoever stops receives no campaign, not even of the events they signed up for: only the confirmations and denials of their registrations
Open and click measurementAllow individual measurement, or Count my opens only anonymously, or Do not measure my opens when your account is in the not measured mode. Not shown when your account measures everyone individually.
Your dataThe personal data your account holds about the person: personal details, contacts, address, company, socials, custom fields. Category, type, groups and notes, your internal organisation, do not show. A line says that, on request, your account also tells the person the emails it sent them and, if they agreed to measurement, the opens and clicks recorded
Privacy notice and your dataShows which version of your privacy notice the person accepted and when, the version in force if you have published a newer one since, and the link to the notice in force. The Withdraw and delete all my data button, after a second confirmation, exercises the right to erasure

The right to erasure deletes everything your account holds about that person: the contact, their registrations to every event and the history of the emails received disappear at once from the application (lists, counts, exports, sends), the messages still queued are not sent, and after 30 days the data is erased for good. The companions they named stay, being other people. The anonymous campaign totals do not change. It cannot be undone from the application: if the person signs up again, they start from scratch.

Individual measurement goes hand in hand with the invitations: whoever stops receiving them (from the page, from the mail client's button or with a spam complaint) also leaves individual measurement, and the measurement section disappears from the page. Whoever starts receiving the invitations again from the page turns individual measurement back on too, and can then opt out of it.

Opting out of individual measurement applies at once, even to emails already received: later opens and clicks follow your account's mode, while those recorded before, with the consent, stay. Nothing else changes: the person keeps receiving your emails and their event participation stays as it is.

What happens when somebody stops receiving invitations, from the page or from their mail client's button:

  • The contact stays in the address book, with the status updated.
  • They no longer receive any campaign, across your whole account, not even of the events they signed up for — on the landing form, by answering yes to the invitation, or because they are confirmed: if you add them as a guest to an event, they stay out of the recipients. The rules are in Who receives a campaign.
  • They keep receiving the automatic confirmation and denial emails of their event registrations.
  • If they stop while a campaign is about to go out, their message is not sent and shows as Blocked.

Anyone who changes their mind can get the invitations back from the same page: the link keeps working. Emails sent before October 2026 still carry the old unsubscribe link, which keeps working.

In previews and test sends the link opens a demo version of the page: you can try the buttons, but choices are not saved.

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.

The whole guide