Visitor choice
Analytics remains disabled until a valid consent choice is recorded.
Last reviewed: August 17, 2026
This policy explains how LUX24 uses cookies, browser storage, software development kits and similar technologies across lux24.limo, the LUX24 booking platform, the Rider App and the Driver App. It also explains why these technologies are used, which service providers may receive information and how you can manage available choices.
This policy should be read together with the LUX24 Privacy Policy. Where an app-store privacy disclosure or an in-app notice provides more specific information about a mobile feature, the more specific notice applies to that feature.
Analytics remains disabled until a valid consent choice is recorded.
Sign-in, booking progress, security and payment rely on essential storage.
Mobile SDK and permission details are published here only when verified.
LUX24 uses Google Analytics 4 on the website and booking platform with production measurement ID G-5DF0H5R8YQ. It measures website and booking-platform usage, such as page views, navigation patterns, browser characteristics and related technical information.
Google Analytics is treated as non-essential Analytics. It now remains disabled until the required consent is recorded through the LUX24 consent panel. You can withdraw that choice later through “Manage Cookie Preferences” in the website footer.
LUX24 uses Google Maps Platform for address suggestions, geocoding, route calculations and related booking functions. Requesting those features may send technical, location or entered-address information to Google.
Current production code loads Maps when the public booking flow uses address and route features, and in certain authenticated map-based tools. It is not loaded by default on every public content page.
LUX24 uses Google reCAPTCHA v3 to help distinguish legitimate use from automated abuse. It may process technical, browser and interaction information.
The current production code confirms reCAPTCHA on the Contact page form. This page does not claim that every form uses reCAPTCHA.
LUX24 uses Stripe Checkout for secure hosted payment processing. Customers are redirected to Stripe’s checkout page to enter payment-card details directly with the approved payment provider.
Stripe may process transaction, fraud-prevention and related technical information required to complete and secure payment. Payment-card fields are not collected directly through a cookie controlled by LUX24 on the public website.
The current production website requests the Fraunces and Inter typefaces from Google servers through fonts.googleapis.com and fonts.gstatic.com.
Because those resources are not currently self-hosted, the browser connects to Google when those font files are requested.
Technology or key
Environment
Provider
Category
Purpose
Data involved
Duration
Activated
lux24_token
Website and Booking Platform
LUX24
Essential
Maintains authenticated account access and authorizes account requests.
Authentication token linked to the signed-in account session.
Until logout, browser deletion or server-side token expiry.
Automatically after sign-in.
lux24_user
Website and Booking Platform
LUX24
Essential
Remembers the account data needed to render the signed-in experience.
Account profile details required by the interface.
Until logout or browser deletion.
Automatically after sign-in.
lux24_pricing
Website and Booking Platform
LUX24
Essential
Caches pricing data used by the booking interface.
Route-pricing and service-class pricing information.
Until replaced by new pricing data or browser deletion.
Automatically when pricing data is requested.
lux24_pricing_version
Website and Booking Platform
LUX24
Essential
Tracks the pricing-data version used by the current interface cache.
Pricing cache version value.
Until replaced or browser deletion.
Automatically with pricing cache updates.
lux24_booking
Booking Platform
LUX24
Essential
Preserves route and booking details while the customer moves through booking steps.
Pickup, destination and related booking-progress details.
Current browser tab or current browser session.
Automatically during booking.
redirect
Website and Booking Platform
LUX24
Essential
Returns the user to the intended page after a sign-in or navigation step.
Target route or redirect destination.
Until used or until the browser session ends.
Automatically when a redirect step is needed.
lux24_cookie_consent_v2
Website and Booking Platform
LUX24
Essential
Stores the visitor’s consent choice, consent version and the time that choice was recorded.
Necessary always-on flag, analytics choice, version, updatedAt and expiresAt values.
Up to 180 days, until replaced, or until the user changes or deletes it.
Automatically when a cookie choice is saved.
_ga / _ga_*
Website and Booking Platform
Google Analytics
Analytics
Distinguishes browser instances and measures website or booking-platform use.
Technical and usage information associated with analytics measurement.
Provider-controlled persistent cookie duration under Google Analytics settings and documentation.
Only after analytics consent.
Google Maps JavaScript API
Booking Platform
Preference / Functionality
Provides address search, route calculations, geocoding and map-based booking features.
Entered addresses, route requests, browser details and related technical requests.
Provider-controlled cookies or browser storage when map or address features are requested.
When the customer uses a map or address feature.
Google reCAPTCHA v3
Website
Essential
Protects the Contact page form from automated abuse and spam.
Technical, device and interaction information used for abuse detection.
Provider-controlled when the protected form is used.
When the Contact page form requests protection.
Stripe Checkout
Booking Platform
Stripe
Essential
Processes secure hosted checkout, fraud prevention and payment completion.
Transaction, checkout-session and related technical payment data.
Provider-controlled on Stripe-hosted checkout pages and according to Stripe’s documentation.
When the customer proceeds to payment.
Google Fonts requests
Website and Booking Platform
Preference / Functionality
Delivers the Fraunces and Inter typefaces used by the website.
Browser request metadata needed to load font styles and font files.
Provider-controlled request and cache behaviour.
Automatically when pages request Google-hosted fonts.
Manage Cookie Preferences
Yes. You can reject non-essential Analytics and continue to browse the website and use essential booking functions. Essential technologies required for account access, security, booking progress or payment may remain active.
Select “Manage Cookie Preferences” in the website footer. You can change or withdraw your choice for future use. You may also delete existing cookies or browser storage through your browser settings.
Yes. This policy explains the general use of similar technologies across the LUX24 website, booking platform, Rider App and Driver App. App-specific permissions and SDK disclosures are also provided through the applicable app store and in-app notices.
No. Deleting browser or app storage may sign you out or remove saved preferences, but it does not automatically delete account, booking, payment or support records retained under the LUX24 Privacy Policy.
The August 17, 2026 production review did not identify optional advertising cookies on the public website or booking platform. Mobile-app advertising or audience-measurement disclosures, where applicable, are provided through the current app-store listing and in-app notices.
Cookie Policy
LUX24 reviewed the current production website, booking flow, public payment handoff and published app listings before this update. Website and booking-platform technologies listed below were verified from current production code. Mobile-app SDK-level details are published here only when they can be confirmed from the current production build or the applicable store disclosure.
The LUX24 website provides information about services, vehicle classes, safety standards, accessibility, corporate travel and available service areas. Website technologies may be used to operate pages, remember selected preferences, protect forms and understand how visitors use the website.
The booking platform allows customers to enter pickup and destination information, select a date and time, compare available service classes, review a fare and complete a booking.
Essential browser storage is required to preserve booking progress, maintain an authenticated session, prevent misuse and return the customer to the correct stage of the booking process. Disabling essential storage can cause sign-in, booking or payment functions to stop working correctly.
The Rider App supports passenger account access, booking management, chauffeur and vehicle details, trip-status information, in-app communication, payment records and rider-support functions.
The current production website and published app listings confirm that the Rider App is distributed through the Apple App Store and Google Play. This page does not publish unverified mobile SDK names or permission claims. Current app-store disclosures remain the reference point for app-specific permissions, device-level storage and mobile analytics or advertising disclosures.
The Driver App supports chauffeur account access, eligibility and document workflows, journey offers, accepted-trip details, navigation-related functions, communication and Driver Support.
The current production website confirms a live Google Play listing for the Driver App. This page does not imply continuous background tracking, a specific SDK or a specific permission flow unless that behaviour is confirmed in the current production app and reflected in the applicable store listing or in-app notice.
Cookies are small text files stored by a website in a browser. They may be used for a single browsing session or remain until they expire or are deleted.
Similar technologies include local storage, session storage, pixels, tags, mobile SDKs and device identifiers. These technologies do not all operate in the same way, but they can support account access, security, preferences, booking progress, analytics and app functions.
First-party technologies are set or controlled directly by LUX24 to operate its website, accounts, booking functions and user preferences.
Third-party technologies are provided by another company. Depending on the requested feature and the user’s choices, third parties may process technical, device, usage, location, payment or security information under their own privacy notices.
LUX24 lists below only providers that were identified in the current production environment or through the current public app listing reviewed on August 17, 2026.
Essential technologies are required to operate requested services and protect the website, booking platform or app. They may be used to maintain an authenticated session, preserve booking progress, remember privacy choices, protect accounts, forms and transactions, prevent misuse or fraud, and route the user through requested payment or support functions. Essential technologies cannot be disabled through the LUX24 consent panel when they are strictly necessary to provide a feature requested by the user.
Preference technologies remember choices such as language, display settings or previously selected options. They are used to reduce repeated input and provide a more consistent experience.
Analytics and performance technologies help LUX24 understand how the website or booking platform is used, identify technical errors and improve performance. Non-essential analytics remain disabled until the required consent is obtained on the website and booking platform.
The public website and booking platform review did not identify optional advertising cookies on lux24.limo during the August 17, 2026 review.
The table below reflects technologies verified from the current production website and booking-platform codebase. It identifies whether the item is a Cookie, Local Storage item, Session Storage item or third-party script or service.
LUX24 confirmed the previously observed keys lux24_token, lux24_user, lux24_pricing, lux24_booking and redirect. The current production code also uses lux24_pricing_version and a consent-storage key for the cookie-choice panel.
The current website repository does not contain the native Rider App or Driver App source used to verify a full mobile SDK or device-storage inventory.
For that reason, we publish only the verified public app listings and the general types of app technologies they may use, and we do not publish unverified SDK names, background-location claims or retention periods for mobile-app storage.
Browser and app storage help a device remember session or preference information. Deleting that storage may sign you out, remove saved choices or interrupt an unfinished booking. It does not automatically delete booking, account, payment or support records retained under the LUX24 Privacy Policy.
You can accept or reject non-essential technologies through the LUX24 consent panel. Essential technologies remain active when they are required to provide a feature you request or protect the service.
Your booking is not conditional on Analytics consent. You can reject non-essential Analytics and continue to browse the website and use core booking functions.
You can change or withdraw your choice at any time by selecting “Manage Cookie Preferences” in the website footer. A changed choice applies to future use. You may also need to delete existing browser storage through your browser settings.
The Rider App and Driver App may provide privacy controls within their settings. You can also manage permissions such as location, notifications, camera and photos through your device settings.
Disabling a permission may prevent the related feature from working. LUX24 should request a device permission only when it is required for a clearly explained function.
For information about data associated with an app download or mobile SDK, review the current privacy disclosure on the applicable App Store or Google Play listing.
Some service providers may process information outside the province or country where you are located. Their processing is governed by their own privacy notices and the agreements applicable to their services. Additional information about LUX24 service providers, cross-border processing and privacy rights is available in the LUX24 Privacy Policy.
Retention depends on the technology and its purpose. Session storage is generally removed when the relevant browser session ends. Persistent storage remains until its configured expiry, until it is replaced or until the user deletes it. Mobile-app storage may remain until it is cleared, the user signs out or the app is removed. The table above provides the verified duration or deletion condition for each technology. Where a third party controls duration, refer to that provider’s current documentation.
LUX24 may update this policy when its website, booking platform, apps, providers or legal obligations change. The “Last reviewed” date will be updated only after a substantive review. Material changes affecting user choices will be communicated through an appropriate notice or renewed consent where required.
For questions about cookies, browser storage, mobile SDKs or privacy choices, contact LUX24 through the Contact page or the privacy contact identified in the LUX24 Privacy Policy.
Include the device, browser or app involved and the page or feature you were using. Do not send passwords, payment-card details, authentication codes or copies of identity documents by ordinary email.