Who we are
Cambridge City Taxi is the official app of Cambridge City Licensed Taxis, the Cambridge taxi federation for licensed hackney carriages. Kodfu Bilisim (“Kodfu”, “we”, “us”) builds and runs the app and this website on behalf of Cambridge City Licensed Taxis, and is the controller of the personal data described here.
Questions about your data: [email protected]. For help with the app, see Support.
The short version
- We collect what is needed to get a licensed taxi to you: your mobile number, your name and where to pick you up. For drivers, also the taxi’s position while on duty.
- The app takes no payments, so we never see card or bank details.
- No advertising, no tracking, no selling of data. The website uses one sign-in cookie.
- Passengers’ location is used only while the app or website is in use, never in the background.
- You can delete a passenger account at any time, in the app or on the website (how to delete your account).
What we collect
Everyone who signs in
- Mobile number. You sign in with a mobile number (from any country) and a 6-digit code we text to it.
- Name. Shown to the driver or passenger on a trip. Passengers can give just a first name.
- Email address, only if you add one, to receive trip records.
- Account details: when the account was created and last signed in, and its role (passenger, driver, taxi owner or office).
Passengers
- Calls: the pickup point (map position and place name or address), the destination if you give one, the fare estimate we showed, which driver accepted, the time of each step, and who cancelled and why.
- Trips: the taxi’s route during the trip, the distance, and the meter fare and payment method (card or cash) that the driver typed in.
- Ratings you give drivers: stars, tags and any comment.
- Reports: concerns and lost property reports you send, with their reference number.
- Messages to support and the details you give us in them.
People you call a taxi for
When you choose “Someone else”, you give us the rider’s name and mobile number (from any country). When a driver accepts, we text the rider once with the driver’s name, the taxi’s details and a link to follow it live, unless the person calling chooses not to. The driver sees the rider’s name and uses the number to call them about the pickup. We don’t use the rider’s number for anything else and we don’t create an account for them.
Drivers
- Name, mobile number, hackney carriage driver badge number, and the photo from the council licence (badge) record, added by the taxi owner or the office.
- Reference numbers and expiry dates of the driver’s badge and driving licence.
- Status (Available, Busy or Off duty) and when it changed; calls offered, accepted, declined or missed.
- The taxi’s position while on duty (see Location).
- Daily vehicle checks: each of the 16 items, any faults and notes, the mileage and the time.
- The driving log: trips from the app, rank and street-hail trips added by hand, meter fares, card or cash, and miles.
- Ratings from passengers, and the private ratings drivers give passengers.
Taxis and taxi owners
- Taxi: make and model, colour, registration, hackney plate number, seats, wheelchair access, whether it takes cards, and the reference numbers and expiry dates of its vehicle licence, MOT and insurance.
- Taxi owners: name, trading name, mobile number and email.
From your device
- Precise location, only as described under Location.
- Push notification token: an identifier from Apple or Google that lets us send notifications to your phone, with the platform (iPhone or Android) and the app version.
- Technical logs: IP address, browser or app version, the addresses requested (on the website these can include a pickup point you chose), times and errors. We use them to run and protect the service.
What we don’t collect
Card or bank details; your contacts (you type in a rider’s details yourself); health data; anything for advertising or analytics; taxi CCTV footage (the daily check only records whether the CCTV works). We don’t hold drivers’ DBS check results: those stay with Cambridge City Council.
Why we use it, and our lawful bases
- To provide the service you asked for (contract). Signing you in; sending your call to the nearest available taxi; showing you the driver, the taxi and where it is; keeping your trips; emailing a trip record when you ask. For drivers: calls, the daily vehicle check, the driving log and its CSV export.
- Safety, and preventing fraud and misuse (legitimate interests). Keeping trip records and the taxi’s route so a concern can be looked into; handling reports; private passenger ratings; showing daily checks and document expiry dates to taxi owners and the office; limiting how many sign-in codes can be requested; security logs.
- Running the taxi fleet (legitimate interests). Letting taxi owners and the office add drivers and taxis, see who is on duty, and deal with unanswered calls, faults and expiring documents.
- Calling a taxi for someone else (legitimate interests). Using the rider’s name and number so the driver can find them and they can follow the taxi.
- Keeping drivers’ records complete (legitimate interests). Keeping trip records, without the passenger’s details, after a passenger deletes their account, because they are part of the driver’s driving log and tax records.
- Improving the service (legitimate interests). Looking at totals such as unanswered calls and how long taxis take to arrive. We don’t build profiles of individual people.
- When the law requires it (legal obligation). Answering lawful requests from the police or from Cambridge City Council’s licensing team, and handling your data protection requests.
- Notifications (consent). We send push notifications only if you allow them on your phone. You can turn them off in your phone’s settings at any time; the app still works while it is open.
Where we rely on legitimate interests, we have weighed them against your interests and use only what is needed. You can object (see Your rights).
Some things happen automatically: a call goes to the nearest Available taxi first; a driver who misses 3 calls in a row is set to Busy and can go Available again straight away; and a failed safety item in today’s vehicle check stops a driver going Available until it is put right. None of these has a legal or similarly significant effect on anyone, and you can ask a person at the office or at Kodfu to look at any of them.
Who sees what
Drivers
For a call they are offered: the passenger’s first name (or the rider’s name), the pickup, and the destination and fare estimate if given. Never the passenger’s rating. Once they accept: the name on the account and a number to call. After the trip, the driver’s log keeps it with the passenger’s name.
Passengers
Before calling: the positions of Available taxis nearby, without names or plates. Once a driver accepts: the driver’s first name and last initial, the photo from their council licence record, badge number and average rating; the taxi’s make and model, colour, registration, hackney plate, seats, wheelchair access, whether it takes cards and when today’s vehicle check was done; the taxi’s live position until the trip ends; and a number to call the driver.
People with a trip link
A rider you called a taxi for, or anyone you share your trip with, sees the pickup and destination, the rider’s name, the driver’s name, photo and badge number, the taxi’s details and its live position. No phone numbers. The link stops working 24 hours after the trip ends.
Taxi owners
Owners see their own drivers and taxis: status and position while on duty, daily checks, documents and expiry dates, the calls and trips their drivers handled (pickup, destination, times and fares), ratings, and concerns reported about their drivers, without the name or number of the person who reported.
The Cambridge City Licensed Taxis office
The office sees the same for every driver and taxi. It can also see who made a report so it can follow it up, and when drivers have repeatedly flagged the same passenger (for example for no-shows), so it can deal with misuse.
Cambridge City Council and the police
Cambridge City Council licenses every hackney carriage driver and vehicle. When a report raises a safety or licensing issue, the office may share the report and the relevant trip details with the council’s taxi licensing team. We share data with the police or other authorities when the law requires it, or when it is needed to protect someone from serious harm.
Kodfu
A small number of Kodfu staff can access the systems to run, support and secure the service.
We never sell personal data and never share it for advertising.
Service providers
These companies process data for us, only on our instructions and under data processing terms:
| Provider | What they do for us |
|---|---|
| Hetzner Online GmbHGermany or Finland (EU) | Hosts our server and database. |
| Cloudflare, Inc.Global network, US company | Protects and delivers the website and the app’s connection to our server. Traffic passes through it, including IP addresses. |
| Twilio Inc.USA | Sends sign-in codes and the text to a rider when you call a taxi for someone else. |
| ResendUSA | Sends emails, such as a trip record you ask for. |
| Google (Firebase Cloud Messaging)USA | Delivers notifications to Android phones. |
| Apple (Apple Push Notification service)USA | Delivers notifications to iPhones. |
Map. The map is drawn from OpenStreetMap data, with map tiles from OpenFreeMap. Your app or browser fetches the tiles directly, so OpenFreeMap receives your IP address and which part of the map you are looking at, but no account details.
App stores. Apple and Google handle app downloads and updates under their own privacy policies.
International transfers
Our server is in the EU (Germany or Finland). UK law recognises the EU as giving adequate protection to personal data.
Twilio, Resend, Cloudflare, Google and Apple are US companies and may process data in the USA. Where a provider is certified under the UK Extension to the EU–US Data Privacy Framework (the “UK–US data bridge”), we rely on that. Otherwise we use the ICO’s International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses. Email us for details of the safeguard for a particular provider.
How long we keep it
| Information | How long we keep it |
|---|---|
| Your account: mobile number, name, email | Until you delete your account. They are removed straight away when you do. |
| Sign-in codes | Valid for 10 minutes. Stored only as a hash and deleted after they expire. |
| Sign-ins (sessions) | Up to 180 days in the app and on the website, 30 days on the taxi console, or until you sign out. |
| Push notification tokens | Until you sign out or delete your account, or Apple or Google tell us the token no longer works. |
| Record of notifications we sent | 90 days. |
| Calls and trips: pickup, destination, times, driver, fare, card or cash | 6 years after the end of the UK tax year in which the trip took place, because they are part of the driver’s driving log and tax records. If you delete your account, the trip is kept without your name, number or email. |
| A rider’s mobile number (calling for someone else) | 90 days after the trip, or straight away if the person who called the taxi deletes their account. |
| A rider’s name | With the trip (your trips show it as “for Margaret”). Removed if the person who called the taxi deletes their account. |
| A taxi’s live position | Only the latest position is kept. It is replaced every few seconds while the driver is on duty. |
| The taxi’s route during a trip | 90 days. |
| Trip links | Stop working 24 hours after the trip ends. |
| Ratings and tags | With the trip record. A written comment is removed if the passenger who wrote it deletes their account. |
| Concern and lost property reports | 6 years after the report is closed, in case they are needed for licensing, insurance or legal claims. |
| Daily vehicle checks and mileage | 2 years from the date of the check. |
| Driver and taxi records: badge photo, licence and vehicle documents, expiry dates | While the driver or taxi is registered with the app, then 12 months after removal. A driver’s name and badge number stay on trip records for as long as those are kept. |
| Driver status history (Available, Busy, Off duty) | 12 months. |
| Emails you send to support | 2 years after the conversation ends. |
| Server and security logs | Rotated automatically and deleted within 30 days. |
| Backups | Deleted data drops out of our backups within 30 days. |
| Your position when the app shows taxis near you | Not stored. |
Twilio, Resend, Apple and Google keep their own delivery records for limited periods under their terms with us. When a period ends we delete the data, or remove everything that identifies a person.
Your rights
Under UK data protection law you can:
- Access your data: ask for a copy.
- Correct it. You can change your name and email under Account. Drivers can ask their taxi owner or the office to correct their records.
- Erase it. Delete your passenger account yourself (how) or ask us. Some records are kept as explained above.
- Restrict how we use it while a question about it is sorted out.
- Object to uses based on legitimate interests.
- Take it with you (portability): the data you gave us, in a machine-readable format. Drivers can export their driving log as a CSV file at any time.
- Withdraw consent to notifications by turning them off in your phone’s settings.
- Ask for a person to review any automated decision.
To use any of these rights, email [email protected] with the mobile number on your account. To protect your account, we confirm the request through that number, usually by texting a code to it. It is free, and we reply within one month. If a request is complex we may need up to two more months, and we will tell you why.
Complaints
If you are unhappy with how we use your data, please tell us first so we can put it right. You can also complain to the Information Commissioner’s Office (ICO), the UK data protection regulator: ico.org.uk, telephone 0303 123 1113.
Children
Accounts are for people aged 13 and over. Teenagers aged 13 to 17 get the same high-privacy defaults as everyone else: location is used only while the app is open and during a trip, there is no advertising, no profiling and no selling of data. We don’t knowingly create accounts for children under 13, and we close any we find. A parent or another adult can call a taxi for a younger child using “Someone else”. We then hold the child’s name and mobile number as the rider, as described above.
Location
Passengers
The app and the website use your precise location only while you are using them, to set your pickup point and show taxis near you. Never in the background. Your phone or browser asks your permission first. If you say no, you can set the pickup on the map instead. The position used to show nearby taxis is not stored; the pickup point is saved with your call.
Drivers
While a driver is on duty (Available or Busy) or on a job, with the app in use, the app sends the taxi’s position every 5 seconds. It is used to offer calls to the nearest taxi, to show the passenger where their taxi is, and to show the taxi owner and the office who is on duty. It stops when the driver goes Off duty. We keep only the latest position, plus the route during a job for 90 days.
Cookies, advertising and payments
- The website sets one cookie,
cct_session, when you sign in. It is strictly necessary: it keeps you signed in. It is httpOnly (scripts on the page can’t read it), sent only over secure connections, and ends when you sign out or after at most 180 days (30 days on the taxi console). Because it is strictly necessary, we don’t ask for consent to it. - No analytics, advertising or tracking cookies, and no third-party cookies. The app contains no advertising or analytics tools and doesn’t use your phone’s advertising ID.
- No payment data: the app takes no payments. You pay the driver in the taxi.
- We don’t sell personal data.
Security
Every connection uses HTTPS. Sign-in codes and session tokens are stored only as hashes. A code expires after 10 minutes and can be tried only 5 times. Only taxi owners and the office can use the taxi console, and each owner sees only their own fleet. No system is perfectly secure: if a breach puts you at risk, we will tell you, and the ICO, as the law requires.
Keep your phone locked. Anyone who can read your text messages could ask for a code and sign in as you.
Changes to this notice
When we change this notice we update this page and the “Last updated” date. If a change makes a real difference to how we use your data, we will tell you in the app before it takes effect.
Contact us
Kodfu Bilisim, on behalf of Cambridge City Licensed Taxis.
Email: [email protected]