Cookies
Effective Date: December 1, 2026
Ludik Évasion Cookie and Tracker Policy
Version 1.1 - effective as of December 1, 2026.
Reference language notice: This English translation is provided for convenience only. In case of discrepancy, inconsistency, or interpretation difference, the French version shall prevail.
This policy explains how Ludik Evasion (the "Publisher") uses cookies, local storage and software development kits (SDKs) in the Ludik Évasion application, available on the web at https://ludik-evasion-preview.lezo.app and through the mobile applications published under the Ludik Évasion brand (the "Application"). It supplements the Application's privacy policy.
1. What this policy covers
A cookie or tracker is information read from or stored on your device, for example a browser cookie, local storage data or an identifier managed by an SDK in the mobile application.
Trackers that are strictly necessary for the service you request, or intended exclusively to enable communication by electronic means, do not require your consent. Other trackers, in particular non-exempt audience measurement, are used only with your agreement.
2. Website
2.1 Cookies
The website uses only cookies necessary for its operation. It performs no audience measurement and uses no advertising or social network cookies; it therefore does not display a consent request.
| Cookie | Purpose | Duration |
|---|---|---|
__Secure-questovery.session_token (without the __Secure- prefix over a non-secure connection) |
Keeping your authenticated session | Seven (7) rolling days, or until the browser is closed where you choose not to stay signed in |
__Secure-questovery.dont_remember |
Remembering the choice not to stay signed in | Until the browser is closed |
__Secure-questovery.state, __Secure-questovery.oauth_state |
Securing sign-in with a Google account, where offered | Five (5) minutes |
theme |
Remembering the light or dark display theme | Until the browser is closed |
sidebar_state |
Remembering whether the side menu is open | Seven (7) days |
The former qv_web_cache_release cookie is no longer created. If it remains in your browser, it is deleted when you load a page of the website.
2.2 Browser local storage
| Item | Purpose | Duration |
|---|---|---|
REACT_QUERY_OFFLINE_CACHE |
Caching data already loaded to speed up display; cleared when the account changes | Seven (7) days at most |
| Display preferences | Remembering the display mode chosen in dashboards and the editor | Until deleted by the browser |
Licence cart (questovery:license-cart) |
Keeping the licences you add to the catalogue cart: identifiers of the offer and its publisher, the category, the tariff and, where applicable, the existing licence to renew or top up, currency and quantities, without prices or contact details. When you are signed in and start a payment, the cart also keeps that payment in progress (identifiers of the order, your account and your organization, ordered lines) so that it can be resumed without creating a duplicate | Cart lines: until they are ordered, removed from the cart or the website's data is cleared in your browser; lines concerning an existing licence are removed at sign-in and sign-out. Payment in progress: until the order is paid or abandoned, unpaid lines then returning to the cart |
Pending licence purchase (questovery:on-prem-operating-license-acquisition) |
Resuming, after you sign up or sign in, the licence purchase chosen before you were signed in: ordered lines, category, name of the organization to create, acceptance of the terms and time of the choice, operation identifiers | Until the payment page opens or until you choose "Abandon this attempt". After twenty-four (24) hours, the purchase is no longer resumed automatically: you are only offered to abandon it |
| Resumption keys for other payment flows | Resuming a payment in progress without creating a duplicate | Until the tab is closed |
| Reload keys after an update | Preventing a reload loop after a new version | Until the tab is closed |
These items are necessary for the website to operate or for the service you request, in particular keeping your cart and resuming your purchase; they are not subject to your consent and are not used for any audience measurement or advertising purpose.
2.3 Error diagnostics
The website sends the technical errors encountered to the PostHog EU Cloud diagnostic service, without cookies, without storage on your device, without identifying your account and without geolocation based on your IP address.
2.4 Third-party resources
The website's fonts are hosted with the Application and are not loaded from any third-party service. To display certain pages, your browser loads resources from third-party services, which receive your IP address and your browser's technical information on that occasion:
- the map backgrounds, loaded from the OpenStreetMap tile servers
- the payment pages, hosted by Stripe, which uses its own cookies under its policy
3. Mobile application
3.1 Storage on the device
The mobile application stores on your device the information required for it to operate:
- in the system's secure storage: your sign-in session, the local storage encryption key, your choice regarding audience measurement and any postponement of an optional update
- in the application's local storage, part of which is encrypted: the game and trail tracking in progress, the language, a cache of loaded data kept for seven (7) days at most, the game log that allows playing offline, the upload queues for media and trail points, your choices regarding trail history and photos together with a random device identifier, the active organization and your preferences
- in the application's files: the media cache, copies awaiting upload and export archives, deleted after they are shared
These items are necessary for the service you request and are not subject to your consent.
3.2 Software development kits
| SDK | Purpose | Consent |
|---|---|---|
| PostHog, diagnostics | Sending application errors and crashes, with an anonymous identifier kept in memory and renewed at each launch, without geolocation | Not required |
| PostHog, audience measurement, where enabled by the Publisher | Measuring use of the application: screens, game events, device characteristics and, once signed in, account identifier; without geolocation based on the IP address | Required: no audience measurement event is transmitted and no identification takes place before your agreement or after your refusal |
| Expo Updates | Checking for and installing application updates, with a technical identifier generated by the SDK | Not required |
| Cloudflare Turnstile | Anti-bot check at sign-up and sign-in: Cloudflare receives the IP address and technical information about the browser embedded in the application, in order to prevent abuse | Not required |
| Apple Maps or Google Maps | Displaying maps | Not required |
| System age range | Limiting certain features where the operating system requires it; the age range stays on the device | Request handled by the system |
| App store review request | Offering to rate the application, through the system interface | Not required |
The mobile application uses no advertising identifier, no advertising tracker and no push notifications.
4. Managing your choices
4.1 Where audience measurement is enabled in the mobile application, your agreement is requested after a first action in the application. You may accept or refuse; refusing has no consequence on the use of the application. To accept, you confirm that you are fifteen (15) or older, or that a holder of parental authority consents with you. If you close the request without choosing, it is presented to you again later.
4.2 You may withdraw your agreement or change your choice at any time from the mobile application's settings. Withdrawing is as simple as accepting and has no consequence on the use of the application.
4.3 When you are signed in to your account, each choice regarding audience measurement is recorded on the Application's servers together with the text displayed, its version, the age confirmation, the language and the date, in order to keep proof of it.
4.4 You may also configure your browser to block or delete cookies, and manage the mobile application's permissions in your device settings. Blocking necessary cookies and storage may prevent sign-in or certain features.
5. Retention periods
The lifetimes of the website cookies are set out in article 2. Items stored by the mobile application are kept for the time required for their purpose; the application's local storage and files are deleted when it is uninstalled. Audience measurement data is kept for a target period of thirteen (13) months at most, and diagnostic data for a limited period defined by the diagnostic service's settings.
6. Contact
For any question about the use of cookies and trackers, you may contact the Publisher at [email protected].