Privacy and transport request data

We use the smallest practical amount of data to prepare a request and follow service quality.

What is collected

General technical context such as page, route, language, device, and traffic source.
Random anonymous visitor and session IDs, visit timestamps, meaningful page actions, and approximate country, region, or city supplied by Cloudflare when available. New analytics records do not retain the visitor's raw IP address.
On a WhatsApp booking click: a random request reference, requested route, and request time.
An additional name or contact number is collected only when optional fields are enabled and the customer chooses to provide it.
Passenger Care opens only with a strong random token linked to the request.
When WhatsApp is confirmed, a frozen technical and journey snapshot is stored with the lead so later browsing does not change the original evidence.

What is excluded from general analytics

Names, phone numbers, detailed locations, and free-form trip notes are not sent to general analytics tools. Booking details remain in the protected lead flow.

Age and gender are never assigned to an individual visitor. If Google Analytics provides demographic data, it is shown only as thresholded aggregate audience statistics.

Google Analytics and Microsoft Clarity use consent controls. Clarity may provide anonymous recordings, heatmaps, scroll, rage-click, and dead-click analysis. Cloudflare Web Analytics supplies aggregate traffic and performance measurements.