1. Identity and contact information of the Data Controller
Within the meaning of Article 4(7) of the GDPR:
| Field | Information |
|---|---|
| Trade Name | Private Chauffeur Service in Bordeaux |
| Corporate Name | VTCBORDEAUX |
| Legal Form | Simplified Joint-Stock Company (SAS) |
| Share Capital | 100 € |
| President | Adrien Moreno |
| SIREN | 924 992 605 |
| SIRET (headquarters) | 924 992 605 00015 |
| RCS | Bordeaux Commercial Register |
| Intra-EU VAT Number | FR81 924 992 605 |
| APE / NAF Code | 4932Z — Passenger Transportation by Taxi and Private Chauffeur Services |
| Headquarters Address | 9 Quai des Mouettes, 33290 Parempuyre, France |
| Phone | +33 7 57 59 89 00 |
| Primary Email Address | contact@vtc-bordeaux-chauffeur.fr |
| Website | VTC Bordeaux Chauffeur website |
| GDPR Contact | contact@vtc-bordeaux-chauffeur.fr |
2. Personal Data Collected
We collect only the data that is strictly necessary for the provision of our services and the proper functioning of the Site. The principle of data minimization (Article 5(1)(c) of the GDPR) is applied.
2.1 Data Collected Through the Reservation/Contact Form
- Title (Mr./Ms.)
- Last Name and First Name
- Email address
- Phone number
- Pickup location (airport, train station, hotel, etc.)
- Destination Address
- Date and time of the race
- Number of passengers, quantity and type of baggage
- Preferred vehicle type (Eco, Sedan, Van, VIP Van)
- Requested options (child seat, welcome sign with name, pet, etc.)
- Free text / Special instructions
- Billing information (last name, first name, address, company name, and VAT number for business customers)
Every booking is always sent through two channels, including its source information: to /api/reservation, which forwards a copy to the fleet platform at app.vtc-bordeaux-chauffeur.com/api/site/demande, and to Web3Forms for the request email that serves as the authoritative record. A successful Web3Forms submission determines the confirmation shown on the website. The custom quote form uses Web3Forms directly, including source information.
2.2 Data Collected During Payment
Stripe is not loaded on the public website or when a reservation request is submitted. If you choose to pay online, you will receive a separate secure payment link, processed by Stripe Payments Europe Ltd (1 Grand Canal Street Lower, Dublin, Ireland).
The banking information entered on the Stripe payment page does not pass through the static website. VTCBORDEAUX receives the information necessary to track the transaction, including its status, amount, and reference number.
2.3 Data Collected via WhatsApp / Phone
If you contact us via WhatsApp or by phone:
- Phone number (visible in the interface or via the caller ID)
- Information Provided during the exchange (name, itinerary, date, etc.)
- WhatsApp chat history, stored within the app
2.4 Automatically Collected Data — Cookies and Trackers
2.4.1 Server Logs
- IP address (potentially pseudonymized)
- Browser type and version, operating system
- Pages Visited and Referrer URLs
- Date and time of the request
- Technical information required for the operation and security of the Site
2.4.2 Google Analytics 4 (GA4) and Microsoft Clarity — audience measurement
Google Analytics 4 (Google LLC, United States) and Microsoft Clarity load from the first page, including on your first visit, unless you have declined audience measurement. Declining disables them and deletes their known cookies accessible on the Site’s domain. GA4 can collect data via the cookies _ga and _ga_58028P09D8:
- GA4 client ID;
- Page views, events, interactions
- Source and acquisition channel (organic, referral, direct, social)
- Approximate geographic data (country, region, city — derived from the IP address)
- Time spent on the site and number of pages viewed
- Device information (category, brand, model)
The GA4 configuration requires IP addresses to be anonymized and limits the duration of cookies to 13 months. Opting out does not affect any functionality.
GA4 cookies _ga and _ga_58028P09D8 and Clarity cookies _clck and _clsk are stored on the Site’s domain. Clarity cookies CLID, ANONCHK, MR, MUID and SM are third-party cookies stored on Microsoft domains: the Site cannot delete them. To remove them, open your browser’s privacy settings, then its cookie and site data controls, find the relevant Microsoft domains (for example clarity.ms and bing.com) and delete their cookies and data. See also the instructions in our cookie policy.
2.4.3 Consent Options
The v3 banner has three independent switches: Google Analytics, Microsoft Clarity and Google Ads. All are off when you first open “Manage choices”; necessary services remain active. “Accept” enables all three. “Continue without accepting” and “Reject all” disable them. “Save choices” applies your selection. Turning Google Ads off counts as a refusal of advertising, even if Analytics or Clarity remains on.
Your choice is saved in localStorage under vtc-consentement: the three switches, the date of your choice and banner version 3. This storage is necessary to honor your preferences and lasts 365 days if you accept all, or 180 days for a refusal or a partial choice.
Clicking the backdrop or pressing Escape does not close the banner. Only saving a choice closes it. Since November 18, 2026, an old version 2 choice is requested again; an old refusal less than 180 days old keeps measurement disabled while awaiting a new choice. When your choice expires, the banner returns. It does not open automatically on the privacy and cookie policy pages in any of the three languages, so you can read them.
A second request when you book. If you have declined Google Ads, an optional checkbox, initially unchecked, repeats the two sentences from the banner followed by “Learn more”. That link opens the policy without checking the box. If you check it and submit your booking, your choice becomes “Accept”: Google Analytics, Microsoft Clarity and Google Ads are enabled, and the new consent is dated. If you submit without checking it, that refusal and its date are saved separately in localStorage, and the checkbox is not offered again in that browser for 180 days. It is not shown if you have no valid choice or have already accepted Google Ads.
You can change or withdraw your choice at any time through “Manage cookies” in the footer. The panel then displays your saved preferences. Advertising consent given in the banner is sent with a booking request together with the actual date of that choice.
Before you choose, operation is unchanged: GA4 and Microsoft Clarity load from the first visit unless a refusal is already saved. Once your choice is saved, each tool follows its own switch. Advertising always waits for consent. Declining a tool removes its known cookies accessible on the website’s domain; Microsoft third-party cookies must be removed through your browser settings.
2.4.4 Summary Table
| Cookie | Publisher | Purpose | Duration |
|---|---|---|---|
_ga |
Unique Visitor ID (Analytics) | 13 months, from the first visit unless declined | |
_ga_58028P09D8 |
GA4-Related Measurement Status | 13 months, from the first visit unless declined | |
_clck |
Microsoft Clarity | Keeps the visitor’s Clarity identifier and preferences for this site. | Not specified in the Microsoft documentation consulted |
_clsk |
Microsoft Clarity | Groups page views within one Clarity session. | Not specified in the Microsoft documentation consulted |
CLID |
Microsoft Clarity | Recognizes the earliest visit seen by Clarity across sites using it. | Not specified in the Microsoft documentation consulted |
ANONCHK |
Microsoft Clarity | Flags any MUID transfer to ANID; its value is 0 for Clarity, which does not use ANID. | Not specified in the Microsoft documentation consulted |
MR |
Microsoft Clarity | Indicates whether to refresh MUID. | Not specified in the Microsoft documentation consulted |
MUID |
Microsoft Clarity | Identifies a browser for Microsoft services, including measurement, advertising and operational uses. | Not specified in the Microsoft documentation consulted |
SM |
Microsoft Clarity | Synchronizes the MUID identifier between Microsoft domains. | Not specified in the Microsoft documentation consulted |
_gcl_au |
Google Ads conversion measurement and link to ad clicks, if set by the tag depending on the visit | 90 days by default according to Google's documentation, after approval | |
_gcl_aw |
Google Ads conversion measurement and link to ad clicks, if set by the tag depending on the visit | 90 days by default according to Google's documentation, after approval | |
_groas_oppref |
Groas | Stores the value of the oppref parameter, reserved for ads that we do not use; set only if this parameter is non-empty in the address |
90 days |
localStorage: vtc-consentement (not a cookie) |
Private Chauffeur Service in Bordeaux | State of the three Google Analytics, Microsoft Clarity and Google Ads switches, choice date and banner version 3 | 365 days if you accept all; 180 days for a refusal or a partial choice |
Separate refusal of the second request in localStorage: vtc-accord-pub-refus | VTC Bordeaux | Refusal and date; prevents offering the checkbox again | 180 days |
sessionStorage: vtc-provenance | VTC Bordeaux | Referring host, landing page and three UTM labels; no choice or advertising consent | Lifetime of the tab; cleared on advertising refusal |
sessionStorage: vtc-devis-envoi | VTC Bordeaux | Quote submission marker for the internal counter; set only without an advertising refusal | Lifetime of the tab; removed on quote confirmation |
sessionStorage: vtcReservationRecap | VTC Bordeaux | Departure, destination, date, vehicle, amount and recap reference for the confirmation page | Lifetime of the tab; removed as soon as the confirmation page reads it |
The Microsoft Clarity documentation describes these cookies’ purposes and first-party or third-party status, but not their lifetimes. Whether they are actually set depends on Clarity and browser settings. See our cookie policy for details.
2.4.5 Groas — adapting ad landing pages
Groas adapts the content of the landing pages for our Google Ads campaigns. Its script, served from app.groas.ai, loads on every page of the Site, regardless of the choice made in the cookie banner.
On every page view, Groas receives the technical data associated with any script request: IP address, browser information and page referrer information, as permitted by browser rules.
In our use, Groas changes the page content only if its address contains its content parameter groas (or landingpage, which the script also recognizes), as when visiting from an ad managed by Groas. That identifier is then sent to retrieve the adapted content, served from groas-backend.onrender.com.
Groas does not write to localStorage or sessionStorage and does not set cookies in our current use. There is one exception: whenever the address contains a non-empty oppref parameter, even without a groas parameter, the script sets the _groas_oppref cookie for 90 days. This parameter is reserved for ads that we do not use.
2.4.6 How you found the website
When you arrive from another website or a campaign link, we retain five pieces of information: the referring website’s host name (not its full address), your landing page (up to 80 characters), and the campaign labels utm_source, utm_medium and utm_campaign (up to 40 characters each). A direct visit adds no source parameter to links; only its landing page may be retained. These details accompany every booking and quote request, even without cookie consent or after a refusal.
They pass between pages in a site-specific parameter on internal links, which is removed from the address bar after it is read. With no choice or with advertising consent, they are also kept in sessionStorage under vtc-provenance for the lifetime of the tab. After an advertising refusal, that storage is cleared: the visit source is stored in neither cookies, localStorage nor sessionStorage; only the links and the current page’s memory carry it. Before the reload triggered by a refusal, the parameter is restored to the address, then read and removed on the next load, without browser storage. The necessary record of your choice is separate.
Our legitimate interest is to understand how travelers find us, for internal use. The source information stays with the booking for as long as the booking is kept, under the retention section; a quote’s source follows the request and, if booked, the booking. Neither the website nor our ride management software sends Google the source information attached to your booking or quote request. When active, Google Analytics separately measures the source of the visit, including the referring website, landing page and UTM labels (see section 2.4.2). The vtcpr relay parameter is removed from the page address and referrer used for that GA4 measurement. You can object to this internal use by email or WhatsApp.
Unless you have declined advertising, our internal counter without an identifier receives the contact type and source information when you click WhatsApp, phone or email, and when a quote or booking is successfully submitted, through /api/site/compteur. With your advertising consent, the source information also accompanies the WhatsApp reference sent to our relay at conversions.vtc-bordeaux-chauffeur.com/waref. The counter stops after a refusal; the source information accompanying the WhatsApp reference is not sent without advertising consent.
2.5 Data Collected in Connection with the Business Relationship
- Race History (dates, routes, amounts)
- Billing and Accounting Data
- Email Correspondence
- Claims and Potential Disputes
- Travel Preferences (for frequent travelers)
2.6 SMS Opt-in Data
All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
3. Purposes of Data Processing and Legal Bases
The following sections describe the purposes, stated grounds and operation of the processing activities.
3.1 Reservation Management and Contract Performance
| Element | Details |
|---|---|
| Purpose | Process your request, organize the trip, send you a quote and confirmation, and handle changes/cancellations |
| Legal Basis | Performance of a contract — Art. 6(1)(b) of the GDPR |
| Data | Identity, contact information, directions, options, payment information |
| Required field | Yes — without this information, the reservation cannot be processed |
3.2 Billing Management and Accounting Requirements
| Element | Details |
|---|---|
| Purpose | Issue invoices, maintain accounting records, and comply with tax obligations |
| Legal Basis | Legal obligation — Art. 6(1)(c) of the GDPR; General Tax Code and Commercial Code |
| Data | Identity, billing address, service amount |
| Required field | Yes — legal requirement |
3.3 Communication and Customer Relations
| Element | Details |
|---|---|
| Purpose | Responding to your requests for information, quotes, and complaints; communications related to your ride |
| Legal Basis | Performance of a contract (6(1)(b)) or legitimate interests (6(1)(f)) for pre-contractual requests |
| Data | Identity, email address, phone number, content of communications |
3.4 No Automated Prospecting
The Site does not offer a newsletter subscription or a checkbox for consent to receive marketing communications. The contact information entered in a form is used to respond to the request, arrange the service, and manage the corresponding customer relationship.
3.5 Audience Measurement (Google Analytics 4 and Microsoft Clarity)
| Element | Details |
|---|---|
| Purpose | Track page views, traffic sources, and user engagement to improve the Site |
| Grounds and operation | Interest pursued: understanding how the Site is used and improving it. GA4 and Microsoft Clarity load from the first visit unless you have declined audience measurement; declining disables them. This operation does not rely on prior consent. |
| Data | Anonymized browsing, cookie identifiers, device data/approximate geolocation |
| Rejection | No impact—the Site remains fully accessible |
3.6 Security and Fraud Prevention
| Element | Details |
|---|---|
| Purpose | Detect intrusions, DDoS attacks, and booking fraud |
| Legal Basis | Legitimate interest — Art. 6(1)(f) of the GDPR |
| Data | IP Addresses and Technical Request Logs |
3.7 Dispute and Litigation Management
| Element | Details |
|---|---|
| Purpose | Retain evidence in the event of a dispute, claim, or legal proceeding |
| Legal Basis | Legitimate interest (6(1)(f)) and legal obligation (6(1)(c)) |
| Data | Reservations, connections, payments |
3.8 Google Ads measurement
The website’s Google Ads tag is enabled only with your advertising consent: through “Accept”, a saved Google Ads switch set to on, or the second request checked when you submit a booking. When you submit a booking or quote request, it helps measure our ads using the ad click identifier if available and your email, hashed using SHA-256 before transmission to Google in a coded, unreadable form. The page address, previous page and measurement cookies may also be used. Your phone number is never sent to Google. The legal basis is consent. There is no targeted advertising or remarketing.
The import through our ride management software follows your most recent explicit choice, as of its actual date, wherever it was made: “yes” or refusal in the cookie banner, the checkbox on the booking form, your answer in the confirmation window before payment, or the link received by email or WhatsApp. We recognize the same customer by their email address or phone number. This choice applies to the booking concerned and to later bookings made without an explicit choice (via WhatsApp, email, phone or on the website without a choice), until you make a new choice. It never changes an earlier booking.
- With your consent, every booking it covers is transmitted, with or without an ad click: the click identifier if one exists, the amount, booking date, order identifier and your email hashed using SHA-256 before transmission. The legal basis is consent.
- If you have never made an explicit choice, for example for a first request via WhatsApp, email or phone, only bookings that originate from an ad click are transmitted, with the click identifier, amount, booking date and order identifier, without any identity information. The legal basis is our legitimate interest in measuring the effectiveness of our ads.
- If you refuse, no booking data is sent to Google until you give new consent. A “No” in the confirmation window before payment or on the page opened from the link received by email or WhatsApp counts as a refusal.
Your phone number is never sent to Google through any of these methods. These processing activities are optional and have no effect on your booking. They are used for neither marketing communications nor personalized advertising.
You can withdraw consent to the tag at any time through the “Manage cookies” link at the bottom of the page. You can also withdraw your consent to the import at any time, however you gave it (in the banner, through the checkbox on the booking form, in the confirmation window before payment or through the link received by email or WhatsApp), simply by sending a WhatsApp message to +33 7 57 59 89 00 or an email to contact@vtc-bordeaux-chauffeur.fr. This withdrawal has no effect on your booking. It does not affect data already sent. You can likewise object to transmission without identity information by WhatsApp or email, using the same contact details, under the right to object described in Section 7.6.
The recipient is Google (Google Ireland Limited and Google LLC, United States); the transfer is governed by the same safeguards as Google Analytics 4: SCCs + Data Privacy Framework (DPF) — Google DPF-Certified.
The Groas script loads on every page, regardless of the choice made in the banner. In our use, content adaptation depends on the content parameter in the address, as described in Section 2.4.5, along with the technical data sent on every page view and the _groas_oppref cookie exception. The rules in this Section 3.8 concern the Google Ads tag and conversion imports.
4. Retention Periods
In accordance with the principle of retention limit (Art. 5(1)(e) of the GDPR):
| Category | Active Duration | Interim Archiving | Foundation |
|---|---|---|---|
| Reservations / Contracts | Relationship duration + 3 years | 5 years | Civil Statute of Limitations (Art. 2224 of the Civil Code) |
| Billing / Accounting | 10 years (fiscal year-end) | — | Art. L. 123-22 of the Commercial Code; Art. L. 102 B of the Financial Programming Act |
| Server Logs | 13 months max | — | CNIL Recommendation |
Analytics Cookies (GA4: _ga, _ga_58028P09D8) |
13 months max | — | Duration configured on the Site |
Clarity first-party cookies (_clck, _clsk) |
Not specified in the Microsoft documentation consulted | — | Cookies accessible on the Site’s domain are deleted when declined |
Clarity third-party cookies (CLID, ANONCHK, MR, MUID, SM) |
Not specified in the Microsoft documentation consulted | — | Cookies on Microsoft domains; removable through browser settings |
Google Ads Cookies (_gcl_au, _gcl_aw) |
90 days by default, after approval | — | Default duration according to Google's documentation |
Groas cookie (_groas_oppref) |
90 days | — | Set only if the address contains a non-empty oppref parameter, reserved for ads that we do not use |
| Payment Information | Transaction + 13 months | 5 years (proof) | Time Limit for Filing an Objection |
| Raw banking data | Not retained | — | Entered only on the Stripe payment page |
| Correspondence | 3 years since the last exchange | — | Civil Statute of Limitations |
| Complaints / Disputes | Duration of proceedings + 5 years | — | Applicable Requirements |
| GDPR Requests | 5 years after closing | — | Evidence of Compliance with Obligations |
| Visit source (referring website, landing page and UTM labels) | As long as the booking it accompanies | — | Legitimate interest; source information attached to the booking used internally, without sending that source information to Google |
Upon expiration, the data is permanently deleted or irreversibly anonymized.
5. Recipients and Subcontractors
5.1 Authorized Internal Personnel
Adrien Moreno (President + driver) is the sole business recipient of the data, strictly within the scope of his responsibilities. The technical service providers listed below may access the data solely for the purposes of providing their services.
5.2 Technical Recipients
The technical service providers listed below process data only to the extent necessary to provide their services:
Cloudflare, Inc. — Cloudflare Pages
| Field | Details |
|---|---|
| Role | Hosting and Publishing of the Astro Static Website |
| Address | 101 Townsend St., San Francisco, CA 94107, USA |
| Data | IP address, requested URL and technical logs; the content of each booking, including its source and evidence of the advertising choice, passes through /api/reservation, a Cloudflare function on this website, to the fleet platform. Quote requests are sent directly to Web3Forms, without passing through that relay |
| Privacy policy | Cloudflare Privacy Policy and Cloudflare DPA |
| Location | Global network; Cloudflare states that it stores data primarily in the United States and the European Economic Area |
| Transfer | Guarantees described in the Cloudflare DPA, including standard contractual clauses and the Data Privacy Framework, depending on the transfer |
Cloudflare Web Analytics measures website traffic. Its script loads on every page, independently of the choice expressed in the banner; the banner switches do not control it.
Google LLC — Google Analytics 4
| Field | Details |
|---|---|
| Role | Audience measurement from the first visit unless you have declined it; declining disables GA4 |
| Address | 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA |
| Data | Pages viewed, traffic source, GA4 cookies, technical data, and approximate location |
| Privacy policy | Google Privacy Policy |
| GA Terms and Conditions | Google Analytics Terms of Use |
| Transfer | SCCs + Data Privacy Framework (DPF) — Google DPF-Certified |
Microsoft Ireland Operations Limited and Microsoft Corporation — Microsoft Clarity
| Field | Details |
|---|---|
| Role | Analysis of Site usage from the first visit unless you have declined it; declining disables Clarity |
| Status | Microsoft states in its FAQ that it acts as a data controller for Clarity |
| Data | Pages viewed, interactions (clicks, scrolling, mouse movements) and cookie identifiers |
| Policy | Microsoft Privacy Statement and Clarity privacy FAQ |
| Transfer | According to the Clarity FAQ, EU customers contract with Microsoft Ireland Operations Limited, whose transfers to Microsoft Corporation in the United States are covered by Standard Contractual Clauses (SCCs) |
Google Ireland Limited and Google LLC — Google Ads (conversion measurement)
| Field | Details |
|---|---|
| Role | Google Ads conversion measurement: tag after advertising consent through the banner or the second request when booking (consent); import according to the customer's most recent explicit choice (same email address or same phone number), as of its actual date, whether made in the banner, through the booking checkbox, in the window before payment or through the link received by email or WhatsApp, applying to the booking concerned and to later bookings made without an explicit choice, never to an earlier booking: with consent, every booking, with or without an ad click, with hashed email (consent); with no explicit choice ever made, import is limited to bookings originating from an ad click, without identity information (legitimate interest). On refusal, nothing is sent until new consent is given, including after a “No” in the window before payment or through the link. No personalized advertising or remarketing (see 3.8) |
| Data | Tag: page address, previous page, conversion measurement cookie; on submission of a booking or quote request, click identifier and email hashed using SHA-256 by Google before transmission. Import with consent: for every booking covered by the consent, the click identifier if one exists, the amount, booking date, order identifier and SHA-256-hashed email. If no explicit choice has ever been made: only bookings originating from an ad click, with the click identifier, amount, date and order identifier, without any identity information. No data on refusal until new consent is given. Never the phone number, through any method |
| Privacy policy | Google Privacy Policy |
| Transfer | SCCs + Data Privacy Framework (DPF) — Google DPF-Certified |
Groas — adapting ad landing pages
The script is supplied by app.groas.ai and the adapted content by groas-backend.onrender.com. Loading on every page and the technical data transmitted are described in Section 2.4.5.
Google LLC — Maps, Places, and Routes APIs
The estimation modules use Google Maps services to search for an address and calculate a route. Google receives the technical information from the request, as well as the addresses, location identifiers, or coordinates needed for the calculation. This functionality is separate from GA4. Google Privacy Policy.
DINUM — French Companies Search API
When you request invoicing to a company, the “Company name” field queries, from the third character typed, the public Companies Search API of the French Interministerial Digital Directorate (DINUM, France) to pre-fill the SIRET, VAT number and registered-office address. The API receives the text typed in that field and the technical information of the request (including the IP address). No cookie or access key, servers located in France; the data returned is that of the public companies register. Privacy policy of the Annuaire des entreprises.
Stripe Payments Europe Ltd
| Field | Details |
|---|---|
| Role | Payment is processed only when the Customer opens the Stripe payment link |
| Address | 1 Grand Canal Street Lower, Dublin, Ireland |
| Data | Bank information, amount, payer's identity |
| Privacy policy | Stripe Privacy Policy |
| Transfer | Depending on the safeguards and processing locations described by Stripe |
ETRANSPORTS / Nebulea — Main Booking API
| Field | Details |
|---|---|
| Role | Fleet platform that always receives a copy of each booking through the website’s /api/reservation relay to app.vtc-bordeaux-chauffeur.com/api/site/demande |
| Data | Identity, contact information, itinerary, schedules, passengers, options, and billing information entered in the form, visit source information and advertising choice evidence |
| Privacy policy | Nebulea Legal Notice |
Web3Creative / Web3Forms — Form API and email delivery
| Field | Details |
|---|---|
| Role | Receipt of every booking and custom quote, including source information, to send the request email. For bookings, this email serves as the authoritative record; the fleet platform receives a copy through a separate channel |
| Data | Fields from the submitted form and visit source information, without advertising choice evidence fields; IP address, and technical information necessary for submission and to combat spam |
| Supplier Retention | Web3Forms announces that submissions will be retained for up to three years, unless a shorter retention period applies based on the plan or the data is deleted earlier |
| Privacy policy | Web3Forms Privacy Policy |
5.3 Authorities and Legally Authorized Third Parties
Your data may be disclosed to the relevant authorities (judicial, administrative, tax) upon legal request.
5.4 Transfer of Business Operations
In the event of a total or partial sale of the business, your data may be transferred to the new owner, provided you are notified in advance.
6. Data Transfers Outside the EU
6.1 Legal Framework
Since the ruling Schrems II (CJEU, July 16, 2020), transfers to the United States are based on the Standard Contractual Clauses (SCCs) (EU Decision 2021/914).
The EU-U.S. Data Privacy Framework (DPF), adopted on July 10, 2023, allows certified U.S. companies to receive data from the EU.
6.2 Breakdown by Recipient
| Recipient | Country | Mechanism | DPF Certification |
|---|---|---|---|
| Cloudflare, Inc. | United States | SCCs + DPF depending on the transfer | Yes |
| Google LLC (GA4, Maps, Places, and Routes) | United States | SCCs + DPF | Yes |
| Google LLC (Google Ads: tag based on consent; import according to the customer's most recent explicit choice (same email address or same phone number), as of its actual date, whether made in the banner, through the checkbox, in the window before payment or through the link received by email or WhatsApp, applying to the booking concerned and to later bookings made without an explicit choice, never to an earlier booking: every booking, with or without an ad click, based on consent; only if no explicit choice has ever been made, import limited to bookings originating from an ad click, without identity information based on legitimate interest; nothing sent on refusal, including a “No” in the window or through the link, until new consent is given, as described in 3.8) | United States | SCCs + DPF | Yes |
| Microsoft Ireland Operations Limited / Microsoft Corporation (Clarity, data controller) | Ireland / United States | SCCs between the two entities, according to the Clarity FAQ | Not relied upon here |
| Web3Creative / Web3Forms | India + International Infrastructure | SCCs announced in the Web3Forms DPA | N/A |
| Stripe Payments Europe Ltd | Ireland + Stripe's infrastructure | Warranties Described by Stripe | Depending on the recipient |
| WhatsApp LLC (if you use the link) | United States + other countries | Warranties Described by WhatsApp | Depending on the recipient |
6.3 Your Rights
You can obtain a copy of the Standard Contractual Clauses (SCCs) by contacting us at contact@vtc-bordeaux-chauffeur.fr.
7. Your Rights
In accordance with Articles 15 through 22 of the GDPR, you have the following rights. Response time: 1 month (Extendable by 2 months for complex applications).
7.1 Right of Access (Art. 15)
Obtain confirmation that your personal data is being processed, and access that data and related information:
- Purposes, Categories of Data, Recipients
- Retention period
- Your Rights (Correction, Deletion, etc.)
- Right to File a Complaint with the CNIL
- Source of data in the case of indirect collection
- Existence of Automated Decision-Making
A copy is provided to you. Reasonable fees apply for additional copies.
7.2 Right to Rectification (Art. 16)
Have inaccurate or incomplete data corrected.
7.3 Right to Erasure / Right to Be Forgotten (Art. 17)
Deletion in the following cases:
- Additional data required
- Withdrawal of Consent (Without Another Legal Basis)
- Legitimate opposition
- Unlawful processing
- Legal Requirement
Exceptions : retention for legal compliance, legal defense, public interest.
7.4 Right to Restriction (Art. 18)
Temporary suspension of processing (verification of accuracy, unlawful processing, legal defense, verification of an objection).
7.5 Right to Data Portability (Art. 20)
Receive your data in a a structured, commonly used, machine-readable format (CSV, JSON) and transfer them to another data controller, if the processing is based on consent or a contract AND is automated.
7.6 Right to Object (Art. 21)
For processing based on legitimate interests : You may object for reasons related to your specific circumstances. We will cease processing your data unless there are compelling legitimate grounds to continue.
7.7 Right to Withdraw Consent (Art. 7(3))
At any time, without retroactive effect:
- Google Ads Cookies (
_gcl_au,_gcl_aw) : “Manage cookies” link at the bottom of the page - Other processing : contact@vtc-bordeaux-chauffeur.fr
You can also decline GA4 and Microsoft Clarity audience measurement through the “Manage cookies” link at the bottom of the page, even if you have never accepted it. Declining disables them.
7.8 Post-Mortem Guidelines (Art. 85 of the Data Protection Act)
Determine what will happen to your data after your death (retention, deletion, or transfer to a designated third party).
7.9 Exercise Procedure
By email : contact@vtc-bordeaux-chauffeur.fr By mail : VTCBORDEAUX — Attention: GDPR Officer — 9 Quai des Mouettes, 33290 Parempuyre, France
To be provided : - First and last name - Email address used for your interactions with us - Nature of the right exercised - Any relevant identifying information
Proof of Identity : We may ask for a copy of your ID (national ID card or passport)—which will be deleted after processing.
Deadline : 1 month (extendable to 2 months, with prior notice).
8. Right to File a Complaint with the CNIL
If your rights are not respected after you have contacted us, you may file a complaint with the CNIL :
| Field | Information |
|---|---|
| Address | 3 Place de Fontenoy — TSA 80715 — 75334 Paris Cedex 07 |
| Phone | +33 (0)1 53 73 22 22 |
| Website | CNIL Official Website |
| Form | File a complaint with the CNIL |
You can also contact the supervisory authority in your Member State of residence if you live in another EU country.
9. Data Security
In accordance with Article 32 of the GDPR, we implement the appropriate technical and organizational measures.
9.1 Technical Measures
- HTTPS : Encryption of communications with the Site and the APIs being called
- Static Hosting : The public website does not contain a customer database, and the forms are submitted to the APIs listed in Section 5
- Audience measurement choice: GA4 and Microsoft Clarity load from the first visit unless you have declined them; declining disables them
- Updates : software components kept up to date
9.2 Organizational Measures
- Less privilege : Data access is limited to those who need it
- Awareness : best practices for data protection
- Service Providers : Limited use of the services identified in this policy and review of their contractual guarantees
- Incident Management : In the event of a breach that could pose a risk, notification to the CNIL under 72 hours (Art. 33) and notification of affected individuals in cases of high risk (Art. 34)
9.3 Limitations
No system is completely foolproof. In the event of an incident, we will take all necessary measures to minimize its impact.
10. Cookies — Additional Information
Reference: CNIL recommendation on cookies and other trackers, official source verified on July 24, 2026.
10.1 What is a cookie?
A cookie is a small text file stored on your device when you visit a website. Among other things, it is used to remember a selection or an identifier.
10.2 Categories Used
Your choice is saved in localStorage under vtc-consentement: the three switches, the date of your choice and banner version 3. This storage is necessary to honor your preferences and lasts 365 days if you accept all, or 180 days for a refusal or a partial choice.
Audience measurement cookies: GA4 and Microsoft Clarity load from the first visit unless you have declined them; declining disables them. The GA4 cookies _ga and _ga_58028P09D8 are retained for no more than 13 months.
Google Ads conversion measurement cookies (subject to consent): _gcl_au and _gcl_aw, set by the Google Ads tag depending on the visit, after your advertising consent through the banner or the second request when booking, and retained for 90 days by default according to Google's documentation (see 3.8).
Groas exception: the _groas_oppref cookie is set for 90 days only if the address contains a non-empty oppref parameter, reserved for ads that we do not use (see 2.4.5).
10.3 Managing Preferences
Through our cookie banner : during your first visit. You can view this again at any time by clicking the “Manage cookies” link at the bottom of the page.
Through your browser : Chrome, Firefox, Safari, and Edge offer management options.
Disabling GA via an extension : Official Google Analytics opt-out tool.
For complete details, see our Cookie Policy.
11. Automated Decisions and Profiling
We do not make any fully automated decisions that have legal effects or significantly affect you, within the meaning of Article 22 of the GDPR.
GA4 data can generate aggregated and anonymous statistical profiles but are not used for automated individual decisions.
12. Data on Minors
Our services are intended for adults. We do not knowingly collect data from minors under the age of 15 without the consent of their legal guardians.
If you are a parent and believe your child has provided us with information without your consent, please contact contact@vtc-bordeaux-chauffeur.fr for immediate deletion.
13. Links to Third-Party Websites
Our Site contains links to third-party sites (social media, review platforms, etc.). We have no control over their data protection practices. We encourage you to review their privacy policies.
14. Changes
We may amend this policy to comply with regulatory changes or to reflect changes in our practices.
14.1 Notification Procedure
- Updated date shown at the top of the document
- Visible notice on the Site for a reasonable period of time
14.2 Archiving
Previous versions are archived and provided upon request.
14.3 Effective Date
Any changes take effect upon publication, unless otherwise specified.
15. GDPR Contact
| Medium | Contact Information |
|---|---|
| GDPR Email | contact@vtc-bordeaux-chauffeur.fr |
| VTCBORDEAUX — Attention: GDPR Officer — 9 Quai des Mouettes, 33290 Parempuyre, France | |
| Phone | +33 7 57 59 89 00 (urgent requests only) |
We are committed to processing your request within the required time frame.
This policy describes the personal data processed by VTCBORDEAUX and how to exercise your rights.
© 2026 VTCBORDEAUX (SAS, SIREN 924 992 605, RCS Bordeaux) — Bordeaux Chauffeur private chauffeur service — All rights reserved.
