How RIDR handles your personal data: what we process, for which purposes, on which legal basis, who receives the data and which rights you have.
Version: 5 August 2026 · Deutsche Fassung
This policy applies to the RIDR app, the web portals at ridr.co and app.ridr.co and this website. It is addressed to everyone who uses RIDR:
Unlike many ride-hailing platforms, RIDR does not have separate privacy notices for passengers and drivers. On RIDR the same person can offer rides and ride along with the same account. Where processing differs by role, we say so.
RIDR LTD
Georgiou Karaiskaki 11-13, CARISA SALONICA, Flat/Office 102
Pervolia, 7560 Larnaca, Cyprus
Registration no. HE 480366, Registrar of Companies, Nicosia
RIDR LTD is the controller within the meaning of Art. 4 (7) of the EU General Data Protection Regulation (GDPR) for the processing described in this policy.
Data protection contact: privacy@ridr.co
As RIDR LTD is established in the EU (Cyprus), the GDPR applies directly. A representative under Art. 27 GDPR is not required.
We process data that you give us, data that arises when you use the platform and, in a few cases, data from other sources. Our principle: we only collect what is necessary for arranging rides, for the safety of our users or to meet a legal obligation.
| Category | Examples |
|---|---|
| Account and profile data | Name (structured as first and last name), phone number (mandatory, verified via SMS code), email address, profile picture (optional), language setting, account status. |
| Identity and verification data | For identity verification (KYC) we work with Stripe: identity document, selfie and liveness check are verified by Stripe Identity. RIDR normally receives and stores only the verification result (confirmed or not confirmed) and the verified master data. Document photos taken in the app are deleted within 24 hours at the latest. RIDR does not store biometric templates. |
| Vehicle data (drivers only) | Scan of the vehicle registration certificate, extracted from it: licence plate, country of registration, keeper name, vehicle identification number, fuel type, CO2 value, number of seats. The vehicle is verified directly from the registration document, not by self-declaration. |
| Location data | Precise location during an active ride or an active offer (pickup, navigation, route matching, arrival time). Background location only while you actively offer or take part in a ride and have granted the permission. Without location sharing, core features cannot be used; addresses can partly be entered manually. |
| Ride and booking data | Origin, destination, intermediate stops, times, distance travelled, seats, co-travellers per route segment, cost contribution, QR boarding confirmations, cancellations. |
| Wallet and payment data | Internal settlement account (balance movements such as top-up, ride costs, credits, payout, refund). Payment instruments such as card details are held exclusively by our payment provider Stripe; RIDR does not store card numbers and does not hold customer money. |
| Communication data | In-app messages between users (operated on EU infrastructure), support requests, attachments you send us. Phone numbers are not disclosed for ride handling; communication takes place in the app. |
| Ratings | Ratings and comments you give or receive, and the average calculated from them. |
| Safety data | SOS events with audio and video recording (dual camera), route deviation events, code word and duress alarm triggers, QR boarding log. Details in Section 5. |
| Device data | Device model, operating system, app version, device identifiers and push token. RIDR ties every account to exactly one phone (one phone per person); for this we process device identifiers for the account-device binding and to detect duplicate accounts. |
| Usage and log data | Logins and logouts, features used, error and security logs, IP address. |
| Taxi section | When you book a taxi ride: pickup and destination, time, agreed fare and the fare confirmation required by law. These data are transmitted to the taxi company you selected, with which your contract of carriage is concluded. |
| Partner portal (companies, municipalities) | Contact details of contact persons, organisational assignment of user accounts (only with their consent), aggregated statistics (e.g. CO2 savings). Reports to companies and municipalities do not contain individual ride profiles of single persons, only aggregated figures. |
| Website chat (RIDR Assistant) | When you use the chat on ridr.co: your chat messages, the assistant's replies, the selected language and the date. Replies are generated by an AI language model (Anthropic, provided via Netlify). To improve quality, we store question and answer in anonymised form, without IP address and without contact details; we cannot link them to your person. Please do not enter personal data in the chat. Your optional rating of a reply (helpful or not) is stored anonymously as well. |
We process your data only where a legal basis under Art. 6 GDPR exists. The table below assigns the legal basis and the main data categories to each purpose.
| Purpose | Legal basis | Data (mainly) |
|---|---|---|
| Creating, managing and securing your account; login via SMS code | Contract (Art. 6 (1) (b)) | Account and profile data, device data |
| Identity verification (KYC) before wallet and ride features are unlocked | Contract; legal obligations of our payment provider; legitimate interest in a platform with real identities | Identity and verification data |
| Vehicle verification from the registration certificate | Contract; legitimate interest (only registered, correctly assigned vehicles) | Vehicle data |
| Matching: search, route matching, pairing drivers and passengers, arrival times | Contract | Location, ride, profile data |
| Calculating and settling the cost contribution, wallet management, payouts and refunds | Contract; legal obligation (tax and accounting law) | Ride, wallet data |
| Taxi brokerage: transmitting the booking to the taxi company, fare confirmation before the ride starts | Contract; legal obligation (regional law on fare agreement and confirmation) | Taxi booking data |
| Safety features: SOS with recording, route deviation, code word, duress alarm, QR boarding | Vital interests (Art. 6 (1) (d)) in an emergency; otherwise legitimate interest in the safety of everyone involved; recordings in an SOS case additionally consent of the person triggering them | Safety, location, ride data |
| Fraud and abuse prevention: duplicate account detection, account-device binding, anomaly checks | Legitimate interest (protecting users and the platform) | Device, usage, verification data |
| Communication between users, moderation of reported violations | Contract; legitimate interest (safe, compliant communication) | Communication data |
| Rating system | Legitimate interest (trust and accountability on the platform) | Ratings, ride data |
| Support and complaint handling | Contract; legitimate interest | Communication, account, ride data |
| Service messages (e.g. booking confirmation, ride status, changes to the terms) | Contract | Account, ride data |
| Product improvement, error analysis, statistics | Legitimate interest; consent where required by law | Usage, device data (aggregated or pseudonymised where possible) |
| CO2 and mobility reports for companies and municipalities | Legitimate interest; reports aggregated only | Ride data (aggregated) |
| Compliance with legal obligations, information to authorities, legal defence | Legal obligation (Art. 6 (1) (c)); legitimate interest | the data required in each case |
Safety is the core of RIDR. Some features process sensitive data for this. We therefore explain them in particular detail:
If a person triggers the SOS alarm during a ride, a recording via both cameras of the phone including audio can start and be live-streamed to the safety desk. All occupants are informed in the app about the possibility of such recordings before a ride starts. Recordings are cryptographically sealed the moment they are created (asymmetric encryption). The key to unseal them is not stored on our servers and not in the app. Unsealing happens only for the investigation of a reported incident, upon documented request, or for law enforcement authorities on a legal basis. Without a reported incident, SOS recordings are deleted after 30 days.
If a ride deviates significantly from the planned route, the app can ask and log the answer. An agreed code word and a duress alarm can signal an emergency without it being noticeable in the vehicle. These events are logged with time and location.
When boarding, the booking is confirmed by QR code. This documents that the right person got into the right vehicle, verified from the registration document. Stored are the time and booking assignment of the scan.
Every account is tied to exactly one device. This prevents account sharing and duplicate accounts and is part of our safety promise to all passengers. For this we process device identifiers permanently for as long as the account exists.
A common industry practice is recurring face recognition checks with selfies stored for years. RIDR does not run its own permanent biometric checks; identity is strongly verified once (Stripe Identity) and the account binding runs via the device, not via recurring selfies.
For a ride to happen, the people involved see of each other: first name, profile picture, rating average, verification status, for drivers additionally vehicle and licence plate as well as the meeting point and the route of the booked segment. Phone numbers are not disclosed; communication runs through the app.
For a taxi booking, the selected taxi company receives the data needed to carry it out (name, pickup, destination, time, agreed fare, in-app contact channel). The taxi company is itself responsible for its own processing; your contract of carriage and the payment of the ride are concluded directly with it.
If you voluntarily assign your account to an organisation (e.g. an employer programme), it receives aggregated reports (participation, CO2 savings, parking spaces saved). Individual ride profiles are not passed on.
We use a small number of service providers bound by contracts under Art. 28 GDPR. We keep an internal register of them; the main recipients are:
| Provider | Purpose | Data location |
|---|---|---|
| Hetzner Online GmbH (DE) | Server hosting | Germany, Finland (EU/EEA) |
| Supabase | Database, authentication, storage | EU (Frankfurt) |
| Amazon Web Services (AWS EMEA) | Operation of the web portals | EU (Frankfurt) |
| Stripe | Payments, payouts, identity verification (KYC) | EU and USA |
| Twilio | Delivery of SMS login codes | USA/global |
| Push notifications (Firebase), maps | USA/global | |
| Resend | Delivery of system emails | EU (Ireland) |
| Netlify | Serving this website | USA/global (CDN) |
We disclose data to law enforcement or supervisory authorities where we are legally obliged to, and we check every request for its legal basis. In legal disputes we process the data required to assert or defend claims. In the event of a restructuring or a sale of the business, data may be transferred to the parties involved to the extent necessary; this policy then continues to apply.
RIDR's core infrastructure (database, authentication, storage, portals, servers) runs entirely in the EU (Frankfurt, Nuremberg, Falkenstein, Helsinki). Your ride, location and profile data are stored there.
We transfer data to the USA only to three providers whose function cannot reasonably be replicated in the EU: Stripe (payment and identity verification), Twilio (SMS delivery) and Google (push notifications, maps). These transfers rely on the standard contractual clauses of the EU Commission and, where applicable, on the adequacy decision for the EU-US Data Privacy Framework.
Many mobility platforms process user data globally and on servers outside the EU. RIDR is deliberately built EU-centred; third-country transfers are the narrowly limited exception, not the norm.
| Data | Retention period |
|---|---|
| Account and profile data | For the life of the account; after account deletion removal within 30 days, unless a legal obligation or an open incident requires otherwise |
| Document photos taken in the app (ID, registration certificate) | No later than 24 hours after verification |
| Verification status and verified master data | For the life of the account |
| SOS recordings (sealed) | 30 days; in case of a reported incident until the proceedings are closed |
| Ride, booking and settlement data | 6 years (tax and accounting retention, Cyprus) |
| Wallet movements | 6 years (like settlement data) |
| In-app messages | For the life of the account; for reported incidents the affected excerpts until closure |
| Ratings and comments | Anonymised after account deletion, remain visible without personal reference |
| Log data | 12 months |
| Website chat (question and answer, anonymised) | 90 days |
| Data of suspended accounts | Core data (account identifier, device binding, reason for suspension) up to 5 years after the suspension, so the suspension cannot be circumvented by re-registration |
Retention periods of 7 to 10 years beyond the end of the account are common in the industry. RIDR deliberately keeps the periods shorter and ties every period to a concrete obligation or purpose.
RIDR uses automated procedures for matching suitable rides (route matching), for calculating the cost contribution within the defined caps and for detecting abuse (e.g. duplicate accounts, forged documents, GPS manipulation).
Decisions with significant effect, in particular the permanent suspension of an account, are not taken by an automatism alone: before a final suspension, a human reviews the case. You have the right to request a review, to state your position and to contest the decision (office@ridr.co).
RIDR has no dynamic pricing based on supply and demand. The cost contribution in the ride-sharing section follows fixed, transparent rules with a hard cap; in the taxi section the fare agreed and confirmed before the ride applies. No profiling is used for pricing.
RIDR does not sell personal data and does not pass data to ad networks, data brokers or social media platforms for advertising purposes. The app contains no advertising SDKs and no tracking for third-party personalised advertising.
We send our own messages about new features or offers only within the legally permitted scope; they can be turned off at any time in the settings.
This is a deliberate difference to large parts of the industry, where user data flows to ad networks and social media platforms. RIDR's business model is the brokerage fee, not the marketing of attention or data.
This website sets no tracking or advertising cookies. Only your language choice is stored (locally in your browser). When the website loads, fonts are retrieved from Google Fonts; Google receives your IP address in the process. The app uses the local storage required for operation (e.g. login state) and no advertising trackers.
Under the GDPR you have the right at any time to:
To exercise these rights, contact privacy@ridr.co. We reply within one month.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular with the Cypriot Commissioner for Personal Data Protection (dataprotection.gov.cy) or with the supervisory authority of your place of residence.
We adapt this policy when features, service providers or the legal situation change. We inform you about material changes in the app or by email before they take effect. The current version is available at ridr.co/privacy; the date above shows the version. For users in Austria, Germany and Switzerland the German version (ridr.co/datenschutz) prevails; otherwise this English version applies.