A booking creates a record about at least two people — the passenger travelling and the driver carrying them. This section sets out what is held, who can see which part of it, how it is protected and what you can ask us to do about it.
The documents
- Privacy and data protection — the full policy: what is collected, the lawful basis for each purpose, who it is shared with, retention periods and your rights.
- Cookie policy — what is stored in your browser and what it does.
Who sees what
Access is deliberately asymmetric, because the two sides of a journey do not need the same information about each other.
| Who | Receives | Does not receive |
|---|---|---|
| Your driver | Your name, phone number, pickup and destination | Your email address, payment details or booking history |
| You, the passenger | The driver's name, photograph, rating and the vehicle's registration | The driver's address, licence number or personal documents |
| The operator | The journey details needed to fulfil the booking | Any right to reuse that data for marketing or to pass it on |
Card details
We do not store your card number. Card payments are taken on a hosted Stripe checkout page — a PCI-DSS Level 1 certified processor — and your card details are entered on Stripe's page, never transmitted through or stored on our systems. We receive confirmation that a payment succeeded, plus the last four digits and card type for your receipt.
We will never ask you for a card number, a PIN or a one-time password in order to process a refund. Anyone who does is not us.
How it is protected
- All traffic is encrypted in transit; the site refuses unencrypted connections.
- Passwords are stored hashed, never in readable form. Nobody here can look up your password.
- Database credentials live in a managed secret store, not in application code.
- Access is role-based — staff see only what their role requires, and administrative actions are logged.
- Driver and vehicle documents are stored outside the public web root and served only to those entitled to see them.
- Payment card data never touches our systems.
How long it is kept
| Record | Retained | Why |
|---|---|---|
| Booking records | 7 years | Accounting and tax obligations |
| Driver verification documents | While listed, then 2 years | Proof of the checks made |
| Complaints and safety reports | 3 years from resolution | Patterns matter in safety cases |
| Marketing consent | Until withdrawn | Consent is the basis |
| Technical logs | 12 months | Security and fault diagnosis |
Your rights
You can ask us to give you a copy of your data, correct it, delete it, restrict what we do with it, or object to a particular use — and you can withdraw marketing consent whenever you like. Ask through the contact form. We respond within 30 days and do not charge for it.
Some records we must keep even if you ask us to delete them; completed bookings inside the 7-year accounting window are the usual case. Where that applies we say so and explain why rather than quietly ignoring the request.
If something goes wrong
No system is perfectly secure. If a breach occurs that is likely to affect your rights, we will tell you and the relevant authority without undue delay — and we will tell you what actually happened rather than issue a statement that says nothing.
Getting in touch
Data requests and questions go through the contact form, choosing the category that fits. It gives your request a reference and a record of what you sent, which a mailbox does not.