Cab24 Fahrer
Driver app for taxi companies and chauffeurs
Privacy policy
Last updated: 5 September 2026
Cab24 Fahrer is a work app for drivers, not for passengers. While a shift is active the app continuously transmits the vehicle’s location — including when the app is closed — so that jobs can be assigned and passengers can track the approach. For payouts we also record your bank details. Card payments run through the Stripe module; the card number never reaches the app or our server.
1. Data controller
- Company
- Babala Özdemir (Einzelunternehmen)
- Address
- Unterer Rainweg 22
4414 Füllinsdorf
Schweiz - info@babala.ch
- Phone
- 076 222 45 99
- Company ID
- CHE-322.105.560
- App identifier
-
iOS: ch.babala.driver.swiftui
Android: ch.babala.driver
We have not appointed a data protection officer or an EU representative because we do not reach the relevant thresholds. Please address all requests to the contact above.
2. What data we process
| Data | Purpose | Stored where | Retention |
|---|---|---|---|
| Vehicle location, continuously during a shift (also while the app is closed) | Job assignment, approach tracking by the passenger, proof of the ride | Our server (EU data centre) | The last position permanently, the trail for 90 days |
| Credentials, name, phone number, vehicle and licence details | Login, dispatch, proof of authorisation | Our server | Until the end of the engagement |
| Bank details (IBAN and account holder), optionally Stripe credentials | Paying out ride revenue | Our server, stored encrypted | Until the end of the engagement; records 10 years |
| Rides, shifts, revenue, tips, ratings | Settlement and quality assurance | Our server | 10 years (accounting obligation) |
| Passenger data of the assigned ride | Performing the ride | Displayed in the app | Until the ride is completed |
| Camera image while scanning the IBAN | Convenient entry of the bank details | On the device only — text recognition runs locally, the image is not transmitted | Only during the entry |
| Push-to-talk recordings and messages | Communication with dispatch, passenger and other vehicles | Our server | At most 30 days |
What we explicitly do not collect
- No location transmission outside an active shift — it stops immediately after clocking out
- No permanent listening: the microphone runs only while the talk button is held
- No card numbers and no CVC codes — the card is read exclusively by the Stripe module
- No advertising, no advertising ID, no analytics SDK
3. Permissions on your device
The app requests only the following permissions. Each of them can be revoked at any time in your device settings; the app remains usable afterwards, with reduced functionality.
- Location, including in the background — Continuous position reporting during a shift. On Android a visible foreground service with a persistent notification is used; on iOS the usual location indicator appears.
- Camera — Scanning IBANs and QR codes. Recognition runs on the device.
- Microphone — Push-to-talk with dispatch and other vehicles — only while the talk button is held.
- Bluetooth — On-device card payment (Tap to Pay).
- Notifications — Alerting you to new ride jobs.
4. Legal bases
We process personal data under the Swiss Federal Act on Data Protection (revFADP). Where the GDPR applies, we rely on:
- Performance of a contract (Art. 6(1)(b) GDPR) — everything needed for the app to deliver the function you requested.
- Legitimate interests (Art. 6(1)(f) GDPR) — secure and stable operation, abuse prevention, troubleshooting.
- Consent (Art. 6(1)(a) GDPR) — for anything you actively enable in this app: location during a shift, the camera for IBAN and QR capture, the microphone for push-to-talk, Bluetooth for card payments and notifications about new ride jobs. Consent can be withdrawn at any time with effect for the future by revoking the permission in your system settings.
- Legal obligation (Art. 6(1)(c) GDPR) — in particular commercial and tax retention duties for payments.
Location transmission is based on performance of the engagement or employment relationship and on the legitimate interest in functioning dispatch. It happens only during an active shift and is not used to monitor behaviour at work within the meaning of Art. 26 of the Swiss Ordinance 3 to the Labour Act.
5. Recipients and third parties
We do not sell data and do not disclose it for advertising purposes. Data is disclosed only to the following parties, and only where required for operation:
| Recipient | Location | Purpose |
|---|---|---|
| Hetzner Online GmbH | Gunzenhausen (Germany), data centre inside the EU | Operation of our servers. Hetzner processes data solely on our behalf and is contractually bound to confidentiality. |
| Stripe Payments Europe Ltd. / Stripe Inc. | Dublin (Ireland) / San Francisco (USA) | Card payment processing. Card data is collected by Stripe directly; we never receive or store full card numbers, only payment references (tokens), amount, status and the last four digits. |
| Firebase Cloud Messaging (Google Ireland Ltd.) | Dublin (Ireland) | Delivery of push notifications to Android devices. A device token and the message content are transmitted. |
| Apple Push Notification service (Apple) | Cork (Ireland) / USA | Delivery of push notifications to Apple devices. A device token and the message content are transmitted. |
| Apple MapKit | Cork (Ireland) / USA | Map rendering. When loading map tiles Apple receives the IP address and the visible map region. |
| OpenStreetMap Foundation | Cambridge (United Kingdom) | Map rendering. Loading map tiles transmits the IP address to the tile server. |
| Apple Inc. / Apple Distribution International Ltd. | Cupertino (USA) / Cork (Ireland) | App Store distribution, processing of in-app purchases and subscriptions, and crash reports if you have enabled them with Apple. |
| Google Ireland Ltd. / Google LLC | Dublin (Ireland) / Mountain View (USA) | Google Play distribution, purchase processing via Google Play Billing, crash reports according to your Play settings. |
Authorities and courts receive data only where we are legally obliged to provide it.
Transfers abroad
Some of the recipients listed above process data outside Switzerland and the EEA, in particular in the United States. We base such transfers on the European Commission’s Standard Contractual Clauses with the Swiss adaptations recognised by the FDPIC and, where applicable, on the EU-US Data Privacy Framework. We will provide information on the safeguards in place on request.
6. Retention and deletion
The most recently reported position is overwritten; a position trail is kept for at most 90 days. Account and vehicle data remain until the end of the engagement. Ride, revenue and payout records, including the bank details on the record, are kept for 10 years (accounting duty). Push-to-talk recordings are deleted after 30 days at the latest. Server logs expire after 14 days.
Step-by-step instructions are available at Delete data.
7. Children and young people
This app is not directed at children. We do not knowingly collect personal data from children under 16. If we learn that such data has been submitted without parental consent, we delete it without delay.
8. Data security
Wherever the app transmits data at all, connections are encrypted via HTTPS/TLS. On the server side we use access restrictions, tenant separation and regular backups. Nobody can, however, guarantee absolute security for data transmission over the internet.
Bank details are stored encrypted and used only for payouts. In the system they are visible only to you and to the settling office.
9. Your rights
- Access to the personal data we process
- Rectification of inaccurate data
- Erasure or destruction of your data
- Restriction of and objection to processing
- Receiving or porting your data in a common format
- Withdrawal of consent with effect for the future
An informal message to info@babala.ch or a call to 076 222 45 99. We normally respond within 30 days. To verify your identity we may request suitable proof. You may also lodge a complaint with a supervisory authority (Switzerland: FDPIC; EU: your competent authority).
10. Changes to this policy
We may adapt this policy when the app or the legal framework changes. The version published on this page, with the date shown above, is the applicable one. We announce material changes inside the app.
← Back to the app overview