Printed document on a plain desk
Terms of service.
Booking, prices, cancellation, waiting time, who answers for what, and how complaints are handled.
Terms of serviceLegal
What we collect, why, who receives it, where it goes and what you can make us do about it. effective 10/16/2026.
RYDES LLC, 800 5th Avenue, Suite 101, Seattle, Washington 98104, United States, is the controller of the personal data described in this policy. Where this policy says we, us or RYDES, it means that company.
Once we pass your details to a licensed chauffeur operator so that they can collect you, that operator becomes a controller of that data in its own right. They decide how they hold it and are answerable for it under the law of their country. section 4 explains what they receive and why.
[[SUPPLY]] Two separate Article 27 appointments are required, one in an EU member state and one in the UK, because RYDES LLC is established outside both and offers services to people inside them. Their contact details must appear in this notice. This is a cheap, named service and its absence is among the first things a supervisory authority looks for. Also confirm whether a data protection officer is required under Article 37, which turns on whether the core activity involves regular and systematic monitoring on a large scale. A booking platform that tracks flights and journeys for 1.2 million rides is not obviously outside that.
Some of what a booking needs is treated as a special category or as sensitive personal information by law, and we would rather name it than let it sit unremarked in a list.
Payment card details are entered directly into our payment provider's systems, which are certified to the Payment Card Industry Data Security Standard. We do not receive or store your full card number. We hold a token, the last four digits, the card type, the amount and whether the payment succeeded.
To confirm that a card is being used by its owner, information such as your IP address, email address and card details may be checked by a fraud prevention provider acting on our instructions. Very occasionally, for an individual transaction, we may ask you for a copy of an identity document to verify the cardholder. If we do, redact everything we have not asked for, including all but the last four digits of the card number.
If you rate a journey, we keep the rating against your booking, and we pass it to the operator without your name attached. Ratings are used to monitor how operators are performing and to remove those who fall below the standard. Other passengers do not see your ratings.
[[SUPPLY]] Device, browser, IP address, and any analytics or advertising identifiers actually collected. This must be a description of what the platform genuinely does, not a template list. Send the list of tags and SDKs in the booking flow and the marketing site, and whether they differ.
Under the GDPR and the UK GDPR every use of personal data needs a lawful basis. This is ours, purpose by purpose.
| Why | What | Lawful basis |
|---|---|---|
| Taking and fulfilling your booking | Contact details, journey details, add-ons | Performance of a contract |
| Verifying your number by passcode | Mobile number, verification record | Performance of a contract, and our legitimate interest in preventing fraudulent bookings |
| Passing your details to the operator | Name, number, pickup, destination, requirements | Performance of a contract |
| Tracking your flight | Flight number and public arrival data | Performance of a contract |
| Taking payment and preventing fraud | Payment token, booking value, device signals | Performance of a contract, and legitimate interest in preventing fraud |
| Meeting an accessibility requirement | What you told us you need | Performance of a contract, and explicit consent where the information concerns health |
| Answering a complaint | Booking record and correspondence | Legitimate interest in resolving disputes, and legal obligation where records must be kept |
| Marketing email, if you have opted in | Name and email | Consent, withdrawable at any time |
We do not send marketing text messages, so no basis is claimed for them.
[[SUPPLY]] Confirm this table matches reality and add any purpose missing from it, particularly analytics, personalisation, and any model training or automated decision-making. If any automated process affects whether a booking is accepted, Article 22 applies and this policy must say so explicitly.
This is the sharing that matters most, so it is described precisely rather than generally.
To collect you, an operator needs your name, a contact number for the day, your pickup and destination, your passenger count, and anything you told us that affects the vehicle, such as a child seat, an animal, or an accessibility requirement. That is what they get. They do not receive your payment details, your booking history, your other journeys, or your email address.
The operator is an independent business, usually in another country, and becomes a controller of that information in its own right. Our agreement with them restricts what they may do with it and requires them to delete it when it is no longer needed for the journey.
[[SUPPLY]] A privacy policy has to name the categories, and increasingly the actual companies. Supply the current list with the country each processes in: payment provider, SMS and one-time passcode provider, email provider, flight tracking provider, mapping and routing provider, hosting and cloud provider, analytics, customer support and ticketing, CRM, and any subcontractor of RYDE itself. A named list is more work to maintain and materially more credible than "trusted third parties".
We do not sell your personal data. We do not share it for cross-context behavioural advertising as that term is used in California. section 8 explains what that means for you.
[[SUPPLY]] Confirm both sentences above are true. If any advertising or analytics tag on the booking flow passes identifiers to an ad network, the second one is not, and California treats that as sharing whether or not money changes hands.
A worldwide chauffeur network cannot work without moving personal data across borders, and pretending otherwise would be dishonest. There are two separate flows here and they are handled differently.
When you book, the details in section 4 go to an operator in the country you are travelling in. That may be any of around 90 countries, most of which the European Commission has not found to provide an adequate level of protection.
For this particular flow we rely on the derogations in Article 49 of the GDPR rather than on an adequacy decision or standard contractual clauses. The transfer is necessary for the performance of the contract between you and us, and for the performance of a contract concluded in your interest between us and the operator. Put plainly: a car in Osaka cannot collect you without being told your name, your number and where you are standing, and there is no version of this service in which that data stays in one country.
We send the operator the minimum that makes the collection possible, and no more. Our agreement with them restricts what they may do with it and requires deletion once the journey is done.
Companies that process data on our instructions, such as our payment provider, messaging provider and hosting, are a different matter. Article 49 does not cover them, and for those transfers we rely on an adequacy decision where one exists, or on standard contractual clauses with a transfer impact assessment where one does not.
[[SUPPLY]] Two things for counsel. First, the Article 49 position above is the one the largest comparator takes for exactly this flow, and it is a reasonable reading, but the European Data Protection Board has said Article 49 derogations should be occasional and not repetitive. Using one for every booking in 90 countries is a systematic reliance, and counsel should decide whether to defend that reading, back it with operator-level standard contractual clauses as well, or both. Second, the EU-US Data Privacy Framework remains valid law but is under appeal at the CJEU with an opinion expected late 2026 or early 2027, and both predecessor frameworks were struck down. Certifying is worth doing and must not be the only mechanism for the processor flows above.
Most of what happens to your booking is decided by people. Two things are not.
Both are automated decisions in the sense of Article 22 of the GDPR, and both are permitted because they are necessary to enter into the contract. Neither uses profiling to judge you as a person, and neither affects the price you are shown.
If a booking of yours is refused this way, write to privacy@rydes.co or call dispatch. You are entitled to a human review, to an explanation, and to put your side of it, and we would rather give you all three than lose a booking to a false positive.
[[SUPPLY]] Confirm this describes what RYDE actually does. If any other automated logic affects acceptance, pricing, vehicle assignment or account standing, it belongs here. If a fraud scoring vendor is used, name it and state what it receives. If nothing is automated, delete this section rather than leaving a description of something that does not happen.
[[SUPPLY]] Retention periods must be stated as actual periods or as the criteria used to set them. "As long as necessary" is not compliant on its own. Supply the period for each of: booking records, account records after last activity, payment and tax records, complaint and dispute files, passcode verification logs, marketing consent records, and server and access logs. Tax and accounting rules will drive several of them and vary by market.
When a period ends we delete the data or irreversibly anonymise it. Anonymised booking counts, used for the coverage figures published on this site, contain nothing that identifies anybody and are kept indefinitely.
Write to privacy@rydes.co. We will verify who you are before acting, which usually means confirming control of the email address or mobile number on the booking. We answer within one month in the EU and UK, and within 45 days in California, and we will tell you if we need the extension those laws allow rather than simply taking it.
[[SUPPLY]] Confirm privacy@rydes.co exists and is monitored, and that there is an internal process that can actually meet a one-month statutory deadline including retrieving data from operators. A published right that cannot be serviced is worse than no page. Also confirm whether an authorised agent process is needed for California.
We use encryption in transit, restrict access to the people who need it, and require our providers to do the same by contract.
[[SUPPLY]] Describe what is actually in place, briefly and accurately: encryption at rest, access control and role separation, multi-factor authentication for staff, logging, penetration testing cadence, and the breach notification process and who runs it. Do not claim a control you do not have. A security section that overstates is the one most likely to be read back to you after an incident.
No system is perfectly secure. If a breach affects your data and the law requires it, we will tell you and the relevant regulator within the time the law allows.
Cookies and similar technologies are covered separately in our cookie policy, which explains what is set, what each one does, and how to change your choices.
[[SUPPLY]] The cookie policy does not exist yet and is linked from the footer of every page. It needs building, and it needs a consent banner that actually gates non-essential tags before they fire in the EU and UK. A policy describing consent that the site does not collect is worse than no policy.
RYDES is not for children. You must be 18 or over to make a booking or hold an account, and we do not knowingly collect data from anyone under that age for that purpose.
Children do travel with us, and where they do we hold only what the booking requires: that a child is travelling, roughly their age where a seat stage depends on it, and the seat requested. That comes from the adult booking, not from the child, and it is used only to arrange the journey.
If you believe we hold data about a child that we should not, write to privacy@rydes.co and we will delete it.
We will update this policy as the service changes, and we review it at least once a year whether or not anything has changed. Each version is dated and numbered at the top of this page.
A privacy policy that has fallen behind the systems it describes is not merely untidy, it is inaccurate, which is the one thing a document like this cannot be.
Where a change materially affects how we use data we already hold about you, we will tell you directly rather than relying on you noticing a new date, and where the law requires your consent for the change we will ask for it.
If you are not satisfied with how we handle a privacy question you can complain to your supervisory authority, and you do not have to come to us first.
The other documents that govern your booking.
Booking, prices, cancellation, waiting time, who answers for what, and how complaints are handled.
Terms of serviceWhy we gave up owning a fleet, what an operator is responsible for, and why the work is not auctioned.
About RYDESPractical answers about bookings, waiting time, luggage and changes, in less formal language than this page.
Help centre