DriveXA

Privacy Policy

Last updated: October 18, 2026

1. Introduction

DriveXA is a driving score app. This policy explains which data the app collects, why, who can see it, how long it is kept and how to delete it. It applies to the Android app and to drivexa.ch.

2. Data we collect

Account

  • Email address, used to sign in and to contact you about your account.
  • Sign-in method: email link or Google account.
  • Account status (free or Premium) and app language.
  • In guest mode no account is created: your last 3 trips stay on your phone and are not sent to us.

Location

  • GPS position, speed, heading and accuracy while a trip is recorded.
  • When you start a trip yourself, location is used only until the trip ends.
  • Auto-tracking (Premium, off by default): if you turn it on and choose “Allow all the time” for location, DriveXA uses your location in the background, even when the app is closed, to notice when you leave or enter one of your zones and to start or stop a trip. A notification stays visible while it is on. Outside a trip, these positions are neither stored nor sent.
  • Physical activity (optional): with this permission, Android tells DriveXA when you get into a vehicle, so auto-tracking can wake up without draining the battery.
  • The auto-tracking zones you save: name, position and radius.

Motion sensors

  • Accelerometer and gyroscope readings while a trip is recorded, to measure acceleration, braking and turns.

Trips and scores

  • Start and end time, duration, distance and speed statistics.
  • Route (GPS points), driving score and its sub-scores: regularity, smoothness, turning comfort and anticipation.
  • Incidents (for example harsh braking) and the trip’s event log.

Vehicle data (OBD-II, Premium)

  • Only if you connect a Bluetooth OBD-II adapter.
  • Readings during the trip: speed, engine speed, throttle, engine load and temperature, battery voltage.
  • The adapter’s Bluetooth name and address.
  • The vehicle identification number (VIN) and the make derived from it.

Driving schools

  • If you belong to a driving school: your role (learner, instructor or administrator), the name the school gave you, and the school’s name and logo.
  • Invitations sent by the school, with the invited email address.
  • Trips an instructor records for you during a lesson are saved in your history, marked “Staff-assisted”.

3. How we use it

  • Calculate your scores and show your trips and statistics.
  • Keep your trips and zones in sync across your devices.
  • Start and stop trips automatically, if you use auto-tracking.
  • Show your vehicle’s readings, if you connect an OBD-II adapter.
  • Let your driving school follow your progress, if you are a member.
  • Answer support requests, fix bugs and make the score more accurate.
  • Write plain-language trip summaries (see section 4).

DriveXA shows no advertising and does not use your data to build profiles for third parties.

4. Who can see your data

  • You. Your trips are tied to your account; other users cannot see them.
  • Your driving school, if you join one: while you are a member, its administrator and instructors can see your name, email address and trips. They lose access when you leave the school.
  • The DriveXA team. A small number of administrators can open trips in an internal tool, protected by sign-in, to answer support requests, fix problems and improve the score.
  • Supabase hosts the accounts, the database and the trip files, and sends the sign-in emails.
  • Google provides Google sign-in and, through Google Play services, the location and activity detection used by Android.
  • Anthropic (Claude) writes the plain-language trip summaries. It receives a condensed version of the trip (statistics, incidents, simplified route, vehicle readings), without your email address. Under its terms for business customers, Anthropic does not use this data to train its models.

We do not sell your data and do not pass it to insurers, advertisers or data brokers. We disclose it to authorities only when the law requires it.

5. Security

  • Trips and sign-in tokens stored on your phone are encrypted.
  • Data travels over encrypted connections (HTTPS).
  • On the server, access rules let each account read only its own data (and, for driving school staff, that of their learners). Raw sensor and GPS files are kept in private storage.
  • Data is encrypted at rest by our hosting provider.

6. Transfers abroad

Our providers may process data outside Switzerland and the European Economic Area, in particular in the United States. Such transfers rely on safeguards recognised by Swiss and European law, such as standard contractual clauses.

7. Retention

  • Trips, raw data and zones: until you delete them or delete your account. Deleting a trip also deletes its files and its summary.
  • Driving school membership: until you leave the school or it removes you.
  • After deletion: encrypted backups are replaced within 30 days, and our hosting provider’s server logs expire within a few days.
  • Guest mode: trips stay on your phone until you uninstall the app or clear its data.

8. Your rights

  • Access your data or get a copy of it: write to us.
  • Have inaccurate data corrected.
  • Delete a trip in the app, or your account and all its data: in the app (Profile → Delete my account) or on this site.
  • Withdraw a permission at any time in Android settings (location, physical activity, Bluetooth), or turn off auto-tracking in the app.
  • Lodge a complaint with the Federal Data Protection and Information Commissioner (FDPIC) in Switzerland, or with the data protection authority of your country in the EU.

9. Changes

When this policy changes, we update the date at the top. For significant changes, we let you know in the app or by email.

10. Contact

For any question about your data, write to us:

Back to home