GDPR for hotels: consent, opt-out and erasure work together

For operators who want to keep guest data in order without checking every message by hand. HAYP records what a guest consented to, checks it before every automated message and handles withdrawal, access requests and retention periods in the guest profile.

Consents tab in the guest profile: current status per purpose, history with source and wording, status of automated messages
The real HAYP interface, shown with sample data.

How the GDPR features work together

From the pre-check-in to erasure, every step writes to the same record or reads from it. A guest's decision therefore applies wherever HAYP sends messages automatically.

  1. 01

    Consent in the pre-check-in

    The guest chooses per purpose. No box is ticked in advance, and marketing is never required.

  2. 02

    Record in the guest profile

    Wording, version, time and source of every consent, each as an entry of its own.

  3. 03

    Check before every send

    Consent, opt-out, profile status and the exclusion list are checked right before the message.

  4. 04

    Message with a sender

    Emails name the property's legal notice and privacy policy; marketing also carries an unsubscribe link.

  5. 05

    Withdrawal without a login

    Through the consent page, the unsubscribe link, STOP on WhatsApp or a spam report.

  6. 06

    Retention and erasure

    Guest profiles are restricted, anonymized or erased after your period; erased contacts stay blocked.

Every withdrawal becomes a new entry in the same record and applies from the next automated message.

From the form in the pre-check-in to the entry in the guest profile.

In the editor

You set purposes, wording per language and the link to your privacy policy; marketing cannot be set as mandatory.

Pre-check-in editor with three consents, wording per language and a link to the privacy policy

For the guest

The guest sees empty boxes and a note on how to opt out of automated messages.

Consents in the pre-check-in on a phone with empty boxes

In the guest profile

Every decision is in the profile with time, source and wording.

Consents in the guest profile with history, source and wording

After STOP

If a guest replies STOP, the withdrawal appears as an entry of its own.

Guest profile with a WhatsApp opt-out by STOP

Before an automated message goes out, HAYP checks in a fixed order: is the reservation blocked for automated messages? Is the guest profile restricted? Is the address on the exclusion list? Does the WhatsApp privacy mode require an opt-in? Is the required consent in place, and has the guest opted out on this channel? Only then do your send rules for automated messages apply.

Every delivery stores which consent was decisive: purpose, granted or not, time and version of the text. For skipped messages, the log shows the reason, such as “no consent” or “opted out”. A message your team writes itself still goes out; the inbox shows the guest's status while you write.

This is how HAYP decides per purpose and channel. You set the purpose for every message.

PurposeWhatsAppEmailAirbnb & Booking.com
Service: arrival, check-in, check-outno consent needed; with privacy mode only after a WhatsApp opt-inno consent neededallowed, with a content check
Marketingconsent “marketing by WhatsApp”consent “marketing by email”, legal notice and unsubscribe linknot allowed
Review requestconsent “review request”consent “review request”, legal notice and unsubscribe linknot allowed

Withdrawal and opt-out without anyone chasing it

Guests opt out where the message arrives. HAYP writes every opt-out to the same record.

Consent page without a login

From the email the guest opens a page with their active consents and withdraws them with one click.

Consent page on a phone with active consents and the button to withdraw the selection

WhatsApp privacy mode per number

When it is on, automated messages from this number only go to guests with a WhatsApp opt-in. Beforehand HAYP shows how many planned sends in the next seven days would be dropped.

Dialog “Turn privacy mode on” stating that 3 of 41 planned WhatsApp sends without an opt-in would be dropped

Unsubscribe link in marketing and review requests

The footer names the property's legal notice and privacy policy. Without a legal notice, such an email does not go out at all.

Email preview of a review request with the footer: legal notice, privacy, unsubscribe

A log with the decision

For every delivery the log shows recipient, language and the decision of the check, for marketing including the consent that applied.

Details of one delivery in the log with recipient, language and the applicable consent “review request”

Access, restriction and erasure in the guest profile

Privacy

Restrict, anonymize, delete and export, each with its own permission.

Privacy tab with restrict, anonymize, delete and export

Anonymize

Before final steps HAYP asks for confirmation and records a reason if you wish.

Anonymize dialog with a warning that the action cannot be undone

Retention

Policies for guest profiles with period and action, if you wish only for guests who canceled.

Retention policies with period and action

Pending

What happens next, with a date; every action can be canceled until then.

Pending retention actions with execution date

Exclusion list

Shared addresses, throwaway platform addresses and erased guests do not count when matching.

List of excluded contact details with reason

Data minimization: AI, roles and sign-in

01

AI sees only what you release

At the start the AI sees no fields. It never gets ID or consent data or internal notes; fields can be released on a schedule, for example only from check-in.

02

AI replies are labeled

When the AI replies on its own, the first reply carries a notice. In autonomous mode it cannot be switched off.

03

Roles with data access per property

A role only sees the properties, units and inboxes assigned to it. Export, restriction and erasure need a permission of their own.

04

Sign-in without a password

Staff sign in with a code by email or a passkey. Accounts exist by invitation only.

05

Hosted in Frankfurt

The platform and the database run in data centers in Frankfurt am Main. All AI features run in the EU, and no AI model is trained on your data.

06

Guest pages kept out of search

Pre-check-in, forms and the consent page are blocked for search engines and name your property as the controller.

FAQ

Frequently asked questions about GDPR for hotels

Is there a data processing agreement?

Yes. HAYP processes guest data as a processor on behalf of your operation. We provide a data processing agreement (DPA) on request.

Can a hotel use WhatsApp Business in line with the GDPR?

That depends on how you use WhatsApp. HAYP gives you the tools: the WhatsApp consent in the pre-check-in, the privacy mode per number, opt-out by STOP in six languages and each guest's status in the inbox. Whether your use is lawful is a question for your legal adviser. More under WhatsApp for hotels.

How long does HAYP keep guest data?

For guest profiles you set retention policies: a period from the last stay or the last cancellation, after which the profile is restricted, anonymized or erased. Anonymizing and erasing follow 28 days after the profile is marked, and until then you can cancel. Policies are switched off at the start. Technical data such as the delivery log expires after fixed periods.

What happens when a guest asks for access or erasure?

In the guest profile you export profile, reservations, pre-check-ins, reviews, consents and history as a JSON file. On erasure, HAYP passes the erasure on to automated messages and guest forms and blocks the contact details for further automated messages. Each of these actions is recorded with person and time.

Where is the data processed?

The platform and the database run in data centers in Frankfurt am Main. All AI features run in the EU, and no AI model is trained on your data. Which service providers take part in individual functions is listed in the privacy policy.

Isn't a home-built script or an AI assistant enough for this?

A script can send messages. For the GDPR, however, consent records, the check before every send, withdrawal and erasure have to work together and stay traceable. An AI assistant in the browser that uses a password and a two-factor code to fetch phone numbers from the extranet raises new questions instead: who has access, where does the data go, and what do the platforms' rules say? More under build or buy and in the guide on the guest's phone number.

Walk through your privacy settings in a demo

We show consent, the check, withdrawal and retention periods with sample data.