This Privacy Policy describes how the personal data of Users of the mobile app TapTaxi (the ‘App’) is processed and protected, in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR) and applicable Polish law.
The App is a technology platform through which the taxi company Taxi Kaszuby, trading under the brand TapTaxi, provides passenger transport intermediary services and is responsible for relationships with Drivers and Passengers. The App software and the technical infrastructure on which data is processed (including the Google Firebase project) are owned by the technology provider — Taxi Osowa Patryk Fanslau (brand: FTSProjekt) — acting on behalf of and on the instructions of the Controller (see section 1).
The App serves two groups of Users. We require different information from each group and use the following labels throughout this Policy:
TAXI KASZUBY RADOSŁAW CZERNIECKI
trading under the brand / taxi company name: TapTaxi
ul. Szymanowskiego 2C lok. 1
83-330 Pępowo
Tax ID (NIP): 8451824894 · Business registry number (REGON): 381828420
Contact: taptaxipl@gmail.com
Determines the purposes and means of data processing; is responsible for relationships with Drivers and Passengers and for delivering the service.
Taxi Osowa Patryk Fanslau (brand: FTSProjekt)
ul. Gospody 18A/7, 80-340 Gdańsk · NIP: 5842626895
Owner of the App software, database and source code, and of the technical infrastructure (Google Firebase project), to which it has administrative access solely to maintain and operate the App. It processes data on behalf of and on the instructions of the Controller under a data processing agreement (Article 28 GDPR) and does not disclose it to any entities other than those listed in section 7.
Contact (technical matters): Patrykfanslau@gmail.com
For questions about personal data protection or to exercise your rights under the GDPR, please contact the Controller: taptaxipl@gmail.com. Technical matters relating to the operation of the App are handled by the technology provider: Patrykfanslau@gmail.com.
The data we collect depends on the User’s role. The table below shows which categories apply to each group:
| Data category | Applies to | Purpose | Legal basis (GDPR) |
|---|---|---|---|
| Account data: email address, telephone number, first name / name, role, password (stored in encrypted form) | BOTH | Account creation and management, sign-in, contact | Article 6(1)(b) |
| Journey data: pick-up and destination addresses, coordinates, route, price, payment method, notes, messages in the journey chat, journey history | BOTH | Providing the journey, processing payment and handling complaints | Article 6(1)(b) and (f) |
| Journey ratings and reviews | PASSENGER | Service quality monitoring, handling reports | Article 6(1)(f) |
| Location (GPS) for booking and providing a journey | PASSENGER DRIVER | Identifying the pick-up point; reaching the Passenger and providing the journey | Article 6(1)(b) |
| Location (GPS) in the background while ‘online’ | DRIVER | Sharing the vehicle’s current position with dispatch and the Passenger, assigning bookings | consent — Article 6(1)(a) |
| Reports of detected false location data (apps that spoof GPS location) | DRIVER | Preventing abuse, passenger safety | Article 6(1)(f) |
| Vehicle and Driver data: vehicle make and registration number, category, additional services | DRIVER | Authorisation to provide transport, safety, providing the service | Article 6(1)(b) and (f) |
| Business and licence data: business name, address, NIP, REGON (PESEL only where there is no NIP), licence number, issuing authority, licence extract number, form of cooperation (B2B / Fleet Partner), cooperation start and end dates | DRIVER | Register of assigned bookings and carrier records required under the Road Transport Act (Article 27b), cooperation agreement | Article 6(1)(b) and (c) |
| In-person verification: digital copies of documents (identity document, driving licence, criminal record certificate, driving entitlement report), reference facial photograph | DRIVER | Verifying identity and entitlements before cooperation begins (Article 27e of the Road Transport Act) | Article 6(1)(c) |
| Facial photographs (selfies) from periodic verification | DRIVER | Confirming that the registered Driver is providing the journey — at least once every 50 journeys and at least once every 7 days (Article 27e(7)–(8)) | Article 6(1)(c) |
| Automated facial comparison (biometric data — see section 5) | DRIVER | Fast, automated identity verification | voluntary, explicit consent — Article 9(2)(a) |
| Settlement data: Wallet (Funds and Bonus), commissions, penalties, top-ups (PayU), settlement logs | DRIVER | Settlements and payments, accounting and tax obligations | Article 6(1)(b) and (c) |
| Payout details: account holder, bank account number (IBAN), payout history | DRIVER | Paying out Funds from the Wallet | Article 6(1)(b) and (c) |
| Technical data: notification token (FCM), installation/device identifiers, online status, IP address (for payments), diagnostic data | BOTH | Notifications, security, stability, preventing abuse | Article 6(1)(f) |
App notifications relate only to service operations: bookings, journeys, verification, payouts and dispatch messages. We do not send marketing communications or use data for marketing purposes.
PASSENGER Location is used to identify the pick-up point and place a journey booking.
DRIVER When a Driver is ‘online’, the App processes location data in the background as well (when running in the background or with the screen off), to share the vehicle’s current position with dispatch and the Passenger, assign bookings and ensure safety. Background processing is based on separate consent given in the system settings; it can be withdrawn at any time by going ‘offline’ or changing permissions in the phone settings (which may limit the ability to receive bookings).
DRIVER The App checks whether location data comes from a location-spoofing app (‘mock location’). Detection of such a location is recorded and reported to the Controller — it does not automatically block the account.
The Driver’s current position is stored briefly and overwritten. We retain detailed location and journey data for 12 months, after which it is anonymised (see section 9).
DRIVER Camera access is used solely to take a facial photograph (selfie) to verify the Driver’s identity. The Controller uses the camera in the dispatch panel during in-person verification (reference photograph, document copies). The App does not record or store video or provide continuous camera monitoring.
1) Phone biometric sign-in (fingerprint and device facial recognition / Face ID) — handled entirely by the phone’s operating system. The App receives only a ‘yes / no’ confirmation, and sign-in credentials are stored locally in the device’s encrypted storage. No fingerprint or facial template from the phone’s sensor is transmitted to or stored in our database.
2) Driver identity verification (described below) — a separate mechanism: a photograph (selfie) taken with the camera and compared with the reference photograph. This is not the phone’s Face ID. It applies only to Drivers.
DRIVER Under Article 27e of the Road Transport Act , a passenger transport intermediary must:
Taking a selfie is therefore a legal obligation and does not require consent. The selfie may be compared with the reference photograph in two ways:
The Driver gives or withdraws consent to automated comparison in the App (Profile) or by writing to the Controller. Drivers can still work with us if they withhold or withdraw consent — verification is then performed manually.
Reference photographs, all verification photographs and document copies are stored in secure, encrypted infrastructure (Google Firebase Storage) for the period required by law (see section 9).
DRIVER Automated facial comparison (with the Driver’s consent) is a partially automated process. It does not produce effects based solely on automated processing within the meaning of Article 22 GDPR — where the result is negative or inconclusive, the matter is decided by a dispatcher (manual verification). The Driver has the right to request human intervention, express their point of view and challenge the result.
DRIVER Automatic account blocks (expired documents, overdue identity verification, Wallet debt below the specified threshold) arise from legislation or the cooperation agreement and end when the cause is remedied. Any block may be appealed to the Controller.
We do not sell personal data. We may share data with the following categories of recipients, including for processing on our behalf, only as necessary to provide the service:
Firebase/Google services may collect limited technical and diagnostic data (e.g. error and stability information, installation identifiers) to ensure that the App operates correctly and securely.
Facial comparison (Amazon Rekognition) takes place within the EEA (Frankfurt). Some Google services may involve transferring data to countries outside the EEA, including the USA. These transfers use appropriate safeguards: Standard Contractual Clauses (SCCs) and, where applicable, the EU–US Data Privacy Framework.
DRIVER Driver Wallet top-ups are processed by the external payment provider PayU S.A. Payment instrument details (e.g. card number, BLIK data) are entered and processed directly by PayU in accordance with its privacy policy; neither the Controller nor the technology provider stores full payment card details. The App stores only the data necessary for settlement (amount, status, transaction identifiers, balance).
DRIVER Wallet Funds are paid out by transfer to the bank account specified in the cooperation agreement. Account details are entered by the Controller; they are visible to the Driver and dispatch staff handling payouts and are emailed to the Controller’s office with the payout request.
PASSENGER The journey is paid for in cash to the Driver or by a cashless method on terms agreed with the Controller. The App does not collect payment card details from the Passenger.
When we process your personal data, you have the right to:
To exercise your rights, please contact: taptaxipl@gmail.com.
We apply technical and organisational measures appropriate to the risk, including encrypted data transmission (HTTPS/TLS), access controls based on security rules, server-side validation of financial transactions and identity verification, prevention of the deletion of legally required records, Firebase App Check / Play Integrity to prevent abuse, and secure password storage by the authentication service.
The App is intended only for adults aged 18 or over; Drivers must be at least 21. Our services are not aimed at children, and we do not knowingly collect their data. If we learn that a minor’s data is being processed without the required consent, we will delete it.
Users may delete their account at any time through the App or by contacting the Controller at taptaxipl@gmail.com. Deleting the account results in the deletion of data, except for data we must retain by law — in particular the booking register, records, Drivers’ verification photographs and document copies, and settlement data (see section 9).
We reserve the right to update this Policy, particularly following changes to App features or the law. The current version is published at this address, together with its last updated date. Detailed rules for using the App are set out in the Passenger Terms and Conditions and Driver Terms and Conditions.
This section covers the taptaxi.pl website. The rest of this document describes the mobile app.
The website may display advertisements through Google AdSense (Google Ireland Limited) in the future. At the time this information was published, AdSense advertisements had not yet been enabled. Once enabled, Google and its partners may use cookies or similar technologies, depending on the consent given and the available settings, to display advertisements, measure their effectiveness and prevent abuse.
Google’s consent management platform (CMP) is being implemented on the website for users in the European Economic Area, the United Kingdom and Switzerland. Once the consent message is activated, users may consent, refuse consent or manage their choices. Google may add a link on an approved website to reopen consent settings. Adding the AdSense script needed to support the consent message may cause connections to Google servers, even when automatic advertisements are disabled. The verification meta tag and ads.txt file alone do not enable advertisements.
More information about how Google uses information: How Google uses data from sites and apps that use our services. Information about advertising settings: My Ad Centre.
Before advertisements are enabled, this information must be supplemented with details of the technologies actually used, data retention periods and the correctly identified website controller.