Privacy Policy

Effective November 2, 2026

Who we are

Cabpin is a booking and dispatch service that local taxi companies use to take bookings by web and phone, send trips to their drivers and keep passengers informed. Cabpin is operated by Ratelsoft Inc. (“Cabpin”, “we”, “us”). This policy covers the Cabpin website (cabpin.com), each taxi company's booking and tracking pages (for example choice.cabpin.com), the dispatch console, the Cabpin Driver app and the Cabpin API.

Each taxi company that uses Cabpin (for example, Choice Taxi) runs its own service and is responsible for the trips it provides. For booking, trip and driver information, the taxi company decides how it is used and we handle it on the company's behalf. For information about our own website visitors and customers, such as demo requests, we decide how it is used.

We follow Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable provincial privacy laws.

What we collect

Passengers

• Booking details: your name, phone number, pickup and destination addresses, the service you choose (for example a ride, a delivery or a battery boost), any options you ask for (such as a wheelchair-accessible car) and any note for the driver. For a delivery, the recipient's name and phone number if you give them.
• Bookings made for you: when you phone a taxi company, its dispatcher enters the same details on your behalf. A company may also send bookings from its own systems, such as a hospital or hotel desk, through the Cabpin API.
• Your location, only if you choose it: if you tap “Use my location” on a booking page, your browser shares your position once to fill in the pickup address.
• Trip records: booking time, status changes, the assigned driver and vehicle, the trip's distance and time, and the fare.
• Text messages, only if you ask: if you tick “Text me updates about this booking”, the taxi company may send up to 3 texts to the mobile number you give, about that booking only: a confirmation with your tracking link, when your taxi has arrived, and when the company needs to call you to confirm the trip. We record when you agreed. Reply HELP for help or STOP to stop these texts; we record that and send no more to that number.
• Booking by text message: if you text a taxi company's Cabpin number, we keep the conversation (your number and the texts both ways), and an AI service reads it to work out your pickup, destination and name, look up the addresses and book the trip. It reads your past bookings with that company to recognise you. It asks before booking, and asks whether you want text updates about the trip. You can also ask it about your booking or to cancel it.
• Texts and calls together: with each taxi company, your texts and calls from the same number count as one conversation, so you can book by text and call about it, or the other way round. It remembers your name and the language you used last (English or French) and uses them next time, from that conversation (kept 30 days after your last text or call) or your latest booking. If it has your name wrong, reply with the right one (“My name is …”) and it updates it, on your booking too. Texts from a company that doesn't use this come from Cabpin's own number, and replies to them aren't read.
• Booking by phone call: if you call a taxi company's Cabpin number, an AI voice assistant answers. It tells you at the start that the call may be recorded. We keep your number, the places it looks up, the booking, and a recording and written transcript of the call, stored in Canada (Montréal). We keep recordings so we can look into a complaint, a dispute or an insurance claim about a trip, and only Cabpin can listen to them. The taxi company's dispatchers and admins can read the written transcript of your call, and your texts with its AI, for 30 days after, to sort out your booking; never the recording, and each time they open one is recorded. Like booking by text, it reads your past bookings with that company to recognise you, reads the trip back before booking, and asks whether you want text updates. If you'd rather not talk to an AI, ask for a person or call the company directly.
• Previous bookings: dispatchers can see a caller's earlier bookings with their own company, so they can fill in a returning caller's name and usual addresses.

Drivers (Cabpin Driver app)

• Account details: your mobile number (used to sign in with a text-message code), and your name and driver number as entered by your taxi company.
• Location while you are online: the app collects your precise location while you are on shift, including when the app is in the background or the screen is off, so dispatch can offer you nearby trips and passengers can see their taxi approaching. Location sharing stops when you go offline. We keep your latest position and, for each trip, the route you drove from accepting it to the drop-off (see How long we keep it). We don't keep a history of where you drive between trips.
• Trip measurements: the distance and time of each passenger trip, measured by your phone between “Passenger on board” and “End trip”, and the fare you enter.
• Shift and vehicle: which vehicle you drive and when your shift starts and ends.
• Device information: a push-notification token so we can alert you to new trip offers. It is removed when you sign out.

Taxi company staff

• Your name, email address and role, used to sign in to the dispatch console.
• Two-step sign-in: your authenticator app is linked to your account. We store what is needed to check your codes, not the codes themselves.
• Who took each phone booking, and which staff member created API keys or connections.

Taxi companies

• Company name, phone number, booking address, services, car features, vehicles and logo.
• Settings for integrations: API keys (stored only in a scrambled form we can check but not read back), webhook addresses and links to other dispatch software.

Website visitors

• Demo requests: if you ask for a demo, your name, email, phone number (if given), company, town, fleet size and message.
• Technical information: like most websites, our hosting records IP addresses and browser details in short-lived server logs. We use IP addresses, in scrambled form, to limit how many bookings or demo requests can be sent from one place, to stop abuse. When a page shows a map or looks up an address, we log the page, the IP address and (for staff and drivers) the account, to see where paid map services are used and to spot misuse.

How we use it

• To take bookings, offer trips to drivers, and show trip progress to passengers and dispatch.
• To let passengers, dispatch and drivers contact each other about a trip, including texts to passengers about their booking.
• To keep fare and trip records for the taxi company.
• To send account emails: setting a password, resetting it and confirming an email address.
• To answer demo requests and support emails.
• To improve fare estimates, using trip distance, time and fare without passenger names or phone numbers.
• To keep the service secure, prevent misuse and fix problems.

We collect only what the service needs. By booking, driving or signing in you agree to these uses; we will ask again before using information for anything new. We do not sell personal information and we do not use it for advertising. We never share mobile numbers, or your agreement to receive texts, with anyone for marketing or promotional purposes.

Who sees it

• The taxi company you book with or drive for sees its bookings, drivers, vehicles, trip records and fares. Other taxi companies on Cabpin cannot.
• Passengers see the assigned driver's first name, the vehicle and its location during their trip, through their private tracking link. Anyone you share that link with can see the same.
• Drivers see the passenger's name, phone number, pickup, destination and notes for trips offered to them or accepted by them.
• Systems the taxi company connects; see “Company integrations” below.
• Service providers that run parts of Cabpin for us, only to provide these services:
  • Google (Firebase and Google Cloud): hosting, database, sign-in, text-message codes and push notifications; Google Maps for address search and maps; reCAPTCHA to check that booking requests come from a real browser. Google's use of reCAPTCHA data is covered by the Google Privacy Policy.
  • Apple and Google: delivering push notifications to the driver app.
  • Resend: sending account and notification emails.
  • Twilio: text messages to and from passengers about their booking.
  • OpenAI: the AI that reads booking text messages and answers them. We ask it not to keep them.
  • ElevenLabs: the AI voice assistant that answers booking calls, with the AI model it runs on. It keeps its copy of a call's recording and transcript for 7 days.
• Authorities, where we are required to by law, or to protect someone's safety.
• A buyer or successor, if Ratelsoft's business is sold or merged, under the same protections as this policy.

Company integrations

A taxi company can connect Cabpin to its own software: its website, a booking desk, its own dashboard, or other dispatch software such as iCabbi or TaxiCaller. When it does, Cabpin sends that company's booking and trip details (including passenger names, phone numbers and addresses, the driver and vehicle, and fares) to the systems the company chooses, and may receive bookings and trip updates from them. Those systems are run by the company or by its own providers, under their privacy policies. Only the company's admins can set up these connections, and they see a log of what was sent.

Cookies and browser storage

Cabpin does not use advertising or analytics cookies. We use your browser's storage for:

• Keeping you signed in to the dispatch console.
• Remembering your name and phone number on a booking page, so you don't retype them next time. This stays on your device; clear your browser's site data to remove it.
• Remembering the tracking link of a booking you just made, for up to a day, so you can get back to it if you close the page while it's in progress.
• reCAPTCHA, which Google uses to tell people from automated traffic.

Where it's stored

Cabpin data is stored with Google Cloud in Montréal, Canada (northamerica-northeast1). Some service providers process information outside Canada, mainly in the United States, for example when sending text messages, notifications or emails, or answering booking calls. Information processed in another country may be accessed by that country's authorities under its laws.

How long we keep it

• Your name, phone number, exact addresses and notes on a booking: 2 years after the trip. Then they are removed and the tracking link stops working. The trip record stays, with the pickup and destination rounded to about 100 metres. The comment and call-back number on a rating are removed at the same time.
• Trip and fare records (time, service, car, driver, distance, fare, payment method, star rating): 7 years after the trip, as tax rules expect taxi companies to keep their records 6 years after the year they relate to. Then they are deleted, and only monthly totals per company are kept. Drivers' shift records are kept for the same 7 years.
• When a company leaves Cabpin: it has 90 days to download its records, and then we delete the company and all its data.
• Driver accounts: until the driver asks us to delete them (see Support). Their trips follow the trip rules above.
• A driver's location: the latest position is kept, and replaced each time the app updates it.
• The route of each trip (the driver's positions, direction and speed from accepting the trip to the drop-off): 30 days, so Cabpin can look into a problem a taxi company reports, such as where the taxi went or how it showed on the map. Only Cabpin staff can see it, apart from the part with the passenger on board, which the trip's tracking page shows on its map once the trip is over. It is deleted automatically after 30 days. The map itself is OpenStreetMap, served by Cabpin, so no other company sees who looks at it.
• Integration delivery logs: 30 days.
• Text-message conversations with a booking number: 30 days after the last text. The booking itself follows the trip rules above.
• Booking calls: the recording and transcript, 2 years after the call, kept by Cabpin in Canada (ElevenLabs deletes its copy after 7 days). A recording needed for a complaint, claim or legal dispute is kept until that's resolved. Our working record of the call (your number and the places looked up), 30 days. The booking follows the trip rules above.
• Demo requests: up to two years after our last contact, unless you become a customer.
• Server logs and map-use records: server logs (including the IP address of each map shown or address search) up to 30 days; daily map-use counts 90 days.
• Backups: our daily backups keep a copy of the data for up to 5 weeks, and a monthly copy is kept in a separate, locked-down Google Cloud project in Canada for 12 months, in case of a serious failure. Anything deleted above can remain in these backups until they expire.

Your choices and rights

• You can ask to see the personal information we hold about you, ask us to correct it, or ask us to delete it. Email support@cabpin.com or follow the steps on our support page. We reply within 30 days. Some trip records may need to be kept, without your contact details, for the taxi company's legal or accounting obligations.
• Where a taxi company controls the information (for example your bookings with it), we may pass your request to that company and help it respond.
• You can withdraw your consent, for example by deleting your driver account. You won't be able to use the parts of the service that need that information.
• Drivers can stop location sharing by going offline, or by turning off location permission for Cabpin Driver (you will not receive trips while it is off). Notifications can be turned off in phone settings.
• If you're not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada, or to your provincial privacy commissioner where one applies.

Security

Information is encrypted in transit and at rest. Access is limited by role: each taxi company's staff and drivers can reach only that company's information, and dispatch and admin accounts need two-step sign-in. API keys and webhook messages are protected with secret keys and signatures. If a breach creates a real risk of significant harm, we will tell the people affected and the Privacy Commissioner, as the law requires.

Children

Cabpin is not intended for children under 13. The driver app is only for drivers approved by a taxi company.

Changes

We will post changes to this policy on this page and update the date above. For significant changes, we will also tell taxi companies and drivers in the app or by email.

Contact

Our privacy officer answers questions and requests about this policy. Email support@cabpin.com with “Privacy” in the subject.