Cookie Policy
This Cookie Policy describes how resort-review.com uses cookies and similar storage. The site is a casino resort review of licensed hotel-casinos in the United Kingdom. It is not a gambling product. The banner at the bottom of the screen tells you that we use cookies so the site can work and so we can remember your choice. Pressing Accept stores that choice. After a recorded acceptance, the banner does not show again on that browser unless you clear storage.
UK law (the Privacy and Electronic Communications Regulations, as amended) requires a clear explanation of cookies that are not strictly necessary. We keep the set small on purpose.
Fourteen points on cookies and storage
- What a cookie is. A cookie is a small text file a site can store on your device. LocalStorage is a related browser store. Both can remember a setting after you close a tab. Neither is a casino account.
- The consent banner. The banner is fixed to the bottom of the viewport. It contains a short notice, a link to the Privacy Policy, a primary Accept button, and a secondary Close button. It can be reached with the Tab key. Buttons have accessible names.
- Accept. If you press Accept, we write the value "accepted" to localStorage under the key cookie_consent. The banner then hides with a short animation and will not return on later visits in that browser, unless you delete the key.
- Close. If you press Close, the banner hides and we store "dismissed" under the same key so the panel does not sit over the footer for the rest of the visit. We do not treat Close as consent for extra marketing cookies because we do not set those cookies.
- cookie_consent. This is the only first-party storage key we set in JavaScript. It is not sent to a casino operator. It does not contain your name or email. It lasts until you clear site data.
- Strictly necessary tools. Session cookies that a host may set to keep HTTPS stable, balance traffic, or remember a security token are treated as necessary for the service you asked for (loading the page). They are not used to advertise rooms or games.
- What we do not set today. We do not embed Facebook pixels, Google Ads tags, or casino affiliate trackers on this version of the site. If that changes, we will name the cookie, the provider, and the purpose in this list before the tag goes live.
- Fonts. Type is loaded from files on this domain (woff2 in the /fonts folder). We do not call Google Fonts in the browser, so Google does not receive a font request from your visit to this site.
- Outbound sites. When you open Booking.com, a hotel site, or the Gambling Commission, those organisations may set their own cookies. We do not control them. Read their cookie notices if you create an account there.
- Forms. Submitting a contact or offer form does not require a marketing cookie. The script only checks that the form is valid, clears the fields, and opens a success dialog on this page. Message contents are not written into cookie_consent.
- How to delete the key. In most desktop browsers, open developer tools or site settings, find localStorage for resort-review.com, and remove cookie_consent. You can also clear cookies and site data for this origin. After deletion, the banner will show again.
- Mobile browsers. Safari, Chrome, and Firefox on phones also store localStorage per origin. If you use private browsing, the key may vanish when the session ends, and the banner can reappear. That is expected.
- Do Not Track and Global Privacy Control. This static site does not currently change behaviour based on DNT or GPC headers because we do not run a third-party ad stack. If we add analytics later, we will honour a published GPC signal for that tool.
- Questions. Email [email protected] with the subject "Cookies". We will explain whether a new tag has been added since this page was dated 16 October 2026. Related rules sit in the Privacy Policy and Terms of Use.
Language of the banner
The whole website, including the cookie banner, is written in English because the domain serves readers looking at United Kingdom hotel-casinos. Buttons are labelled Accept and Close so they match the rest of the interface and remain clear to a keyboard user.