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.

What cookies and related technologies are

Cookies are small text files stored by a website or service in a browser. Websites can also use local storage, scripts, tags and similar technologies to store or access information on a device. Some are used only for a browser session; others can remain between visits.

Strictly necessary technologies support a service requested by the visitor, such as security, a booking session or hosted payment. Optional technologies used for analytics, advertising or preference tracking require the appropriate choice before they are activated.

Technologies used by this site

Service/category Purpose When used Typical duration/control
WordPress and security Deliver pages, protect forms and administration, and retain signed-in state where applicable. When required for the requested page, security check or authorised sign-in. Session or provider-configured. Public visitors do not need an administrative login cookie.
Quantica booking system Keep the requested journey, booking step and validation state together while the booking form is used. When the booking interface is opened or used. Primarily session/booking state.
Google Maps, Places and Routes Provide location search, place details and journey-map/route functions requested in the booking form. When location and map functions load or are used. Google-controlled cookies or storage may apply; see Google’s policy and browser controls.
Stripe hosted payment Open secure card payment, prevent fraud and return payment status to the booking system. Only after secure checkout is opened. Stripe-controlled cookies or storage; see Stripe’s policy and payment controls.

Cookie names and expiry can change when WordPress, the licensed booking plugin or third-party services are updated. Savoy must repeat the inventory and update this table before adding or materially changing a technology.

Analytics, advertising and marketing

Optional Google Analytics is used only after you choose Accept analytics.

If optional technologies are introduced, the website must provide an equally clear way to accept or refuse them and a way to change that choice later. Simply continuing to browse will not be treated as consent.

Your choices

You can delete or block cookies through browser settings. Blocking technologies needed for security, location search, a booking session or hosted payment may prevent those requested functions from working correctly.

  • Use browser privacy settings to view, delete or block stored information.
  • Use private-browsing mode where appropriate, while recognising that it does not make browsing anonymous.
  • Do not proceed to Stripe checkout if you do not want the hosted payment service to load.
  • If an optional consent control is displayed in future, use it to accept, refuse or revisit non-essential choices.

Third-party services

Third-party services operate under their own privacy and storage practices. Current information is available from Google’s Privacy Policy and Stripe’s Privacy Policy. Their services and cookie durations may change independently of this website.

Where a third-party technology is not strictly necessary for a service you request, it must not be activated before the required consent state.

Updates and contact

Savoy will review this policy when the booking system, payment provider, maps service, security tools or tracking configuration changes. Questions can be sent to info@savoyexecutive.com.

For more information about personal information used through these services, read the Privacy Policy.

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.