Legal

GDPR checklist for taxi apps

Eight practical points for taxi operators who run their own app. General information, not legal advice.

Short answerA taxi app handles personal data every day: names, phone numbers, pickup places and payment status. Under the GDPR you need a legal basis, a clear privacy notice, a contract with every processor, limits on how long you keep data, and a way to answer riders' requests. This is a checklist, not legal advice. Ask a lawyer for your case. See how HOPIN handles data.

A note first

This guide is general information for taxi operators in the European Union. It is not legal advice. Rules differ by country, and your lawyer or data protection officer should check your situation.

1. Know what data you hold

List every kind of data your app and your office collect:

  • Rider: name, phone, email, ride history, pickup and drop-off places, payment status.
  • Driver: name, contact, licence and vehicle details, location while online, earnings.
  • Company accounts: contact person, invoices.

If you do not need it, do not collect it.

2. Choose a legal basis for each use

The GDPR needs a reason for each use of data. For a ride, the reason is usually that you need it to provide the service (a contract). For marketing messages it is usually consent. Write down which basis you use for what.

3. Publish a clear privacy notice

Tell people who you are, what you collect, why, how long you keep it, who receives it and how to use their rights. Put it in the app, on your website and in the app store listing. HOPIN's own policy is on the privacy page as an example of how a taxi service describes this.

4. Sign contracts with your processors

Your platform, your payment provider and your email tool process data for you. You need a data processing agreement with each. Ask where they store data and who their subprocessors are.

5. Decide how long you keep data

Keep data only as long as you need it. Tax and accounting records have legal minimum periods. Location data usually needs much less time. Write the periods down and delete data when they end.

6. Be ready for requests

Riders can ask what you hold about them, ask you to correct it, delete it or stop using it for marketing. You normally need to answer within one month. Decide who handles requests and how.

7. Protect it

Use strong passwords and two-step login for your admin panel, give each staff member only the access they need, and remove access when they leave. Plan what you will do if there is a data incident. In many cases you must tell the authority quickly.

8. Marketing messages

Ask for clear consent before marketing emails or push messages, make it easy to say no, and respect the choice. Ride confirmations are different from marketing.

FAQ

Does the GDPR apply to a small taxi company?

Yes, if you process personal data of people in the EU, whatever your size.

Do I need a data protection officer?

Only in certain cases, for example large-scale systematic monitoring. Ask your lawyer. Many small operators do not need one.

Who is responsible, me or the platform?

Usually you decide why data is used (controller), and the platform processes it for you (processor). Check the agreement.

How long should I keep ride data?

As short as you can, within legal requirements for accounting. Decide and write it down.

Launch your brand. We'll help you grow it.

Book a 30-minute demo and see the live HOPIN app running on the same platform.