Privacy policy
Rutu Rides — Privacy Policy
What Rutu Rides collects, why, who sees it, and how long it is kept.
[Under legal review: brand name only. Counsel decides the legal company name and whether this document should name it.]
1. What we collect
- Your phone number — your account identity; there is no separate password.
- Google account info, if you sign in with Google — your name, email address, and Google account ID, from Google's own sign-in confirmation. We don't see your Google password. [Under legal review: confirm whether this needs its own consent/disclosure treatment distinct from the phone-only path above under Zimbabwean data-protection law.]
- Trip, offer, and booking details — origin/destination, seats, fare or contribution amounts, and messages exchanged through in-app chat about a specific booking.
- Parcel details, when you send or expect one — declared contents and value, recipient name and phone number, and a pickup/drop-off photo (which can include the time and place it was taken) used to confirm custody at each handover.
- A traveller's name, phone number and a short note, when you book a seat for someone else. Their name and note are shown to the driver; their phone number is shown only to you, never to the driver, and is used to send them the booking code, the car's plate and where to meet by SMS. [Under legal review: confirm the notice owed to a third person whose number is given by someone else, and how long it is kept after the trip.]
- Location, only while a safety feature is active — an SOS alert or "share my trip" share, for as long as you keep it on — and, for a driver, from the moment you start a trip until you complete or cancel it, so riders with a booking, and senders with a parcel, on that trip can see where you are. This carries on while the app is in the background or the screen is off, and Android shows a notification for as long as it does. It stops when you complete or cancel the trip, or sign out.
- A profile photo, only if you choose to add one. It is shown to people you are travelling with (for example, a driver's photo to a passenger with a booking on their trip) and you can remove it at any time.
- Profile photos of the people you travel with, kept on your phone only, so the app does not download the same photo again on every visit (at most 50 photos, each fetched again after a week). They are deleted when you sign out or delete your account.
- Your phone's notification address (a push token), if you allow notifications, so we can send you booking and trip updates. It is removed when you sign out or delete your account.
- The number you signed in with, and your first name, kept on your phone only, so that when you come back the welcome screen can ask you to confirm it is you instead of making you type your number again. Neither is sent anywhere for this, and no login is kept: you still receive a fresh code by SMS. They are forgotten when you tap "Use a different number" or delete your account.
- Crash and diagnostic reports from the app: the type of error, where in the app it happened, and basic device information (such as phone model and Android version). Phone numbers, login tokens and tracking links are removed from these reports before they leave your phone. Reports are not collected while you are not running a released version of the app.
- Ratings and reports you or a counterpart submit about a trip or parcel.
- Drivers you follow, and routes you searched, if you tap Follow on a driver. We keep who you follow and, only while you follow at least one driver, up to 10 of the routes you searched recently, so we can tell you once when a driver you follow posts a trip on a route you look for. Searched routes are forgotten after 60 days, and all of it is removed when you stop following, block the driver or delete your account. A driver never sees who follows them; once at least 3 people follow a driver, that driver sees only the number.
- The interest form on our website, if you fill it in: your first name (optional), your phone number, what you are interested in (travelling, driving, or carrying a parcel along a trip) and, if you wish, the route. We keep it until you ask us to delete it, or until we launch and contact you. We send nothing without your consent, and the form itself sends nothing. You can ask us to delete it at any time.
- Payment records — Rutu Rides stores a reference to each transaction (amount, status, which gateway processed it), not your card or mobile-money PIN; those are handled directly by our payment processors (Paynow and Pesepay).
1a. Anonymous usage counts
So we can see what people use and what is missing, the app counts a few things, on Rutu Rides' own server. Nothing is sent to Google or any other analytics company.
- What is counted: that the app was opened; that a search was made, and whether it found any trips; that a trip was looked at or "Book" was tapped; that a parcel or ride request screen was opened; that a notification was opened; and which "More on the way" ideas you tapped. Each count carries the date and time, the app version, the type of phone (Android, iOS or web), and, where it applies, the two towns of the route (for example "Harare-Bulawayo").
- What is not counted: your name, phone number, email, exact location, what you type in a message or note, or any amount you enter.
- Not linked to your name or phone. Each account is given a code made from your account with a secret key kept on our server, so we can tell "one person came back three times" without knowing who that person is. The code belongs to your account, so it stays the same if you sign in on another phone. We don't keep your account ID next to the counts, and the code can't be read back to your account without our secret key.
- You can switch it off in Profile ("Share anonymous usage counts"). When it is off, the app records and sends nothing new. Counts already sent stay on our server until they are deleted after 180 days, or with your account (see below).
- How long we keep it: 180 days, then it is deleted. If you delete your account, your counts are deleted with it.
[Under legal review: review this section — in particular whether the pseudonymous code counts as personal data under Zimbabwe's Data Protection Act, the pseudonym wording ("not linked to your name or phone", "can't be read back to your account without our secret key"), the 180-day retention, and whether a default-on setting with an opt-out meets the consent standard before public launch. Also review this operational limit: the code is made with a key derived from the server's login secret, so if that secret is ever changed, counts made before the change are no longer matched to your account when it is deleted, and stay until their 180 days pass.]
2. What we use it for
- Matching you with a trip or a driver, and letting you and a counterpart complete a booking.
- Operating safety features — sending an SOS alert to your trusted contacts and, where Rutu Rides has set a safety number, to the Rutu Rides safety line, and letting you share your trip with people you choose.
- Confirming a parcel's custody at each step, and resolving a dispute if one is raised.
- Sending you SMS messages you'd expect from using the app (a one-time login code, a parcel PIN and tracking link, a booking confirmation).
- Keeping the platform safe — reviewing reports, and verifying a driver's documents before they can post a trip.
3. Who can see what
- Your real phone number is never shown to another user. In-app calling connects both sides through a masked number; chat and receipts never display it either.
- A parcel's recipient gets a PIN and a tracking link by SMS, and a public (no login needed) tracking page showing the parcel's status and custody timeline — this page does not show live GPS position.
- When you book a seat for someone else, the driver sees the traveller's name, your first name and the note, never the traveller's phone number; the driver calls or messages you, not the traveller.
- An SOS location share can be seen only by you, the trusted contacts the SOS is sent to (through the link in their SMS), the Rutu Rides safety line where Rutu Rides has set a safety number, and authorised Rutu Rides staff.
- A driver's live position, while a trip is under way, is visible only to the driver, riders with a confirmed booking, and senders with a parcel on that trip. It is not shown after the trip ends.
- Rutu Rides staff can access account and trip data as needed to operate the platform (verify a driver, investigate a report, resolve a payment issue) — access is role-gated internally, not open to every staff member for every action.
4. How long we keep it
- A parcel's tracking link and PIN stay valid until 24 hours after the parcel is collected.
- An in-app chat thread about a trip or parcel closes 7 days after that trip or parcel is completed.
- Who you follow stays until you unfollow, block the driver or delete your account. Routes you searched while following drivers are kept for 60 days at most.
- A one-time login code expires after 5 minutes; a login session can be ended at any time by signing out everywhere.
[Under legal review: the above are the retention windows already built into the product for those specific features — a general data-retention schedule for everything else (account records, payment history, reports) still needs to be set with counsel and regulatory requirements in mind.]
5. Third parties we share data with
- Sending SMS for login codes, parcel PINs, and booking notices, via our SMS gateway provider.
- Sending your login code on WhatsApp, only if you ask for it that way: your phone number and the code go to WhatsApp (Meta) to deliver the message.
- Payment processing, via Paynow and Pesepay, for the booking fee and wallet top-ups paid in the app. The fare and any parcel contribution are paid directly to the driver, in cash or the way the driver accepts, and do not go through Rutu Rides or these payment providers.
- Notifications and crash reports, via Google's Firebase services: it delivers push notifications to your phone and receives the crash and diagnostic reports described in section 1.
[Under legal review: how long Google keeps crash reports, and that it may process them outside Zimbabwe, need to be stated here once confirmed against Google's current terms and Zimbabwe's Data Protection Act.]
We do not sell your data to third parties.
6. Your rights
You can ask us at any time to:
- Show you what we hold about you (a copy of your account details, your trips, bookings, parcels and support messages).
- Correct details that are wrong. You can change your name and photo in the app yourself.
- Delete your account. You can do this yourself in the app (Profile, then "Delete my account"), or ask us. Your name, phone number and email are removed straight away. Ride and payment records that the law or our accounts require stay on file but are no longer linked to you.
- Stop optional uses: usage counts, crash reports and WhatsApp notices can each be switched off in Profile.
To ask, write to the address in section 10, or message us from inside the app (Help & Support). Before we act we check that the request comes from you, by sending a code to the phone number on the account. We aim to answer within 30 days. If you think we have handled your data wrongly you can complain to the Postal and Telecommunications Regulatory Authority of Zimbabwe (POTRAZ), Zimbabwe's data protection authority.
[Under legal review: confirm the rights listed, the 30-day answer time and the authority named against Zimbabwe's Cyber and Data Protection Act before publishing. A downloadable copy of your data is not built yet: today a copy is prepared by hand on request.]
7. Children
Rutu Rides is for people aged 18 or over (see the Terms). We do not knowingly collect data about anyone under 18. If we learn that an account belongs to someone under 18, we close it and delete its personal details.
[Under legal review: confirm the minimum age to hold a Rutu Rides account and how that's enforced — no age-verification step exists in the product today beyond phone-number ownership and the 18+ statement in the Terms.]
8. Security
Login uses short-lived access tokens and a separately rotated refresh token, not a stored password. A parcel's handover PIN is verifiable without being stored in a way that lets anyone but the recipient's own tracking page display it back to them.
9. Changes to this policy
Rutu Rides may update this policy from time to time; continued use after an update means you accept the revised policy.
10. Contact
Questions about this policy, or a request about your data: support@rwendo.co.zw [Under legal review: confirm this is the real support/data-protection contact before publishing.]