TL;DR
A hotel guest hands you personal data for one reason: to stay. Everything else you do with it, newsletters, WhatsApp offers, retargeting, loyalty nudges, needs its own legal footing, and that footing differs between the UK, Singapore and the UAE. The practical answer is not three separate systems. It is one consent model in your property management system (PMS), CRM and booking engine that records what the guest agreed to, when, how, under which wording, and can honour a withdrawal on every channel quickly. This article explains the differences that matter and how to design for them.
This is a technical and operational guide, not legal advice. Confirm your specific obligations with qualified counsel in each jurisdiction.
Why hotels get consent wrong
Hospitality is unusually exposed to consent problems for structural reasons.
First, guest data is collected in many places by different parties: the booking engine, an online travel agency (OTA), the front desk, a Wi-Fi portal, a spa booking form, a loyalty sign-up, a restaurant reservation tool. Each touchpoint writes to a different system, and each tends to use its own tick-box wording.
Second, the same person is a customer, a loyalty member, a corporate booker's colleague and a prospect for the next stay. A single email address can carry three different legal bases in the same week.
Third, marketing preferences are often stored as a single true/false flag. That flag cannot answer the questions a regulator, or an angry guest, will actually ask: consent to what? Collected where? Using which words? Withdrawn when?
If your current system cannot answer those four questions for a randomly chosen guest record, you have a design problem before you have a legal one.
The three regimes in plain language
United Kingdom: UK GDPR plus PECR
In the UK, two layers apply. UK GDPR governs personal data in general. The Privacy and Electronic Communications Regulations (PECR) add specific rules on electronic marketing. The ICO's guidance on PECR is the best starting point: How do we comply with the PECR electronic mail marketing rules?
What the ICO guidance establishes, in practical terms:
- Unsolicited email marketing to individual subscribers needs either consent or all the conditions of the "soft opt-in". Corporate subscribers do not need consent or a soft opt-in.
- Consent follows the UK GDPR standard: a freely given, specific, informed and unambiguous indication. The guidance says you must not use pre-ticked opt-in boxes, silence or inactivity as evidence of consent.
- Consent must be withdrawable, and you must stop sending once it is withdrawn.
- You must give people the chance to opt out in every marketing message, free of charge apart from the normal cost of sending the message, and you should not require an account just to unsubscribe.
The soft opt-in matters a great deal for hotels, because a guest who has just booked a room is the textbook case. The ICO lists five conditions, all of which must be met: you obtained the contact details yourself; you did so while selling, or negotiating to sell, a product or service; you only market your own similar products or services; you offered an opt-out when you collected the details; and you offer an opt-out in every later communication.
Two practical implications follow. Details obtained through an OTA are usually not details you obtained yourself in the sense that matters here, so check carefully before treating OTA guests as soft opt-in contacts. And "similar products or services" is narrower than many marketing teams assume. A room-night guest receiving an offer for your own spa or restaurant is easier to defend than a third-party partner's promotion.
Penalty exposure. According to a Mayer Brown briefing on the Data (Use and Access) Act 2025, the maximum PECR fine is raised from £500,000 to £17.5 million or 4% of annual global turnover, aligning it with UK GDPR. The same briefing notes a statutory definition of direct marketing and a 72-hour breach notification duty to the ICO under PECR. The briefing gives the Royal Assent date but not the commencement dates for each change, so confirm what is in force when you plan your compliance work.
Singapore: PDPA and the Do Not Call provisions
Singapore's Personal Data Protection Act (PDPA) has a general consent regime, and a separate set of Do Not Call (DNC) provisions for marketing messages. The PDPC publishes an organisations' guide to the DNC provisions and the Advisory Guidelines on the DNC Provisions.
The DNC framework is tied to Singapore telephone numbers, and covers voice calls, text messages and fax through separate registers (the No Voice Call, No Text Message and No Fax Message registers). Before sending a specified message to a Singapore number, you must check the relevant register, unless the person has given "clear and unambiguous consent in evidential form". Messages must also identify the sender and say how to contact them.
Three points for hotel teams:
- Evidence is the point. The phrase "in evidential form" means you need to be able to show the consent later: the wording, the date, the channel. A free-text note in a guest profile is weak evidence. A time-stamped record linked to the wording version shown is strong.
- Channel matters. The guidelines' own examples draw a line between messages sent to a Singapore telephone number and messages sent to an email address; an email address alone does not make a message a DNC "specified message". That does not mean email marketing is unregulated in Singapore: the PDPA's general rules on consent for using personal data still apply, so treat email as covered by your consent model and ask counsel where the edge cases sit.
- Inaction is not consent. The guidelines indicate that a mere failure to opt out is unlikely to amount to clear and unambiguous consent, and that you should not make consent to marketing a condition of supply beyond what is reasonable. Bundling marketing consent into a booking confirmation is therefore a poor design.
Note that the PDPC's guidelines describe themselves as advisory and not legally binding. Verify current penalty provisions on the PDPC's own site rather than relying on secondary summaries.
United Arab Emirates: federal PDPL, with free-zone regimes alongside
The UAE's Federal Decree-Law No. 45 of 2021 (the PDPL) sets a consent standard that will feel familiar to GDPR practitioners: consent should be free, specific and unambiguous, presented in clear and simple terms in writing or electronically, and the person can withdraw it at any time without affecting processing carried out before withdrawal (CookieYes summary of the UAE PDPL, a vendor overview, not the legal text).
Two cautions apply for anyone building now.
- Implementation detail has lagged. As of the 2025 secondary sources we reviewed, the executive regulations were described as pending, and enforcement was still maturing. Check the current status with local counsel before you assume the details are settled.
- More than one regime may apply. The DIFC and ADGM free zones maintain their own data protection laws. A group with a property in a free zone and another on the mainland may be dealing with different rules for different properties. There are also sector rules, for example around telecom marketing, that sit outside this article's scope.
The sensible engineering stance for the UAE is to build to the highest common standard you can already see (explicit, recorded, withdrawable consent) and keep the policy layer configurable so you can tighten it when the regulations land.
Comparing the three at a glance
| Question | UK (UK GDPR + PECR) | Singapore (PDPA + DNC) | UAE (PDPL) |
|---|---|---|---|
| Consent standard | Freely given, specific, informed, unambiguous | General PDPA consent; "clear and unambiguous consent in evidential form" for DNC specified messages | Free, specific, unambiguous, clear terms |
| Pre-ticked boxes / silence | Not valid as consent | Inaction unlikely to qualify | Unambiguous standard points the same way |
| Existing-customer exception | Soft opt-in, five conditions, individual subscribers only | DNC: check register or hold evidenced consent | Check current regulations with counsel |
| Opt-out in each message | Required | Identification and contact details required in messages | Withdrawal possible at any time |
| Channel nuance | Email, SMS and similar electronic mail | Rules keyed to Singapore telephone numbers for DNC | Confirm by channel and zone |
| Regime stability | In force; DUA Act changes phasing in | In force | Executive regulations were pending in 2025 sources |
What this means for your systems
Legal texts differ. The system you need to build does not differ nearly as much.
1. Separate purposes, not a single marketing flag
Model consent as a record, not a boolean. A useful minimum:
- Guest or contact ID
- Purpose (e.g. "own-brand email offers", "own-brand SMS offers", "partner offers", "profiling for personalised pricing")
- Channel
- Status (granted, withdrawn, never asked)
- Timestamp and source (booking engine, front desk tablet, Wi-Fi portal, app, import)
- Wording version (a pointer to the exact text and language the guest saw)
- Collected by (your property, a group company, an OTA feed, a third party)
- Basis (consent, soft opt-in, other)
That table answers the four questions: consent to what, where, under which words, and when withdrawn.
2. Make the front desk a first-class consent surface
Many marketing lists are built at check-in by a rushed human with a keyboard. If the PMS allows a free-text "marketing OK" note, that is where weak evidence is born. Give staff a clear, unticked, purpose-specific control, a short script, and a way to capture the guest's own action (for example, a tablet sign-off) where your risk appetite requires it.
3. Treat OTA and corporate data as a different class
Contact details arriving via an OTA or a travel management company should enter your CRM tagged with their origin and without a marketing flag inherited by default. Whether you can later rely on a soft opt-in or another basis depends on how and when you obtained the details, so let your policy layer decide rather than hard-coding assumptions.
4. One preference centre, honoured everywhere
A withdrawal in a footer link must reach the email platform, the SMS gateway, the WhatsApp or push tool, the loyalty system and the ad-audience export. If those are separate tools synchronised nightly, you have a window in which you will message someone who has said no. Prefer event-driven propagation, and make suppression lists authoritative: a guest on the suppression list is excluded even if another system still shows a stale "yes".
For a deeper look at unifying profile data across booking, stay and loyalty systems, see our guide to guest data platforms and the single customer view.
5. Region-aware policy rules, not region-specific code
Put the rules in configuration: which purposes need explicit consent in which jurisdiction, which channels are keyed to phone numbers, whether the soft opt-in is available for a given contact source, which wording variants to display. Then a property in Dubai, one in Singapore and one in London can share the same codebase while behaving differently. When the UAE regulations firm up, you change configuration, not architecture.
6. Log evidence, and keep it findable
Retain the wording versions, screenshots or templates of consent screens, and the audit trail of changes. If a regulator or a guest asks for proof, you should be able to retrieve it in minutes, not by reconstructing it from three vendors' exports.
7. Secure the stack that holds it
Consent records sit next to identity and payment-adjacent data. Weak integrations around the PMS undermine the whole programme; our article on cybersecurity architecture for hotel tech stacks covers where the integration risk tends to sit.
Buy, configure or build?
Most hotel groups will not build a consent platform from scratch. The realistic question is where consent logic should live.
| Option | Works well when | Watch out for |
|---|---|---|
| Rely on PMS and email-tool defaults | One property, one market, simple marketing | Single flags, no wording versions, weak withdrawal propagation |
| Add a dedicated consent or preference layer | Multi-system estate, several channels | Integration effort; must be the source of truth |
| Build consent into your guest platform or CRM | Multi-property, multi-region groups with bespoke journeys | Needs proper design, testing and ownership |
If your tech stack is already being rethought, for example during a booking engine decision, bring consent into that conversation early. Our guide on build, buy or hybrid for a hotel direct booking engine across the UAE, Singapore and the UK discusses the wider trade-offs, and consent capture at the point of booking is one of the highest-value places to get it right.
A practical rollout sequence
- Inventory every collection point. List each form, screen and integration that writes guest contact data, with its current wording.
- Map purposes and channels. Decide what you actually do with the data: own offers by email, SMS, WhatsApp, partner promotions, profiling, ad audiences.
- Define the jurisdictional rules. With counsel, write down for each market what basis you rely on for each purpose and channel.
- Design the consent record. Use the structure above; decide the system of record.
- Fix capture first. Booking engine, front desk, Wi-Fi portal and app. New data in the right shape is easier than repairing history.
- Wire suppression. Withdrawals must propagate to every sending tool.
- Handle legacy data deliberately. Segment old records by what evidence you have. Where you cannot show a valid basis, do not market to them on that channel; consider a clean re-permissioning campaign instead.
- Test with real scenarios. A UK guest booked via OTA; a Singapore mobile number given at check-in; a UAE guest who withdraws via WhatsApp. Trace each end to end.
- Review on a schedule. Laws, guidance and your own marketing tools change.
Common mistakes
- Treating consent as a one-time signature rather than a lifecycle with changes and withdrawal.
- Bundling marketing consent with terms of stay or booking acceptance.
- Pre-ticked boxes in booking flows, which the ICO guidance rules out as evidence of consent.
- Assuming OTA contact details are fair game. The origin of the data matters.
- Forgetting phone-number-keyed rules in Singapore when a text or messaging campaign is planned.
- Hard-coding one country's rules into a multi-market platform.
- No suppression authority. An unsubscribe in one tool that never reaches the others.
- Relying on a vendor's "GDPR compliant" label instead of checking how consent is stored and honoured in your own configuration.
How Syslabs approaches this
Syslabs builds custom software for hospitality and other regulated sectors, and consent is typically a design topic that spans several of our hospitality building blocks: the hospitality management platform, the guest experience app and the integrations between your PMS, CRM and email marketing automation. We usually start with a short discovery: which systems write guest data, what the current wording looks like, which markets you operate in, and where evidence is thin. From there we scope a consent and preference layer that fits your estate, and we work with your legal advisers on the policy rules. Scope and cost are set on a consultation rather than quoted up front. If compliance planning is a wider concern, our compliance and risk consulting and custom software development pages explain how we work.
Conclusion
The three regimes use different vocabulary, but they converge on a design that holds up in any of them: purpose-specific, unticked, evidenced consent; a clear route for withdrawal; and honest handling of where each contact came from. Build that once into your PMS, CRM and booking flows, keep jurisdiction rules in configuration, and your marketing team can run campaigns in London, Singapore and Dubai from the same foundations.
If you are planning a guest data, booking or CRM project and want consent designed in from the start, book a conversation with the Syslabs team. The booking page shows times in your own time zone.



