Before you choose anything

Most sites set analytics cookies on page load and show you a banner afterwards. This one loads with Google Consent Mode set to denied on all four signals — analytics storage, ad storage, ad user data, ad personalisation — before any Google code runs. On top of that, the Google Analytics script is only requested at all when a measurement ID has been configured for the deployment. When one has not been, your browser never contacts Google about analytics, consent or otherwise.

If you press Accept

We flip one signal — analytics storage — to granted. The other three stay denied permanently, on every page, for everyone: we run no advertising product, so there is nothing for them to turn on. Google Analytics may then set these two first-party cookies:

Swipe the table sideways to see every column.

Cookies set only after you accept
NameSet byPurposeExpires
_gaGoogle Analytics 4Tells one browser apart from another, so two visits are not counted as two people2 years
_ga_<id>Google Analytics 4Keeps session state for this specific property2 years

We use them to count page views, see which city and guide pages people actually read, and see which filters, calculators and forms get used. Those events carry the option picked (a guest-count band, a style), never anything you type. We do not use them to build an advertising profile, and we have no way to turn them into one: the ad signals are denied in code, not in a settings panel someone could flip.

If you press Reject

Nothing is granted and no analytics cookie is set. We store one thing either way — see below — because a banner that forgets you rejected it is a banner that asks again forever.

The one thing we store whatever you choose

When you press either button we save your answer in your browser's local storage under the key hw_consent, with the value granted or denied. It is not a cookie — it is never sent to us or to anyone else, it just stops the banner reappearing on every page. It is strictly necessary for remembering your choice, which is why it does not itself need consent. Until you press a button, not even this is stored.

Changing your mind

Use Cookie settings at the bottom of any page: the banner comes back and you can choose again. Choosing Reject after Accept stops analytics from that moment; the Google Analytics cookies already set stay in your browser until they expire or you clear them. To clear everything, delete this site's data in your browser:

Your browser's own controls work too — blocking cookies for this site, or private browsing — and nothing here will try to route around them. If your browser sends the Global Privacy Control signal, we take it as a no: the banner does not ask, and nothing is set unless you opt in from Cookie settings.

Other things your browser fetches

These set no cookies, but your browser has to contact them, which means they see your IP address. Listing them because “we only use one analytics cookie” would be technically true and practically misleading:

Swipe the table sideways to see every column.

Third-party requests, cookies or not
WhoWhat forWhen
VercelHosting — it serves every page, and logs the requestEvery page load
FormspreeDelivers a hotel claim or a room-block request to our inbox where our own database route is not switched on yetOnly when you submit one of those forms

What is not on this site

No advertising cookies. No retargeting pixel — no Meta pixel, no LinkedIn insight tag, no TikTok pixel. No cross-site tracking, no fingerprinting, no session recording, no heatmaps, no A/B testing tool, no chat widget. If you find something here that we have not listed, email privacy@hotelweddings.com — that would be a bug, and we would want to know.

More

What happens to the details you type into a form is in the privacy policy. The rules for using the site are in the terms of use.