Cookie Policy
This Cookie Policy explains how RoyalTui uses cookies, browser storage and consent controls on www.royaltui.com.

Effective date: 2 July 2026.
1. What cookies are
Cookies and similar technologies are small files or browser storage entries used to operate a website, remember user choices, protect forms, measure site use and support advertising measurement where consent is given.
2. Cookies used by RoyalTui
RoyalTui uses necessary cookies and local storage to keep the website working, remember cookie choices, support navigation and reduce spam or misuse of enquiry forms. These are required for the website to operate properly.
3. Optional analytics storage
Analytics storage helps RoyalTui understand how visitors use the website so we can improve the guest experience. Analytics storage is denied by default and is used only if you grant analytics consent in the cookie banner or settings panel.
4. Optional marketing storage
Marketing storage may support advertising measurement, ad user data and ad personalisation where advertising tools are connected. Marketing storage is denied by default and is used only if you grant marketing consent. RoyalTui does not use the website to advertise gambling incentives, casino bonuses, wagering offers or casino pricing.
5. Google Consent Mode v2
The website includes Consent Mode v2-ready settings. The default consent state is denied for ad_storage, analytics_storage, ad_user_data and ad_personalization. If Google tags are installed, they must respect the visitor’s consent state.
6. Your choices
The first cookie layer offers Accept all, Reject all and Settings. Optional analytics and marketing choices are not pre-ticked. You can change your choice later by selecting “Change cookie settings” in the footer.
7. Managing cookies in your browser
You can also block or delete cookies through your browser settings. Blocking necessary cookies may affect website functionality, form behaviour or the ability to remember your preferences.
8. Updates
RoyalTui may update this Cookie Policy if cookies, tags or consent processes change. The effective date above identifies the current version.