Privacy
Effective Date: December 3, 2026
Questovery Privacy Policy
Version 1.2 - effective as of December 3, 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 Privacy Policy describes how personal data is processed when using the www.questovery.com website, the web application, the Questovery mobile applications and related services (the "Application").
1. Who processes your data
1.1 LEZO. LEZO, publisher of Questovery, is the controller for its own processing: management of the website, accounts and authentication, security and abuse prevention, support, technical diagnostics, audience measurement, invoicing of its services, settlement of Publisher Commissions and historical fees, evidence of the acceptance of contractual documents, handling of content reports, compliance with its legal obligations and defense of its rights.
1.2 Customer organizations. The professional organizations that use Questovery to publish scenarios and operate quests (the "Customers") are controllers for the data processed in connection with their quests: teams, answers, scores, photos, positions, participant data, end-of-game feedback and, where they sell registrations, registration payments. For this processing, LEZO acts on behalf of the Customer, as processor. The Customer may provide you with its own additional information.
1.3 Independent providers. Stripe, Apple, Google and the other providers that determine their own purposes, in particular regarding payment, fraud prevention, app distribution or authentication, process certain data as separate controllers, under their own policies.
2. Contact
LEZO (EURL)
21 boulevard Auguste Pageot
44000 Nantes
France
- Support contact: [email protected]
- Personal data contact: [email protected]
3. Data processed
Depending on your use of the Application and the features enabled for a quest, the following categories of data may be processed:
- account data: email address, last name, first name, display name, language, avatar, email verification status, anonymous nature of a game session created without a named account
- authentication and security data: hashed password, Google identity where that sign-in is used, sign-in sessions with IP address, browser or device and expiry date, sign-in codes and links, invitations, result of the anti-bot check performed at sign-up and sign-in
- organization data: organization name and logo, an account's membership of an organization and role, invitations, recipients of end-of-game feedback emails
- seller identity declared by an organization that sells paid registrations: company name, legal form, registration, address, telephone, email address, name and website of the consumer mediator, cancellation conditions and, where applicable, the address of its own terms of sale
- participation data: team, team name and avatar, times, progress, answers, hints used, scores, aggregated distance traveled, rankings
- participant data requested by the organization operating the quest, among the fields it has chosen: first name, last name, email address, date of birth, postal code, telephone number
- end-of-game feedback
- route history, where you have accepted it: latitude, longitude, accuracy, altitude, heading, speed, timestamp and last position transmitted
- photos, videos, sounds and avatars submitted, with their file metadata
- evidence of your privacy choices: type of choice, decision, text displayed and its fingerprint, age confirmation sentence ticked, version of the audience measurement consent text, language, quest and team context, technical session and device identifiers, fingerprints of the IP address and browser
- evidence of acceptance of contractual documents: accepted document and its version, date, context of the acceptance (account creation, invitation to an organization, purchase of an operating license, order of a paid registration), reference of the relevant invitation, order or payment, account and organization, language, fingerprints of the IP address and browser
- billing data for LEZO's services: organization, Stripe customer identifier, billing email address, tax identifiers entered, subscription, credit purchases, payment references and, for in-app purchases in the mobile application, purchase receipts
- registration payment data, where the organization operating the quest sells registrations: the buyer's email address and language, participant data and related choices, payment identifiers and status, amount, any refund, confirmation email
- operating license data: orders, purchasing organization, payment references
- technical and diagnostic data: errors, crashes, technical logs, application version, device, system and browser type, IP address in server logs
- audience measurement data, described in article 4 and in the Cookie and Tracker Policy: pages and screens viewed, usage events, device characteristics, account identifier and organization. On the website as in the mobile application, no audience measurement event is sent before your agreement, nor after your refusal or the withdrawal of your agreement, and your account identifier is associated with these events only after your agreement
- support data: communications, attachments and, where you use the website chat while signed in, your email address and your organization's name
- data of the connector for artificial intelligence assistants, where an organizer connects one: authorized application, access tokens, consents and log of the actions performed, without the content of the exchanges
- content reports: name and email address of the person reporting, identifier of their account where they are signed in, type and reference of the reported content, reason, good-faith statement, handling status
- operating logs: administrative actions performed by LEZO, maintenance operations
No location is derived from your device's IP address for audience measurement and diagnostic events, whether they are sent from the website or from the mobile application. Error diagnostics are sent without an account identifier.
Some data is not collected directly from you: the email address and role indicated by an organization that invites you to join it, as well as the identifier, email address, its verification status and the name transmitted by Google where you use Google sign-in.
Providing an email address is necessary to create a named account and sign in to it; otherwise, the account cannot be created. It remains possible to take part in a quest from the mobile application with a game session without a named account. Where the organization operating the quest makes a participant data field mandatory, providing it is necessary to complete the relevant step, before registration or after end-of-game feedback; optional fields may be left empty. The data requested during a payment is necessary to complete the purchase. Route history and audience measurement are optional: refusing them does not prevent you from using the Application.
Bank card data is entered directly on Stripe's payment pages and is not processed by LEZO.
The Application does not collect push notification tokens, does not use an advertising identifier and does not include any artificial intelligence feature intended for participants.
4. Purposes and legal bases
4.1 Processing for which LEZO is controller
| Purpose | Main data | Legal basis |
|---|---|---|
| Provision of the Application and management of accounts and organizations | account, organization, participation | performance of the contract (general terms and conditions and terms of use) |
| Authentication, security and abuse prevention, including the anti-bot check | authentication, sessions, IP address, logs | LEZO's legitimate interest in securing the Application |
| Invoicing of LEZO's services, platform fees and accounting | billing, payment and order data | performance of the contract, legal obligation |
| Support and assistance | communications, data required for the request | legitimate interest, performance of the contract |
| Diagnosing and fixing errors | technical and diagnostic data | LEZO's legitimate interest in ensuring the stability and security of the Application |
| Audience measurement of the website and of the mobile application | audience measurement data, account identifier and organization | consent |
| Evidence of your audience measurement choices | evidence of your privacy choices | legal obligation to demonstrate consent |
| Evidence of the acceptance of contractual documents | evidence of acceptance | legitimate interest of LEZO and of the parties to the contracts concerned in retaining evidence of it |
| Presentation of the seller's identity before a paid registration is ordered | seller identity | performance of the contract (platform terms) |
| Connector for artificial intelligence assistants | connector data | performance of the contract |
| Handling reports of illegal content | content reports, reported content | legal obligation |
| Compliance with legal obligations and defense of rights | data required for each obligation or dispute | legal obligation, legitimate interest |
4.2 Processing carried out on behalf of Customers
| Purpose | Main data | Legal basis |
|---|---|---|
| Running the quest, results and rankings | participation, answers, proof photos, feedback | determined by the Customer |
| Route history and live tracking | route history, last position | consent |
| Publication of photos in the quest album | photos, publication decisions | consent |
| Collection of participant data | fields chosen by the Customer | consent, with retention of the text displayed |
| Sale and confirmation of registrations | registration payment data | performance of the sales contract concluded with the organization selling the registration, legal obligation |
5. Geolocation
5.1 With your device's permission, your position may be used to unlock a nearby step, validate a geolocated objective or guide you. This one-off use does not create any point in a history.
5.2 Where the organizer enables route history, the Application asks you separately for your agreement. Refusing does not prevent you from playing or from using one-off validations. Recording, including in the background, starts only after your agreement and the corresponding system permission, and is limited to the current game. Points are accepted only during the game window. During the game, the authorized organizer may see the last position transmitted.
5.3 You may withdraw your agreement in the Application: collection stops and points not yet transmitted are deleted from your device. Points already transmitted are retained under the conditions of article 11. A team member may delete the team's route history. You may also withdraw location permission in your device settings, which may make geolocated validations unavailable.
5.4 Route history is never displayed in rankings or in public links.
6. Photos and media
6.1 A photo sent during the game is private evidence visible to your team and to the authorized organizers.
6.2 It is visible to the other participants of the quest, in the album, only if publication has been accepted by a team member and no member objects. An objection removes the entire album publication, without deleting the private photos. Photos of test teams are never published.
6.3 A published photo may also be viewed by anyone holding the public ranking link, where the organizer has activated that link.
6.4 The optimized copy displayed in the Application does not include the camera's metadata, in particular location metadata. When it is processed, the original file of a photo in JPEG, PNG, WebP or TIFF format is stripped of its EXIF, XMP and IPTC metadata, including the GPS position; files in other formats are kept as submitted. Any team member may delete a photo of the team. A shared photo may be reported using the reporting form described in article 13.3.
6.5 A team member's agreement does not replace the authorizations applicable to other persons visible in a photo, in particular minors; obtaining them is the responsibility of the Customer responsible for the quest.
6.6 Photos are not subject to any biometric processing.
7. Payments
7.1 Subscriptions and credits for Questovery services are sold by LEZO and paid on Stripe-hosted pages. In the mobile application, individuals may buy their Personal creator subscription and credits through Apple or Google. RevenueCat receives purchase references, the stable technical account identifier and renewal or restoration events. LEZO verifies these events, retains receipts and acquired product rights and prevents double crediting.
7.2 Paid registrations are sold by the organization operating the quest and collected on its Stripe account. Operating licenses are sold and collected by the publisher. Any Publisher Commission is deducted and transferred in full through Stripe Connect, without any new LEZO remuneration on these registrations; historical payments keep their conditions. Refunds requested by the selling organization are executed by Stripe.
7.3 Before ordering a paid registration, you see the identity of the organization selling it, the contact details of its consumer mediator and its cancellation conditions, and you accept the applicable terms of sale. This acceptance is recorded with the reference of the terms accepted.
7.4 Stripe processes payment data under its own terms and privacy policy, in particular as controller for fraud prevention and compliance with its regulatory obligations.
8. Recipients
Your data may be accessible, to the extent necessary:
- to LEZO's authorized personnel
- to the authorized personnel of the Customer operating the quest in which you take part, for that quest's data
- to the organization that published the quest's scenario, to the extent necessary to manage the license
- to buyers of paid registrations, for the seller identity of the organization selling the registration
- to the members of your team and the other participants of the quest, for the information required for the game, rankings and albums
- to anyone holding the public ranking link, where the organizer has activated it, for team names, scores and published photos
- to the providers listed in article 9
- to administrative or judicial authorities, where required by law
Your data is not sold.
9. Service providers
| Category | Provider | Data location |
|---|---|---|
| Hosting of the application, database and media | OVHcloud (OVH SAS) | France |
| External copy of backups, where this service is enabled | Scaleway | France |
| Sending transactional emails | Amazon Web Services (Amazon SES) | European Union (Paris region) |
| Audience measurement and error diagnostics | PostHog (PostHog EU Cloud) | European Union |
| Website support chat, loaded only at your request | Crisp | Under the provider's terms |
| Anti-bot check at sign-up and sign-in | Cloudflare (Turnstile) | United States |
| Payment | Stripe | Under its terms |
| Subscription and credit verification; administration of store products | RevenueCat | United States |
| Distribution and updates of the mobile application | Expo (650 Industries) | United States |
| App stores | Apple, Google | Under their terms |
| Sign-in with a Google account, where used | Under its terms | |
| Mapping | OpenStreetMap Foundation on the web; Apple Maps or Google Maps on mobile depending on the device | United Kingdom; under the provider's terms |
For audience measurement and error diagnostics, LEZO is the controller and PostHog acts as LEZO's processor.
The anti-bot check transmits your IP address and technical information about your browser or the application to Cloudflare. Loading maps transmits your device's IP address to the relevant provider. The website fonts are hosted by LEZO, without any call to a third-party service. The Crisp support chat is loaded only when you click the chat button.
10. Transfers outside the European Union
The hosting of the Application, database and media is operated in France.
Some providers are established outside the European Union or belong to groups established outside the European Union, in particular in the United States and the United Kingdom, and may access or process data from those countries. Where safeguards are required by applicable regulations, LEZO implements appropriate safeguards or relies on those provided by the relevant provider, in particular an adequacy decision of the European Commission or standard contractual clauses. You may obtain information on these safeguards by contacting LEZO.
11. Retention periods
| Category | Period |
|---|---|
| Account | Duration of the account, until it is deleted at your request. An account that has taken part in at least one game, including a game account without an email address, is deleted automatically when it is a member of no organization, has no ongoing sign-in session and has not been modified for twenty-four (24) months; its game history is then dissociated. |
| Sign-in sessions | Validity of seven (7) rolling days; deleted upon sign-out and with the account. Expired sessions are deleted thirty (30) days after their expiry. |
| Invitations to join an organization | Unaccepted invitation: ninety (90) days after its expiry; accepted invitation: duration of the organization. Invitations received or sent are deleted with the account. |
| Participation, answers, scores and rankings | Duration of the quest's operation and of its history, and at the latest until the Customer's data is deleted after the end of its contract. If your account is deleted, the history is dissociated from the account. |
| Test teams | Six (6) hours after their creation |
| Route history | Twelve (12) months at most after each point is recorded; earlier deletion where a team member deletes it, where the team or the quest is deleted, or where no account remains linked to the team. Aggregated distance, scores and progress are retained. |
| Album photos not linked to an answer | Twelve (12) months after their creation, unless deleted earlier; the file is deleted and the metadata is retained |
| Photos submitted in answer to a challenge | As long as the answer exists; deletion by a team member or with the team or the quest |
| Participant data | Duration of the participation; deleted with the account or with the team or the quest, subject to data associated with a registration payment |
| Evidence of your privacy choices | Duration of the participation or of the account to which it relates; dissociated from the account if the account is deleted, then deleted five (5) years after the decision once it is no longer linked to any account or participant |
| Evidence of acceptance of contractual documents | Duration of the account or organization to which it relates; dissociated from the account and the organization upon their deletion, then deleted five (5) years after the acceptance once it is no longer linked to any account or organization |
| Seller identity | Duration of the organization; deleted with it |
| Content reports | Two (2) years after receipt for a closed report, and at the latest three (3) years after receipt; the account of the person reporting is dissociated from it upon deletion of that account |
| End-of-game feedback | Duration of the quest's operation |
| Invoicing, registration payments and license orders | Duration of the contractual relationship, then ten (10) years for accounting records |
| Game synchronization data | Seven (7) days for the change log; lifetime of the team for acknowledgements |
| Technical diagnostics | Fourteen (14) days for technical logs and traces sent to the diagnostic service; for errors and crashes, the period provided for by the plan subscribed with that service |
| Audience measurement | Target period of thirteen (13) months at most |
| Support | Time required to handle the request, then twenty-four (24) months after closure or the last exchange; up to five (5) years in the event of a dispute or claim |
| Maintenance task logs | Thirty (30) days |
| Log of administrative actions performed by LEZO | Five (5) years |
| Connector for artificial intelligence assistants | Authorized application, access tokens and consents: duration of the account or of the application's authorization. Log of the actions performed: one (1) year; it is deleted earlier with the user's account or with the relevant authorized application |
| Application and security logs | Target periods of six (6) months for application logs and twelve (12) months for security logs, except in the event of an incident or need for evidence |
| Data subject requests | Five (5) years at most, except in the event of litigation |
| Backups | Rotation over thirty (30) rolling days, and ninety (90) days at most; a backup is not used to reactivate deleted data, except for a restoration required after an incident |
Data dissociated from a deleted account continues to be treated as pseudonymized data as long as a team, date, location or organizer makes it possible to link it to a person.
Where LEZO processes data on behalf of a Customer, certain periods may depend on that Customer's choices or on the applicable contract. At the end of a Customer's contract, its data is in principle deleted or anonymized within thirty (30) days, subject to temporary backups, legal obligations, evidence needs and data linked to a commercial history shared with another Customer.
12. Security
LEZO implements reasonable technical and organizational measures intended to protect personal data, in particular access control, encryption in transit, logging, monitoring, restriction of access to authorized persons, backups or security procedures appropriate to the service.
No online service can guarantee absolute security. In the event of an incident affecting personal data, LEZO takes the necessary measures in accordance with applicable regulations and, where LEZO acts as processor, informs the relevant Customer under the agreed conditions.
13. Your rights
13.1 Under the conditions set out in regulations, you have the rights of access, rectification, erasure, restriction, objection and portability, as well as the right to withdraw your consent at any time where processing is based on it and to set instructions regarding the handling of your data after your death.
13.2 Where processing is based on LEZO's legitimate interest, in particular security, support and error diagnostics, you may object to it at any time, on grounds relating to your particular situation, by writing to [email protected]. LEZO then stops the processing, unless there are compelling legitimate grounds that override your interests, rights and freedoms, or for the establishment, exercise or defense of legal claims.
13.3 From the Application, you may:
- obtain an export of your personal data as an archive, from your account settings in the mobile application or on the website; the archive is downloadable through a link valid for one (1) hour
- modify your profile information, your email address and your password
- delete your account from your account settings, in the mobile application or on the website, where you have a named account; the procedure is described on the page www.questovery.com/en/account-deletion
- withdraw your agreement to audience measurement, through the “Manage cookies” link on the website or from the mobile application settings
- withdraw your agreement to route history and delete your team's history
- object to the publication of your team's album
- delete a photo of your team
- report content using the reporting form available at www.questovery.com/en/report
13.4 Deleting your account dissociates your game history from the deleted account where that history must be retained for rankings, results and evidence of consent. Deletion may be refused as long as your account is the last owner of an organization shared with other members or is linked to a commercial history that must be retained; it is then up to you to designate another owner or to write to support.
13.5 To obtain a copy of data not included in the export, for a portability request, to delete a game session without a named account, to withdraw an agreement to the collection of participant data, or for any other request, write to [email protected]. You will receive a response within one (1) month, which may be extended under the conditions set out in regulations. You may be asked to verify your identity, in particular by means of a code sent to your account's email address.
13.6 Where your request concerns data processed on behalf of a Customer, you may address it to that Customer or to LEZO, which forwards it and assists the Customer in responding.
13.7 You may lodge a complaint with the Commission nationale de l'informatique et des libertés (CNIL) or with the supervisory authority of your place of residence.
14. Minors
14.1 Questovery may be used autonomously from the age of thirteen (13). A minor under thirteen may take part in a quest only in a setting organized by an adult, in particular a Customer or an organizer, under that adult's responsibility and with the authorization of their legal representatives.
14.2 Where processing is based on consent, in particular route history, photo publication, the collection of participant data or audience measurement, the consent of a minor under fifteen must be given jointly with the holder or holders of parental authority. In the mobile application, each consent request therefore includes the box “I am 15 or older, or a holder of parental authority consents with me”; consent can be given only after ticking this box and, otherwise, the choice counts as a refusal. For the use of photos, route history and participant data, the ticked sentence is kept with the proof of consent. The Customer is responsible for age-appropriate information, obtaining the legal representatives' authorizations, in particular for minors' image, and the choice of features enabled for a minor audience, in particular route history, photo publication and public rankings. Legal representatives may ask support to withdraw an agreement given by a minor.
14.3 On mobile, where the operating system requires it or provides an age range indication, the Application may read the age range provided by the system in order to limit access to certain features. This information stays on the device; it is neither stored nor transmitted to LEZO or to measurement tools. Questovery does not perform any other age verification.
15. Cookies and trackers
The use of cookies, local storage and software development kits in the Application, as well as how to change your choices, is described in the Questovery Cookie and Tracker Policy.
16. Changes to the policy
We may amend this Privacy Policy to reflect legal, technical, functional or contractual developments. The version in force is the one published in the Application. In the event of a substantial change, LEZO informs you by appropriate means.