Privacy, kept simple.

Who is responsible

I’m James Marengo, and I operate this website and chauffeur service as a UK sole trader. You can contact me about privacy at james@jamesmarengo.com.

Information I may handle

Depending on how you contact me and the journey you are considering, this may include your name, email address, mobile number, pickup and destination, date and time, planned stops, journey notes, airport or flight information, railway-arrival information, and anything else you choose to provide.

This does not mean that all of this information is permanently stored.

How information reaches me

You may provide information by emailing me, contacting me through WhatsApp, or using the journey-planning experience on this website.

When you submit the journey form, the journey and contact details are sent to me by email so I can review the request. A transactional email provider processes the messages needed to deliver the request to me and, where successful, send you an acknowledgement.

Submitting the form does not automatically confirm a booking. The website does not currently provide customer accounts or keep a dedicated booking database.

How I use information

I use relevant information only to respond to enquiries, discuss and check a requested journey, arrange the chauffeur service where appropriate, communicate about that service, protect the website and its services from abuse and disruption, and meet legitimate administrative or legal obligations where applicable. I do not use it for marketing.

Arranging a journey

Where a journey proceeds, relevant details may need to be provided to the licensed TfL private hire operator through whom the journey is arranged. I am a TfL-licensed private hire driver, not a licensed private hire operator.

Technical services

The website is hosted by Vercel. Google Maps Platform supports address suggestions, location verification and route planning. AeroDataBox, accessed through RapidAPI, supports the optional flight lookup. Resend processes transactional email used to deliver submitted journey requests and acknowledgements. These services may process the technical or journey-query information needed to provide their part of the experience.

Google’s handling of information is explained in the Google Privacy Policy.

Messages sent by email or WhatsApp are also handled by the communication service you choose to use.

Browser storage and journey recovery

The journey planner uses session storage in your browser tab to remember your progress. An editable draft can include your journey details, notes, arrival preferences and contact information. Drafts are checked for validity for up to 24 hours after their last save. You can clear an editable draft using Start over.

When a request is prepared for sending, the planner also saves a recovery record containing its reference, attempt identifier, preparation and expiry times, and an encrypted copy of the prepared request messages. It may also record that online retry is blocked. The editable draft may remain alongside this record. Encryption does not make the information anonymous.

Online delivery and retry are available for up to 12 hours after preparation, unless recovery is blocked or unavailable. Expired, invalid or blocked recovery records may remain in the tab to help prevent an uncertain request from being submitted again as a new request. Follow the recovery screen’s instructions and contact me if receipt is uncertain.

After receipt is confirmed, the planner saves a small receipt containing the reference, attempt identifier, receipt time and acknowledgement status. This restores the received screen and is checked for validity for up to 24 hours. The planner normally clears the draft and pending record after saving this receipt; browser-storage failures can prevent cleanup.

These validity periods are not timed deletion guarantees. Expired drafts and receipts are removed when checked, while protected recovery records may remain. Starting another journey or using an available recovery-clearing action removes the relevant records when cleanup succeeds. Session storage normally ends with the browser session, subject to browser recovery behaviour. Clearing browser storage does not cancel a request or delete an email already received.

The website does not include advertising tracking, behavioural analytics or marketing pixels. It uses only the browser storage and technical services needed for the current journey-planning experience.

Security and abuse prevention

The website processes technical request information to help prevent abuse, excessive provider use and disruption. Its application rate limits use pseudonymous identifiers derived from IP addresses, rather than email addresses or phone numbers. These identifiers and request counters are held in bounded server memory, with expired entries removed during later checks. They are lost when the server process ends.

Vercel also processes request information, including IP addresses, for hosting and firewall protection. A custom observation rule logs bursts of requests to selected journey-planning and flight-lookup endpoints without blocking them through that rule. Other application and platform protections may still limit abusive traffic. Vercel’s security records are separate from the application’s in-memory counters.

Sharing and retention

I do not sell customer information. I share it only where reasonably necessary with the licensed operator arranging a journey, technical providers needed to operate the website or service, or where a legal or regulatory requirement applies.

Information is kept only for as long as reasonably necessary for the enquiry or service and any legitimate administrative or legal requirements. A submitted request may remain in my business email as the operational record. No fixed retention period has been adopted.

Your rights

You can contact me to ask about personal information I hold about you, or to request access, correction or deletion where applicable. If you remain concerned, you can also contact the UK Information Commissioner’s Office.