Savoy Executive
Cookie Policy
How this website uses cookies and related technologies for booking, maps, security and payment.
Last updated: 29 August 2026
This policy explains how Savoy Executive’s website uses cookies and related storage or access technologies when you browse the site, search for locations, use the booking form or open secure payment.
Optional website analytics
With your consent, we use Google Analytics to understand page visits, booking stages and clicks on our phone or WhatsApp contact links. This helps us identify where visitors leave the booking journey. Reaching Review is not recorded as a completed or paid booking.
Our analytics integration does not send traveller names, email addresses, phone numbers, journey addresses, form-field contents or booking URL parameters. Google receives technical information such as browser/device information and an online identifier to provide analytics. See Google’s Privacy Policy for its processing practices.
You can accept or reject analytics without affecting booking. Use Privacy preferences to change or withdraw your choice. Your choice is stored locally for up to 180 days. When accepted, this integration uses analytics cookies with the savoy_ga prefix for up to 180 days. Withdrawal stops this integration’s future analytics events and removes its accessible analytics cookies; it does not remove data already processed by Google.
This analytics preference controls this Google Analytics integration, not necessary booking, map, security or payment services.
PostHog booking and enquiry analytics
If you accept analytics, we also use PostHog’s EU-hosted service to measure page groups, broad traffic sources, booking stages, vehicle classes, enquiry progress and general error categories. PostHog uses a random identifier stored for the browser tab. These counts represent anonymous tab journeys, not identified customers. Session replay and automatic click capture are off.
We do not send names, email addresses, phone numbers, journey addresses, flight information, booking references, customer or payment identifiers, form contents, raw click identifiers or URL query values. We disable person profiles and location enrichment. PostHog receives the network IP when a request reaches its service; this project is configured not to retain IP addresses in analytics events. See PostHog’s Privacy Policy.
The same Accept analytics and Reject analytics choices control Google Analytics and PostHog. Older Google-only choices do not enable PostHog: we ask again with this disclosure. Withdrawal stops new events and clears this integration’s tab identifier and source classification. It does not erase events already processed. Necessary booking, maps, security and payment services continue to work.
Optional advertising measurement
Advertising measurement has its own choice in Privacy preferences and is off until you allow it. Accepting analytics does not accept advertising. When allowed, Google Ads can receive a verified completed booking total in GBP and an opaque conversion identifier. We do not send traveller contact details, routes, flight numbers, booking references or payment identifiers as conversion data. Google also processes technical browser and network information and may use advertising attribution cookies. Advertising personalisation signals are disabled.
You can withdraw advertising separately in Privacy preferences. Withdrawal stops future conversions from this integration and removes its accessible attribution cookies; it does not erase information already received by Google. A loaded Google tag may process the consent update. Blocking scripts or leaving the confirmation page before verification can mean a paid booking is not counted.
With analytics consent, PostHog can also receive a verified paid-confirmation event without a value or booking identifier, and an enquiry-success event after the site saves a valid enquiry. These measure site processing, not email delivery. Necessary booking and payment services work without either optional choice.
