The controller is Ilan CHALEF EI, 20 avenue Montclar, 06100 Nice, France, reachable at contact@exploreriviera.com. We collect what it takes to run your journey and nothing beyond it: your name, your contact details, your route and, if you give it, your flight number. We never see your full card number, and the fare you are shown does not depend on any data about you.
1. Who is the controller
Ilan CHALEF EI, sole trader, 20 avenue Montclar, 06100 Nice, France. Business identifier (SIREN) 833 263 148. Trading as Explore Riviera.
For any question or request about your data: contact@exploreriviera.com, or by post to the address above.
No data protection officer is appointed. Neither the nature of the activity nor the volume of data processed makes an appointment mandatory. Your requests are handled directly by the controller.
2. What we collect
Identity and contact details. First name, last name, email address, telephone number with its international dialling code.
Journey data. Pick-up address, drop-off address, date, time, duration for an hourly hire, number of passengers, number and type of bags, vehicle class, options chosen.
Optional travel data. Flight or train number, the name for the meet-and-greet sign, whether an animal travels, child restraints needed, and any free-text request.
Payment data. Our provider tells us the status of the transaction, its amount, its date and a reference. We neither receive nor store your full card number, its expiry date or its security code: those are entered on Stripe’s own pages and never pass through this site.
Contact data outside a booking. The content of the quotation, contact, business account and partnership forms, and of exchanges by email or WhatsApp.
Technical data. IP address, request headers, pages viewed, timestamps. These sit in the server logs and serve site security.
We collect no special category data within the meaning of article 9 of the GDPR. Please do not put any in the free-text field: if you have an accessibility need, describe the practical requirement rather than the medical reason for it.
3. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Calculate a fare and show it to you | Steps taken at your request before contracting, GDPR article 6.1.b |
| Record and carry out your booking, reach you on the day | Performance of the contract, article 6.1.b |
| Take payment, handle a refund or a post-journey charge | Performance of the contract, article 6.1.b |
| Issue and keep your receipt, run the accounts | Legal obligation, article 6.1.c |
| Answer a quotation request | Steps taken at your request before contracting, article 6.1.b |
| Answer a contact, business account or partnership request | Legitimate interest, article 6.1.f, or pre-contractual steps where the request concerns a journey |
| Handle a complaint, establish or defend a legal claim | Legitimate interest, article 6.1.f |
| Protect the site against abuse: rate limiting, anti-spam, logs | Legitimate interest, article 6.1.f |
| Measure site audience, once that measurement is switched on | Consent, article 6.1.a and article 82 of French law no. 78-17 of 6 January 1978 |
The legitimate interest relied on is the security of the service, the defence of our rights and dealing with the requests you send us. You may object to it under section 10.
Why a quotation request is not a matter of consent. Asking your consent before replying would make a tick box the condition of something you have already asked us to do. Article 6.1.b of the General Data Protection Regulation covers performance of a contract, but equally “steps taken at the request of the data subject prior to entering into a contract”: a quotation request is the textbook case. The box on the form is therefore not the legal basis; it tells you what your details will be used for and adds no purpose of its own. Nothing on this basis is used for marketing, which would need separate consent that we do not collect.
4. What is required and what is not
The fields needed to perform the contract are required: name, email address, telephone number, addresses, date and time. Without them the booking cannot be recorded.
Everything else is optional: flight number, name on the sign, free-text request. The flight number does determine whether we can track your flight and absorb an airline delay. Without it, that tracking is impossible.
We make no service conditional on marketing consent, and we sell no data.
5. Recipients and processors
Your data is accessible to the controller and, for the journey concerned only, to the chauffeur carrying it out. A partner chauffeur receives only what he needs: your name, your telephone number, the addresses, the time and the options.
The following processors and recipients are involved.
| Provider | Role | Established in |
|---|---|---|
| Stripe Payments Europe, Limited, and Stripe, Inc. | Payment, card on file, refunds | Ireland and United States |
| Resend, Inc. | Sending confirmation and notification emails | United States, sending routed from Ireland |
| Vercel Inc. | Site hosting and server function execution | United States |
| IGN Géoplateforme, and api-adresse.data.gouv.fr | Address autocomplete in France | France |
| Photon, Komoot GmbH | Address autocomplete for Monaco, Italy and Switzerland | Germany |
| OpenRouteService, HeiGIT gGmbH | Route calculation outside the fare grid | Germany |
How the services operate. Automatic request and acknowledgement emails are delivered through Resend when the form sends them. A request is only described as received once delivery succeeds. If sending fails, the site offers phone and WhatsApp contact.
Online card payment is not open. A booking request remains subject to confirmation by the chauffeur. The form does not collect card details.
Google Analytics 4, which may be managed through Google Tag Manager, measures site activity only after your permission. It receives limited journey-through-the-site events, without customer contact details or journey addresses. See the cookie policy.
Address lookups and route calculations run on our server, not in your browser. Those mapping services therefore never see your IP address; they see our server’s.
Your data may also be disclosed to our accountant, to the French tax authorities and, on a valid order, to a competent judicial or administrative authority.
No data is sold, rented or exchanged for commercial purposes.
6. Transfers outside the European Union
Vercel and Resend are established in the United States. Google may also process measurement data outside the European Union after your permission. Each provider’s terms describe the applicable transfer safeguards, including standard contractual clauses where necessary. An email sending region does not guarantee exclusively European storage.
Google. No Google measurement script loads before you agree through the banner. Advertising features and automatic form measurement are disabled. Fonts are hosted on our own domain. See Google’s data processing terms and our cookie policy.
7. How long we keep data
| Data | Period | Counted from |
|---|---|---|
| Bookings and journey data | 3 years | Your most recent journey |
| Receipts and accounting records | 10 years | End of the financial year concerned |
| Quotation, contact and partnership requests that go nowhere | 3 years | Your last contact |
| Server logs | 6 months | Date of the request |
| Your choice about trackers | 6 months | Date of your choice |
| Payment data held by our provider | Per Stripe’s own policy | Transaction |
Keeping bookings for three years comfortably covers the two-year period within which a professional may bring a claim against a consumer under article L218-2 of the French code de la consommation, and leaves room for late complaints.
Keeping accounting records for ten years is imposed by article L123-22 of the code de commerce. The six-year tax period in article L102 B of the livre des procédures fiscales is absorbed by that longer period.
As at the update date shown at the top of this page, this site runs no booking database of its own: your booking data lives in the emails exchanged and with our payment provider.
8. Security
The site is served over HTTPS only. Security headers, including a content security policy, restrict what a page is allowed to load.
No card number passes through this site or our servers. No secret is stored in the code: credentials for third-party services are held in environment variables.
Endpoints that receive data are protected by strict validation, an anti-bot measure and a cap on the number of requests.
If a data breach is likely to result in a high risk to your rights, you will be informed under article 34 of the GDPR.
9. No profiling, no automated decisions
The fare is calculated automatically from the route, the date, the time, the number of passengers and bags, and the vehicle class.
That calculation uses no data about you: not your name, not your history, not your device, not your browser, not your location. It runs before you have entered a single contact detail.
There is therefore no profiling, no per-visitor pricing, and no solely automated decision producing legal effects concerning you within the meaning of article 22 of the GDPR. Two people asking for the same journey at the same moment see the same fare.
10. Your rights
Access. Confirm whether we process data about you, and obtain a copy. GDPR article 15.
Rectification. Have inaccurate data corrected or incomplete data completed. Article 16.
Erasure. Ask for your data to be deleted. Article 17. This does not extend to accounting records, which the law requires us to keep for ten years.
Restriction. Ask for processing to be frozen, in particular while the accuracy of contested data is checked. Article 18.
Portability. Receive the data you provided in a machine-readable format, to pass on to another controller. Article 20.
Objection. Object to processing based on our legitimate interest, on grounds relating to your particular situation. Article 21.
Withdrawing consent. Withdraw consent at any time, as easily as you gave it, without affecting the lawfulness of processing carried out beforehand. Article 7.3.
What happens to your data after your death. French law no. 78-17 of 6 January 1978 lets you set general or specific directions on this point. We apply them on proof that they exist.
11. How to exercise your rights
Write to contact@exploreriviera.com, or by post to Ilan CHALEF EI, 20 avenue Montclar, 06100 Nice, France.
State which right you are exercising and, if you have one, a booking reference. Proof of identity is requested only where there is reasonable doubt about who you are, and it is not retained.
We answer within one month of receiving the request. That may be extended by two months where the request is complex or where requests are numerous; you are told within the first month, with the reason.
Exercising these rights is free.
12. Complaining to the CNIL
If, after contacting us, you consider that your rights are not respected, you may lodge a complaint with the French data protection authority.
By post: Commission nationale de l’informatique et des libertés Service des plaintes 3 place de Fontenoy TSA 80715 75334 Paris Cedex 07 France
Online: https://www.cnil.fr/fr/plaintes
This route is open to you without prejudice to any court action.
13. Trackers and cookies
Trackers written to or read from your device, what they are for, how long they last and who sets them are listed on the Cookies page.
Audience measurement requires your prior permission. Advertising trackers are disabled. You can withdraw permission through Cookie settings in the footer.
14. Minors
The service is aimed at adults. A booking concerning a minor is made by an adult, who remains responsible for the information provided.
We do not knowingly collect data from a child under fifteen. If you find otherwise, write to us and the data will be deleted.
15. Changes
This policy may change, in particular when a new service is connected or a processor changes. The date of the last update appears at the top of the page.
Any substantial change, in particular adding a recipient or a purpose, will be flagged on the site before it takes effect.
The other legal pages