Privacy Policy

Last Updated: October 6, 2026  · Operator: Dravex LLC, doing business as My Transfer Miami

When you use our Platform or submit a booking request, we may collect:

• Name, phone number, and email address
• Pickup and drop-off locations
• Travel dates and times
• Payment information (processed securely via Stripe)
• Communications via WhatsApp or email

We use your information to:

• Process and confirm reservation requests
• Assign an available transportation Provider
• Send booking confirmations and updates
• Process payments via Stripe
• Improve our Platform and services
• Comply with legal obligations

We do not sell your personal information. We may share your information with:

• Independent Providers — to fulfill your transportation request (name, phone, pickup location, travel details)
• Stripe — to process payments securely
• Law enforcement — if required by law

We implement reasonable security measures to protect your information. However, no method of transmission over the internet is 100% secure.

Our website may use cookies to improve user experience. You may disable cookies in your browser settings.

Our Platform uses the following third-party services which have their own privacy policies:

• Stripe (payment processing) — stripe.com/privacy
• Google Maps (route calculation) — policies.google.com/privacy
• Google Calendar (optional, private dispatch records) — policies.google.com/privacy
• WhatsApp (communication) — whatsapp.com/legal/privacy-policy

My Transfer Miami Booking includes an optional Google Calendar connection for the authorized Dravex operator, not a Google sign-in service for passengers. It is used only for internal booking administration. Customers do not need a Google account, receive no Calendar invitation from this integration, and cannot see the operator's private calendar or Google-account email through the booking page.

• Access: With the calendar owner's consent, we request calendar.freebusy to check availability intervals and calendar.app.created to create dedicated private booking and test calendars in the Dravex account and create, read back, and delete events on those app-created calendars. This does not grant event-content access or event-editing rights to the operator's pre-existing calendars. Application event writes and readback are restricted to the configured booking or test calendar. Any additional calendars used for availability diagnostics must be explicitly configured by the operator.
• Use: Availability intervals are processed transiently for an administrator's connection diagnostic; they are not used to read unrelated event descriptions or automatically determine fleet capacity. A booking event may contain the booking reference, customer name and phone, trip addresses and times, vehicle class, passenger and bag counts, flight number, quoted amounts, payment status, and booking notes supplied through our Platform.
• Storage and protection: OAuth credentials and the offline refresh token are stored only in protected server environment settings, not in browser code or a public repository. The booking database stores booking information and its Calendar event identifier. This integration does not import unrelated Google Calendar event contents into the booking database.
• Sharing: Google processes the booking event in the operator's configured private calendar. The integration does not make calendars public, add event attendees, or automatically send calendar invitations. Google Calendar data and OAuth tokens are not sent to Mia or an AI model, used to train AI models, sold, or used for advertising. Passenger communications and dispatch details supplied directly to our Platform are handled separately as described above.
• Retention and control: Booking records and event identifiers are retained for service administration and applicable legal obligations. Cancellation or refund removes the linked event according to the booking workflow. The calendar owner can revoke the application's access in their Google Account's third-party connections settings, which prevents future token refreshes, or contact us to disconnect the integration and request deletion. Revocation alone does not delete existing Calendar events or booking records; deletion requests are subject to applicable recordkeeping obligations.

Our use of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

You may request access to, correction of, or deletion of your personal information by contacting us at info@mytransfermiami.com.

• Email: info@mytransfermiami.com
• WhatsApp: +1 (786) 486-5474