MegaRide

Privacy Policy

Effective 30 August 2026 Last updated 17 September 2026

MegaRide is the software a chauffeur company runs its business on. That means we hold data about two very different groups — the companies who license the platform, and the passengers who book a ride through one of them — and the rules are not the same for both. This page says which is which.

Two roles, and the difference matters. When a chauffeur company uses MegaRide, that company decides what to collect from its passengers and why — it is the controller of that data. We hold and process it on the company's instructions, as its processor. For the company's own account data — the people who sign up, sign in and get billed — we are the controller. Requests about a passenger's ride data go to the chauffeur company; we help them answer.

01Who we are

MegaRide is operated by Mega Ride USA, part of Mega Tickets USA. Reach us at support@megarideusa.com for anything in this policy, including a request to see or delete your data.

02What we collect

Only what the product needs to do its job. No advertising profiles, no data sold to anyone, ever.

DataWho it is aboutWhy it exists
Name, email, phoneCompany staff, chauffeurs, passengersSigning in, and reaching the right person about a ride.
Company detailsThe chauffeur companyBranding the booking page, apps and console; billing.
Ride detailsPassengersPickup and drop-off addresses, times, flight number, passenger count, notes. A chauffeur cannot run the ride without them.
Chauffeur documentsChauffeursDriver's licence and related documents the company uploads to verify who is authorised to drive.
Vehicle photosThe company's fleetShown on the booking page so passengers see the car they are getting.
Live locationChauffeurs on dutySee section 03 — this is the most sensitive thing we hold.
Technical logsEveryoneKeeping the service up and investigating faults and abuse.

We do not ask for, and have no use for, race, religion, health, political opinion or any other special-category data. Please do not put it in a ride note.

03Location data

When a chauffeur is on duty in the chauffeur app, the app reports the vehicle's position so the company's dispatcher can see where the fleet is and tell a waiting passenger the truth about the arrival time. This is real-time tracking of a working person, and we treat it that way:

04Why we hold it

Where the law requires consent — for example, device location on a chauffeur's phone — we rely on consent, and withdrawing it is always possible.

05Text messages

MegaRide sends one kind of text message, and it goes to chauffeurs only: a chauffeur is texted when a ride is assigned to them. The message names the company, the ride, the time and the pickup address, so the chauffeur can act on it without the app open. Nothing else is ever sent by text — no marketing, no promotions, no passenger traffic.

The number comes from the chauffeur’s own record, which the chauffeur company fills in when it adds them to its fleet, confirming at that moment that the chauffeur agreed to be texted about work. The chauffeur has the last word either way: Ride alerts by SMS in the app’s More menu switches them off, and replying STOP to any message does the same at the carrier. Replying HELP returns how to reach us.

Frequency follows the work — about one message per ride assigned, so a busy week brings several a day and a quiet one none at all. Message and data rates may apply. Carriers are not liable for delayed or undelivered messages.

We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. The number reaches our messaging provider (Twilio, section 06) for the single purpose of delivering the message, and goes nowhere else. The sender registered with the mobile carriers for these messages is Mega Tickets USA, which operates MegaRide.

06Who else processes it

MegaRide runs on infrastructure we do not own. These are the companies that touch data on our behalf, and what each one gets:

ProviderWhat it doesWhat it sees
Google (Firebase)Sign-in, database, file storageAccounts, ride records, uploaded documents and photos.
Google Maps PlatformAddress suggestions and mapsThe address text being typed, and map positions.
StripeSubscription billingBilling contact and payment details — see section 06.
RailwayHosting the web platformTraffic and technical logs.
TwilioText messages to chauffeursThe chauffeur’s phone number and the text of the message — see section 05.
Email deliveryTransactional emailRecipient address and message content.

We do not sell personal data, and we do not share it for advertising. We disclose data outside this list only when the law compels us, and only as far as it compels.

07Payments

We never see or store full card numbers. Card details are entered directly with Stripe, which is PCI-DSS certified. What comes back to us is enough to show a receipt and know an invoice was paid — the card brand, the last four digits, and the outcome. Stripe's own privacy terms govern what they hold.

08Keeping companies apart

MegaRide is one platform hosting many chauffeur companies, and the single most important promise we make is that one company can never read another's data. Every stored record is filed under its company, and access is checked on the server against a token that names which company the signed-in person belongs to — not in the browser, where anyone could edit it.

We test this deliberately rather than trusting it: an automated suite attempts cross-company access on every change and fails the build if a single attempt gets through.

09How long we keep it

When a company leaves MegaRide, we delete its data on request and otherwise after the wind-down period. Backups roll off on their own schedule.

10Your rights

Depending on where you live — the GDPR in Europe and the UK, the CCPA/CPRA in California, the LGPD in Brazil, and comparable laws elsewhere — you can ask to:

Where to send the request. If you booked a ride with a chauffeur company, that company holds your data and answers your request — contact them first. If you cannot reach them, or your request is about a MegaRide account itself, write to support@megarideusa.com and we will act, or route it to the right company and help them act.

We do not charge for this and we do not treat anyone differently for asking.

11Security

Traffic is encrypted in transit. Access to company data requires a signed-in account whose token names its company, and the rules that enforce it live on the server. Uploaded documents are stored with access controls rather than on a public URL.

No system is perfect, and claiming otherwise would be the least trustworthy sentence on this page. If you believe you have found a vulnerability, write to support@megarideusa.com — we would rather hear it from you than from an incident.

12Children

MegaRide is a business tool and is not directed at children. We do not knowingly create accounts for anyone under 18. A passenger's booking may name a minor travelling in the vehicle; that record belongs to the chauffeur company and exists only to run the ride safely.

13Changes

When this policy changes we update the date at the top. If a change materially affects what we collect or who processes it, we tell account holders directly rather than relying on you to notice.

14Contact

Questions, requests and complaints: support@megarideusa.com.

If you are in the European Economic Area or the UK and you are not satisfied with our answer, you have the right to complain to your national data protection authority.