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.
| Data | Who it is about | Why it exists |
|---|---|---|
| Name, email, phone | Company staff, chauffeurs, passengers | Signing in, and reaching the right person about a ride. |
| Company details | The chauffeur company | Branding the booking page, apps and console; billing. |
| Ride details | Passengers | Pickup and drop-off addresses, times, flight number, passenger count, notes. A chauffeur cannot run the ride without them. |
| Chauffeur documents | Chauffeurs | Driver's licence and related documents the company uploads to verify who is authorised to drive. |
| Vehicle photos | The company's fleet | Shown on the booking page so passengers see the car they are getting. |
| Live location | Chauffeurs on duty | See section 03 — this is the most sensitive thing we hold. |
| Technical logs | Everyone | Keeping 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:
- It is visible to that chauffeur's own company — never to another company on the platform, and never to us for any purpose other than running or fixing the service.
- It exists to operate rides. It is not used to score, rank or discipline anyone by us.
- The chauffeur's device controls the permission. Operating-system location permission can be withdrawn at any time — with the honest consequence that live tracking stops working.
- Employment questions about tracking are between the chauffeur and the company that employs them. The company is the controller of that data.
04Why we hold it
- To perform the contract — with the company that licenses MegaRide, and with a passenger who books a ride.
- Legitimate interests — keeping the platform secure, preventing abuse, and fixing what breaks.
- Legal obligations — tax and accounting records tied to payments.
Where the law requires consent — for example, device location on a chauffeur's phone — we rely on consent, and withdrawing it is always possible.
05Who 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:
| Provider | What it does | What it sees |
|---|---|---|
| Google (Firebase) | Sign-in, database, file storage | Accounts, ride records, uploaded documents and photos. |
| Google Maps Platform | Address suggestions and maps | The address text being typed, and map positions. |
| Stripe | Subscription billing | Billing contact and payment details — see section 06. |
| Railway | Hosting the web platform | Traffic and technical logs. |
| Email delivery | Transactional email | Recipient 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.
06Payments
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.
07Keeping 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.
08How long we keep it
- Account data — while the account is open, and for a short wind-down period after it closes.
- Ride records — kept by the chauffeur company for as long as it needs them for its own operations, disputes and tax records. The company sets this; we act on its instruction.
- Chauffeur documents — until the company removes them or the working relationship ends.
- Live location — operational data, kept only as long as it is useful for running and reconstructing rides. It is not archived indefinitely.
- Billing records — for the period tax law requires.
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.
09Your 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:
- see the personal data held about you;
- correct it when it is wrong;
- have it deleted;
- get a copy in a portable format;
- object to or restrict certain processing;
- withdraw consent you previously gave.
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.
10Security
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.
11Children
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.
12Changes
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.
13Contact
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.