Privacy Policy

Ride.mg ("the app") is a ride-hailing app for Antananarivo, published by Flit Soft. A rider names the price they will pay for a ride; nearby drivers accept that offer or bid back their own price. The rider chooses who picks them up, follows the ride on a live map, and reviews the driver afterward — and the same account can apply to become a driver at any time.

This policy explains exactly what the app collects, where it is stored, who it is sent to, and how to get rid of it. Questions go to flitsoft.dev@gmail.com.

Account details. When you sign in, we receive your email address, your display name and your profile picture from the sign-in provider, and we store them together with the account identifier that provider issues. We never see or store your password.

Ride details. Your pickup and dropoff points, the price you offer, every bid a driver sends back, and the ride's status from request through completion or cancellation.

Location, while the app is open. The app asks for your location only to place your pickup pin, show nearby drivers, and follow your driver's live position during a trip — it is never collected in the background, and the app requests no "always" location permission.

Driver application details, if you apply to drive. Your name, phone number, and photographs of your driving licence and vehicle papers, submitted for a human reviewer to check before your application is approved.

Reviews. The star rating and comment you leave about a driver after a ride, and the one a driver leaves about you.

Photographs. Your profile photo, and the licence and vehicle-paper photos attached to a driver application. Both are picked with the system photo picker or camera — the app never reads your photo library in the background.

The app contains no advertising SDK and no third-party analytics or tracking SDK. It has no AI feature: nothing you write or say inside the app is sent to any AI or machine-learning model. The app does not process payment — a fare is agreed between rider and driver and paid directly, in person, and no payment card or bank detail is ever collected by the app.

Image files — your profile photo and driver-application documents — are stored in Google Firebase Storage. The database only ever holds the address of an image, never the image bytes.

Everything else — your account record, rides, offers, reviews, driver applications and settings — is stored in a PostgreSQL database hosted by Supabase, in the United States.

Authentication is handled by Google Firebase Authentication and Google Sign-In.

The live map and the route between pickup and dropoff are drawn using Google Maps.

Traffic between the app and our servers is encrypted in transit with HTTPS.

Google Firebase Authentication and Google Sign-In — sign you in and issue the token that identifies you to our backend.

Google Firebase Storage — stores your profile photo and driver-application documents.

Google Maps — draws the map, the pickup and dropoff pins, and the road route for a ride.

Supabase — hosts the PostgreSQL database holding your account, ride and review records.

Apple Push Notification service and Firebase Cloud Messaging — deliver the notifications you have switched on (a new bid, an accepted offer, a driver arriving). We store the push token your device issues so we can reach it.

Each of these providers operates under its own privacy policy and processes your data on our instructions in order to run the app.

Photographs you submit with a driver application — your licence and vehicle papers — are seen only by the people who manually review applications. They are never shown to a rider or to another driver.

Once a driver, your public rating and review history are visible to riders considering your offer. Your licence and vehicle-paper photos remain visible only to reviewers.

A ride you request is visible to the drivers it is offered to, and to the driver who accepts it, for the duration of that ride. A review you leave, and one left about you, is visible to the other party and factors into the public rating shown before a ride is accepted.

You can block another member. A block is mutual: they cannot see your rides or offer on them, and you cannot see theirs.

If you create an API key inside the app for your own programmatic access, that key can read your own data and nobody else's. We store only a SHA-256 hash of the key and a short visible prefix; you see the full key once, when you create it. You can revoke a key at any time.

We keep your data for as long as your account exists. Delete your account and we remove the stored image files first, then the account record and everything attached to it — rides, offers, reviews, your driver application if you made one, and any block or report involving your account.

Account deletion is permanent and is not reversible.

You can read your ride history and reviews from inside the app, and delete your whole account at any time from the account settings screen.

Depending on where you live you may also have the right to request a copy of your data, to have it corrected, or to object to its processing. Write to flitsoft.dev@gmail.com and we will respond within 30 days.

The app is not directed at children under 13 and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will delete it.

If we change how the app handles your data — in particular if we add payment processing or an AI feature — we will update this page and change the date at the top. Material changes will also be announced inside the app.

Email flitsoft.dev@gmail.com for anything at all: a privacy question, a data request, or a mistake you spotted on this page.