Privacy Policy

Profile. Phone number, first and last name, date of birth, gender, profile photo (selfie), app language, and the roles on your profile (Passenger, Driver).

Driver. Driving licence: number, category, issue and expiry dates, and photos. Passenger transport licence (when the App asks for it): number, issue and expiry dates, the plate number it names (if any), and photos of its front and back. Vehicle: make, model, class, plate number, VIN, year of manufacture, number of seats, photos of the vehicle (outside, inside and the VIN), and photos of the registration certificate (technical passport) with its issue and expiry dates. Whether the vehicle is your own or driven under a power of attorney and, if so, photos of the power of attorney (1–2 pages) with its issue and expiry dates. The result of each document check, the reason if a document was declined, and which moderator made the decision. If you open a Driver profile from your Passenger profile, the name, date of birth, gender and language already on it are used.

Trips and Bookings. Published Trips (route, time, seats, price, weekly schedules), Bookings, pickup and drop-off points and addresses, the pickup fee quote, Trip stages and their times (including when, and on which phone, a Trip was started), and route alerts. The "Home" and "Work" places you save on the Home screen stay only on your phone and are deleted when you sign out.

Parcels. Parcel category, size, weight, description, and price, the time window for handing it over, pickup and handover points, photos at posting, pickup and handover, the Recipient's name and phone number (entered by the Sender or picked from the phone's contacts; the app does not read your contact list, only the contact you pick), the delivery code, and when the tracking link was opened.

Messages and safety. Chat messages and reactions, reports and blocked users, ratings and reviews, cancellations and missed Trips (reason, comment, time), no-show marks, SOS alerts (reason, location, time), lost-item reports and disputes (text, photo, amount).

Support. Messages you write to RideUz support in the app (text only, up to 2,000 characters), the topic you pick, and when each message was sent and read.

Device and technical data. Device identifier (on Android, the Android ID), device manufacturer and model, app version, push-notification token, sign-in sessions (each bound to the phone it was created on), one-time sign-in codes and the channel they were sent through, IP address and server logs, app performance and crash data.

The app uses your precise location only where you allow it: when you pick a point on the map; when a Driver opens a new Booking or Parcel request, to draw the road route from where the Driver is to the pickup point (this position is sent to our own route server and is not stored); and during a Driver's active Trip. During an active Trip the Driver's app sends its location every 10 seconds (every 5 seconds when approaching a stop), including while the app is in the background — a persistent notification is shown on the phone while this happens. A Trip's live location is accepted only from the phone that started the Trip. This location is shown on the live map only to that Trip's participants (Passengers, Senders, and Recipients) and is not stored permanently after the Trip ends. Locations that are stored: pickup and drop-off points, the places where Trip stages were recorded, and the place an SOS alert was sent from. Before a Driver accepts a Parcel request, its pickup and handover points are shown to Drivers rounded to about 100 m.

• creating your profile, confirming sign-in, managing sessions, and limiting how many sign-in codes one phone can request;
• verifying Drivers and vehicles;
• arranging Trips, Bookings, and Parcels, live tracking, and sending notifications and reminders;
• ordering Trip search results (by departure time, then the Driver's counted cancellations in the last 30 days, then rating);
• safety: SOS, reports, detecting fraud and rule violations, applying the cancellation rules (including recording a booked Trip as missed if the Driver does not start it in time), and making sure a Trip's live location comes only from the phone that started it;
• handling disputes, lost items, and claims, and answering your questions in the support chat;
• improving the app's stability and usability (anonymous analytics and crash reports);
• meeting legal obligations and responding to lawful requests from competent authorities.

We do not sell your data, use it for advertising, or share it with third parties. It is passed on only as far as the Service needs — to the Users described in section 4 and the services listed in section 5 — and to competent state authorities where the law requires. No advertising identifier is collected.

• A Passenger sees the Driver's name, photo, rating, vehicle, plate number, and number of counted cancellations (including missed Trips) in the last 30 days; during an active Trip they can call the Driver and see the Driver's live location.
• A Driver sees the name, photo, phone number, and rating of a Passenger who requests a Booking, their number of late cancellations in the last 30 days, and the pickup point.
• Female Passengers see a badge in search results when a Trip has a confirmed woman passenger; other passengers' names or details are not shown.
• An open Parcel request is shown to Drivers whose Trips match it: the cities, date and time window, category, size, weight, description, photo, and price, with the pickup and handover points rounded to about 100 m. The Recipient's name and phone number and the exact points are shown only to the Driver who accepts the Parcel.
• For an accepted Parcel, the Driver sees the Sender's and Recipient's names and phone numbers. If the Recipient's phone number belongs to a RideUz profile, the Parcel appears in their app and they get notifications that include the Sender's name and the route.
• Anyone who opens a Parcel tracking link the Sender shares sees the Parcel's status and its times, the first names of the Sender and the Driver, the vehicle's make, model and class, and the origin and destination, while the link is valid.
• Anyone who opens a Trip link you share sees the Trip's current stage and its time, the Driver's first name, the vehicle's make, model, class and photo, and the origin and destination, while the link is valid.
• Chat messages are visible only to the people in the conversation; RideUz moderators may see messages that have been reported.
• RideUz support staff see your support messages together with your name, phone number, role, app language and, for Drivers, whether you are verified.
• RideUz moderators see the data needed to handle reports, SOS alerts (including where the alert was sent from, on a map), disputes, claims and document checks (including the documents already on file when you send one again), and can look a Driver up by name, phone number or ID.

Data is stored on servers in the Republic of Austria; photos and document images are stored with Amazon Web Services in Frankfurt, Germany.

All communication between the app and the server uses encrypted HTTPS only; each sign-in session is bound to the phone it was created on, and the server keeps only an identifier of the sign-in token, never the token itself; sign-in tokens are excluded from device backups; photos are opened only through links that expire within an hour; the secret part of shared links is stored on the server as a hash; personal data is masked in server logs; staff access to data is limited to what their role needs.

You have the right to access your data, correct it, withdraw your consent to its processing, and ask for your profile to be closed. You can change your profile and settings in the app yourself, and turn off location, camera, and notification permissions in your phone settings at any time (the related features will then not work). The app has no access to your photo gallery or contact list: it receives only the photos and the contact you pick. Send requests to info@rideuz.app or through the support chat in the app; they are handled within the period set by law. If you have a complaint, you can contact the competent state authority for personal data.

The Platform is not intended for anyone under 18, and we do not knowingly collect their data.

If this policy changes, we will publish the new version on this page with a new date and notify you in the app about significant changes. Questions: info@rideuz.app.