2. Data we process and why
a) Website visit
When you visit our website, technically required connection data is processed so that the website can be delivered
to your device and operated securely. This may include your IP address, date and time of access, requested URL,
referrer URL, browser type and version, and operating system.
The purpose is to provide the website, ensure a stable connection and evaluate system security and stability.
The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is the secure and technically reliable provision of
our online offering.
b) Contact via WhatsApp
Our website offers links that let you contact us via WhatsApp. If you click one of these links, you are redirected
to WhatsApp. Personal data such as your phone number, name, profile information and message contents may be
transmitted to WhatsApp Ireland Limited and Meta Platforms. We do not control WhatsApp's or Meta's processing.
WhatsApp's privacy information is available at
https://www.whatsapp.com/legal/privacy-policy-eea.
The legal basis for processing in connection with your enquiry is Art. 6(1)(b) GDPR where the contact relates to
pre-contractual or contractual matters.
c) Contact by phone
If you call us, we process the information you provide, such as your name, phone number and enquiry, only to handle
your request and contact you about it. The legal basis is Art. 6(1)(b) GDPR where your enquiry relates to a
contract or pre-contractual steps, and otherwise Art. 6(1)(f) GDPR.
If you use our online ride request form, we process the details you enter to handle your request and contact you
about it. This may include pickup location, destination or booking duration, pickup date and time, return-trip
details, selected vehicle class, phone number and email address.
The form data is sent to our technical form endpoint based on Cloudflare Workers and then delivered to us by email
through Resend. The legal basis is Art. 6(1)(b) GDPR because the processing is necessary to take pre-contractual
steps and handle your ride request.
If you consent to Marketing, we also use your email address and phone number in hashed form for Google Ads
conversion measurement. See section 7 for details.
e) Google Maps Platform in the booking process
FRALIMO treats Google Maps Platform functions as technically necessary for the booking experience you request.
They therefore remain active regardless of your Statistics or Marketing choices and are technically separate
from optional measurement through Google Analytics 4 and Google Ads.
When you enter an address in the ride request, your browser sends the address text you entered to the FRALIMO
Cloudflare Worker. The Worker sends the information required for the relevant request to the Google Places API
and Google Routes API. This may include the origin, destination, place IDs, language settings and route-related
information.
These services are used for address suggestions, route calculation, distance and duration calculation, pricing
support and route visualisation. To display the selected route, the browser also loads a Google Maps Embed iframe.
This may cause your browser to communicate directly with Google.
The legal basis is Art. 6(1)(b) GDPR where the processing is necessary to handle your ride request and take
pre-contractual steps. Where technically necessary information is stored on or accessed from the terminal device,
we rely on Section 25(2)(2) TDDDG.
7. Cookies, similar storage technologies and consent manager
FRALIMO uses a first-party consent manager to store and apply your choices for necessary storage, statistics and
marketing performance measurement. Your selection is stored in localStorage under fralimo.consent.v1.
It contains only the schema version, necessary: true, your statistics and marketing choices, and saved
and expiry timestamps. The validity period is 180 days.
Necessary storage is used to provide the website and ride request process. This includes your privacy selection and
temporary sessionStorage under frankfurtLuxuryDrive.bookingEntry.v1 when ride details are passed into
the full ride request page. On the directly accessible request pages /buchen and
/en/book-a-ride, ride details are instead stored under fralimo.directBookingEntry.v1
to resume the request after a reload or language change.
If a full withdrawal of optional consent requires a page reload, an incomplete,
non-contact booking draft may be stored for no more than 30 minutes in sessionStorage under
fralimo.bookingDraft.v1, or fralimo.directBookingDraft.v1 on the direct request pages.
Phone numbers, email addresses and advertising click identifiers are not stored
in this draft. These necessary storage items are used only for the requested ride request process and to preserve
ride details already entered.
FRALIMO also treats the Google Maps Platform functions described in Section 2(e) as necessary for address
suggestions, route calculation, distance, duration, pricing support and map display. These map and route functions
are not controlled by the optional Statistics and Marketing categories.
If you consent to Statistics, we load the existing Google tag and use Google Analytics 4 to measure website usage,
page performance and ride-request funnel interactions. This includes events such as submitted ride requests, viewed
fare indications, phone clicks and WhatsApp clicks. The legal basis is your consent under Art. 6(1)(a) GDPR and
Section 25(1) TDDDG.
If you consent to Marketing, we use Google Ads conversion measurement to understand whether Google Ads lead to ride
requests, fare indications, phone clicks or WhatsApp clicks. sessionStorage under fralimo.adAttribution.v1
may be used for click identifiers such as gclid, gbraid or wbraid. Fare-indication event deduplication may be stored
under fralimo.fareQuoteViewed.v1 where the corresponding Statistics or Marketing consent exists. The
legal basis is your consent under Art. 6(1)(a) GDPR and Section 25(1) TDDDG.
Enhanced conversions: If you submit a ride request with Marketing consent, the Google tag sends
your email address and phone number to Google Ads together with the conversion. The details are hashed with SHA-256
in your browser before they are transmitted. Google matches these hashes against data from signed-in Google
accounts to attribute ride requests to ad clicks when cookies are not sufficient, and provides us only with
aggregated reports. We also send an estimated value of the request based on the displayed fare.
Import of confirmed bookings: If such a request becomes a booking, we usually send Google Ads,
once a week, the ad click identifier (gclid, gbraid or wbraid), the hashed email address and phone number, the time
the booking was confirmed and the fare. We do this only for requests that came from a Google ad and for which you
consented to Marketing. This tells Google Ads which ads lead to actual bookings.
The legal basis for both is your consent under Art. 6(1)(a) GDPR. The Google Ads Data Processing Terms apply, and
Google processes this data as our processor. Data may be transferred to the USA; Google LLC is certified under the
EU-U.S. Data Privacy Framework. If you withdraw Marketing consent in the cookie settings, the Google tag stops
sending data from that point on. To stop the import of a confirmed booking, an informal message to us is enough
(contact details in section 1); we will then not send your booking to Google Ads.
Before you make a choice, FRALIMO uses Google Consent Mode v2 with analytics_storage,
ad_storage, ad_user_data and ad_personalization set to “denied”. Statistics
consent grants only analytics_storage. Marketing consent grants ad_storage and
ad_user_data. ad_personalization remains denied because FRALIMO currently uses conversion
measurement, not remarketing or personalized advertising.
You can withdraw or change consent at any time through the “Cookie settings” button in the footer. On withdrawal,
Statistics-dependent analytics storage and, where technically possible for this domain, Analytics cookies such as
_ga, _gid and _gat are deleted when Statistics is withdrawn. Advertising
attribution storage and corresponding cookies such as _gcl_* and _gac_* are deleted when
Marketing is withdrawn. Necessary booking storage and Google Maps functions remain available without optional
Statistics or Marketing consent.
The provider of the Google services is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
Further information is available in Google's privacy policy:
https://policies.google.com/privacy?hl=en