Privacy Policy — Euro Taxi

Last updated: September 17, 2026

This Privacy Policy describes how Euro Taxi (eurotaxi.mx) collects, uses, stores, and protects personal information when you use:

• the mobile application Euro Taxi ("the App") as a client (rider), driver, or authorized administrator; and
• the website at eurotaxi.mx, including the taxi request form.

By using the App or the website, you agree to the practices described here. This URL may be used as the privacy policy in Google Play Console; Section A describes data collected by the Android application.

A) Euro Taxi mobile app

This section applies only to the installed application on mobile and desktop devices (admin panel). It does not cover the web WhatsApp request form.

1. Data we collect in the App

We collect only data necessary for ride requests, dispatch, service operation, safety, and legal compliance.

a) Location (precise and approximate)

Android permissions, by role:

• ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION — clients, drivers, and administrators.
• Drivers on Android: we also request background location (ACCESS_BACKGROUND_LOCATION / "Allow all the time") to keep the driver's position published while connected or on a trip, even when the app is not in the foreground.

We use location to:

• display positions on maps and calculate routes, distances, and ETAs;
• match clients with nearby drivers (Geofire);
• track trip progress and accumulate kilometers for fare calculation;
• publish the driver's position while available or working;
• driver safety alerts (panic button).

Drivers (Android): while the service is active, a persistent notification ("Driver online") is shown, location is updated continuously, and a periodic heartbeat (approx. every 5 minutes) indicates the driver is still online. Position publishing stops when disconnecting or signing out.

Before asking for "Allow all the time", the app shows an on-screen disclosure (dialog) explaining background location. The driver can decline; in that case the permission is not requested and they cannot stay online with the app minimized.

Battery optimization (Android drivers): we may ask to ignore battery optimization (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS) so the system does not stop GPS or trip requests while the app is in the background. This is explained in a separate disclosure and can be declined. It does not grant access to photos or files. It can be reversed in system Settings.

Clients: location is used mainly while the app is in use (foreground or during an active trip). Clients are not asked for background location permission.

b) Notifications

We request notification permission (POST_NOTIFICATIONS on Android) and use Firebase Cloud Messaging (FCM) for:

• trip requests, offers, and status changes;
• chat messages and operational alerts;
• administrative dispatch messages;
• security alerts, including new sign-in detected on another device.

c) Profile and account

• name;
• phone number (primary authentication via OTP);
• email and password (optional, linked to phone);
• role (client, driver, or administrator);
• profile photo (optional);
• driver and vehicle data: license plate, make, model, color, unit number, and service preferences.

d) Trips and service

• origin, destination, and intermediate stop addresses;
• GPS coordinates, routes, distance, duration, and estimated or final fares;
• trip preferences (pets, cargo, bank transfer, physical assistance, etc.);
• trip status, history, and ratings (1–5 stars);
• in-trip chat between client and driver during active trips, including typing indicators and unread counts;
• cancellation records, penalties, reputation, and account suspensions when service rules apply.

e) Safety — panic button (drivers)

Drivers can trigger a panic alert that sends authorized administrators: name, phone, license plate, vehicle, unit number, real-time GPS coordinates, map link, and trip context (if applicable). This data is stored on our servers (Firebase) for operational response and retained in admin history.

f) Photos

You may upload a profile photo with the camera or the system photo picker (the app does not request access to the full gallery or the READ_MEDIA_IMAGES permission). The image is stored in Firebase Cloud Storage at clients/{uid}/profile.jpg or drivers/{uid}/profile.jpg and linked to your account.

g) Device, session, and identifiers

• device identifiers (e.g. Android ID, IDFV on iOS, or equivalent desktop ID) for single-session control;
• FCM token for push notifications;
• sign-in history: device ID, device name, OS version, and timestamp;
• current_device_id on your profile to detect access from another device and, when applicable, end previous sessions.

h) Data stored locally on your device

• recent pickup and destination addresses (up to 10 each);
• client local trip history (up to 20 records);
• closed admin dispatch messages for drivers (up to 20);
• app preferences (role, email verification, admin panel theme);
• anti-abuse counters for address search (Places).

This data stays on the device until you clear it, clear app data, or uninstall Euro Taxi.

2. How we use App data

• book trips, dispatch drivers, and manage the service;
• connect clients and drivers and show necessary data during a trip;
• calculate fares, cancellation penalties, and price estimates;
• send notifications, operational messages, and security alerts;
• manage reputation, ratings, and suspensions;
• operate the admin panel (fleet, dispatch, panic alerts);
• meet legal obligations and prevent fraud or abuse.

3. Third-party services in the App

• Google Firebase: Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging, Cloud Storage. Firebase App Check is planned for the project but may not be active in all builds.
• Google Maps Platform and Places: maps, geocoding, address autocomplete, and route calculation.
• OpenStreetMap / CARTO (desktop admin panel): alternative maps; your IP may be sent to tile servers under their policies.

We do not use Firebase Analytics or Firebase Crashlytics in the App. Google and Firebase may still generate their own technical infrastructure logs.

4. Additional App features

• TTS (Android drivers only): spoken offer countdowns; text is processed on-device, not uploaded.
• Audio: local sound playback (trip alerts, dispatch, admin panic); we do not record user audio.
• External links: the app may open maps or other system apps; we do not send SMS or WhatsApp from the app.

B) eurotaxi.mx website

This section applies to the static site at eurotaxi.mx, including the "Request taxi" form. It is not part of the Android app or Google Play Data safety form, but it does process personal data when you use the web form.

1. Data we collect on the website

The request form may ask for, among other fields:

• neighborhood or area;
• full address and, if provided, a home reference;
• destination;
• name and phone number;
• additional notes and wait time;
• optional browser GPS location, if you authorize it, to adjust pickup on a map (Leaflet) and, if the neighborhood has no fare table, estimate route distance and time.

2. How that data is processed

• No own backend: form data is not sent to Firebase or an Euro Taxi database.
• When you submit, a message is built and WhatsApp opens (+52 222 458 4262) with pre-filled text. From that point, processing is subject to Meta / WhatsApp policies.
• The neighborhood and fare lists are loaded from static JavaScript files; they are not uploaded to a server.

3. Cookies and local storage on the website

The website does not use its own cookies. Your browser may keep a form draft in localStorage (neighborhood, street address, landmark, name, and phone) so the next visit fills faster. Destination and trip notes are not remembered. This data is not sent to an Euro Taxi server; you can delete it with “Delete saved data on this device” or by clearing site data in the browser. Integrated third parties (e.g. Leaflet CDN, WhatsApp when opening the link) may use their own technologies under their policies.

4. Third parties on the website

• WhatsApp (Meta): channel for submitting the request message.
• Leaflet / OpenStreetMap: interactive map for location adjustment.
• OSRM (OpenStreetMap): free distance and time estimate when a neighborhood has no fare table. Only origin and destination coordinates are sent, not your name or phone number.
• External resources (e.g. CDN) required to load the site.

Data sharing

We do not sell personal data. We share limited information only when necessary to:

• provide transportation service (e.g. driver sees client data during a trip);
• operate infrastructure providers (Google Firebase, Google Maps, WhatsApp on the website);
• respond to emergencies or panic alerts to authorized staff;
• comply with law or competent authority requests.

Data retention

We retain data as long as needed to operate the service, resolve disputes, apply penalties or reputation rules, and meet legal obligations. Local device data can be removed by clearing app data or uninstalling. Authorized administrators may permanently delete driver accounts when appropriate, including Firebase profile and authentication account.

Security measures

We use authenticated access control, Firestore security rules, encrypted communication with cloud providers, and single-device session control. No system is 100% secure; protect your device and notify us if you detect unauthorized access.

Controls and your rights

You may revoke permissions (location, notifications, camera) in device settings; disconnect as a driver to stop publishing location; or stop using the App or website.

In-app account deletion: the map menu (passenger or driver) includes Delete account. It removes your profile, photo, session, and personal data. If a trip is in progress, finish or cancel it first. Completed trips are kept for the other party without your name, phone, or email.

If you are in Mexico, you may exercise your Access, Rectification, Cancellation, and Opposition (ARCO) rights by emailing contacto@eurotaxi.mx with your name, contact method, and request details. We will respond within applicable LFPDPPP timeframes.

Children

Euro Taxi and the website are not directed at minors. We do not knowingly collect data from children.

Google Play compliance

Section A) Mobile app describes data collection, sensitive permissions (background location for Android drivers, notifications, camera for profile photo), and use limited to the transportation service purpose. It should align with the Data safety form and the background location declaration in Google Play Console.

Changes to this policy

We may update this policy. Material changes will be reflected in the "Last updated" date and, when appropriate, through notices in the app or website.

Contact