MegobeEste documento legal é publicado em inglês; a versão em inglês é a que prevalece.
Private Driver — Privacy Policy
Ace Limited LLC ("we", "us"), 6831 Eastview Dr, Lake Worth, FL 33462, operates the Private Driver application and the provider booking pages (the "Service"). This policy explains what personal information we collect, why, who sees it, how long we keep it, and your rights.
1. Two roles, two relationships
- Providers (transportation businesses subscribing to the Service): we are the controller of your account and subscription data.
- Passengers and Guests (people booking a ride from a Provider): the Provider you book with collects your booking details through their booking page for their business; we process that information on the Provider's behalf to run the software, and we are the controller only of the technical and security data described in §2.4. Questions about how a Provider uses your information should go to that Provider; you may also contact us and we will help.
2. What we collect
2.1 Providers. Name, email, mobile number, business name and legal name, country / state / city, language, currency and distance-unit preferences; vehicle details and photos; business-card design and logo; pricing and availability settings; identity and compliance documents you upload (driving licence, commercial insurance, vehicle registration — including the document number, expiry, insurer, coverage amount, and the image); the six certifications you make and when; subscription tier and payment status (payment itself is taken outside the app by our payment provider); your team members' names and mobile numbers if you add staff; notifications; notes.
2.2 Passengers with an account. Name, email, mobile number; saved home and work addresses (with coordinates if you pick a suggestion); your bookings; the Providers you have linked; language; notifications.
2.3 Guests. Name, mobile number, email if given, the booking details below, your preferred language, and a booking reference (we store only a one-way hash of it).
2.4 Booking details (all Passengers). Pickup and drop-off addresses with coordinates, place identifiers and country/region/city; stops; date and time and time zone; passenger and luggage counts; flight number and aircraft registration if given; chosen terminal; notes; the price computed from the Provider's rates and the measured or estimated route; payment method stated and payment status recorded by the Provider; cancellation and modification history; the version of the terms and disclosure shown to you.
2.5 Technical. Device type and OS, app version, IP address, log and security events, approximate location derived from IP for fraud prevention. We do not track a Provider's or Passenger's live location during a ride — the Service has no live tracking.
2.6 Address lookups. When you type an address, the text you type is sent to our server, which queries Google's Places, Routes and Time Zone services to resolve it. The result (place identifier, coordinates, country) is stored with the booking; Google's own privacy policy applies to Google's processing.
3. Why (legal bases where they apply)
To run the Service and perform our contract with Providers; to let a Provider perform their contract with you; to operate platform conditions (document review and expiry); for security, fraud prevention, and abuse limits; to comply with law (including record-keeping duties for transportation records); and, with consent where required, to send messages.
4. Messages
We send transactional messages only: booking received, accepted, declined, changed, cancelled, completed, payment marked, receipt, and verification codes. Channels: in-app always; email and SMS only when enabled and only to a number or address you gave for that booking. Reply STOP to any SMS to stop SMS. We send no marketing. We never place automated or artificial-voice calls.
5. Who sees what
| Data | Who can see it |
|---|---|
| A Provider's public page (name, vehicle, photos, rates, payment methods, cancellation policy) | Anyone with the link or QR code. Not listed, indexed, or searchable inside the Service. |
| A Provider's mobile number | The Passenger, only after the Provider has accepted the booking. Never on the public page. |
| A Passenger's name and mobile number | The Provider they booked, and that Provider's staff assigned to the booking. |
| A Provider's documents and identity information | The Provider and our administrators, via time-limited links. Never other users. |
| A Provider's calendar and customer list | The Provider (and their staff, limited to assigned jobs). Never other Providers. Availability checks by a Passenger reveal only "free / not free" and an alternative time. |
| Bookings | The Provider and the Passenger of that booking; our administrators for support. |
We share data with processors that run the Service: Supabase (database, authentication, storage, edge functions; US-East), Google (address, route and time-zone lookups), our email and SMS providers when enabled (Resend, Twilio), our payment provider for subscriptions (Stripe, Inc.), and flight-data providers for the flight number or registration you give us (AeroDataBox). We do not sell personal information and do not share it for advertising. We disclose data when the law requires or to protect rights and safety.
6. How long we keep it
| Data | Retention |
|---|---|
| Booking records | While the Provider's account is active, as part of the Provider's own business records, and in any case at least the period required by transportation law where the ride occurred (Florida: 1 year). |
| Passenger contact details (registered and Guest) | Kept as part of the Provider's own customer records while the Provider's account is active; deleted or anonymised after the Provider's account is closed, or earlier on the passenger's request where the law allows. |
| Provider documents | While the account is active and for at least 1 year after it closes (statutory driver-record retention), then deleted. |
| Certifications and terms acceptances | Kept as a record for as long as the account exists and the statutory period after. |
| Security logs | 365 days. |
| Cached address and route results | Up to 30 days (Google's terms), place identifiers longer. |
7. Your rights
Depending on where you live you may have rights to access, correct, delete, port, or restrict the use of your personal information, to object to processing, and to complain to a supervisory authority. Contact support@megobe.com. Passengers may also direct requests to the Provider they booked with; we will assist the Provider. We verify identity before acting. We will not discriminate against you for exercising a right.
Florida residents: the Florida Digital Bill of Rights applies to certain large businesses; we honour deletion and access requests regardless. We do not sell biometric data and do not use facial recognition.
8. Children
The Service is not for anyone under 18. We do not knowingly collect information from children; tell us if you believe we have.
9. Security
Data is encrypted in transit and at rest; access is restricted by row-level security so that each account sees only its own data; documents are served through expiring links; verification codes and booking references are stored hashed. No system is perfectly secure; we will notify you and the authorities of a breach as the law requires.
10. International transfers
Our servers are in the United States. If you use the Service from elsewhere, your information is transferred to and processed in the US under appropriate safeguards.
11. Changes
We will post changes here with a new version date and, for material changes, notify account holders in the app.
12. Contact
Ace Limited LLC, 6831 Eastview Dr, Lake Worth, FL 33462, support@megobe.com.
---
Version 2026-09-28.