Cab24
Book a taxi — passenger app
Privacy policy
Last updated: 5 September 2026
Cab24 arranges taxi rides. For a vehicle to reach you we need your phone number and the pickup and destination locations. We pass this to the driver who accepts the ride. Card payments are handled by Stripe: your card number never reaches the app or our server. Your location is used only while you use the app — there is no background tracking.
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.kunde.swiftui
Android: ch.babala.kunde
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 |
|---|---|---|---|
| Name, phone number, optional e-mail address, password (hashed) | Account, login, contact at pickup | Our server (EU data centre) | Until you delete your account |
| SMS login code | Passwordless login and verification of the phone number | Our server; sent by SMS | A few minutes |
| Pickup and destination, stops, coordinates, ride options and notes | Arranging and performing the ride, price calculation | Our server; passed to the performing driver | Ride records 10 years; other data until account deletion |
| Location while using the app | Centring the map, suggesting the pickup point, showing nearby vehicles | Device; as pickup point on our server | Only while in use, or stored with the ride |
| Messages and voice messages (shared rides only) | Communicating with the driver | Our server | Until the ride is completed, at most 30 days |
| Ratings, tips, favourites (e.g. “home”, “work”) | Quality assurance and faster ordering | Our server | Until you delete your account |
| Payment data | Paying for the ride | At Stripe; with us only amount, status and reference | 10 years (accounting obligation) |
| Device push token | Notifications about the ride status | Our server; delivery via Google or Apple | Until the device is signed out |
What we explicitly do not collect
- No location tracking in the background or while the app is closed
- No eavesdropping: the microphone is used only while you hold the push-to-talk button
- No SMS reading: the login code may be offered by the system, but the app never reads messages
- No card numbers, 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 while using the app — Suggesting the pickup point and showing nearby vehicles. You can also enter the pickup point manually.
- Microphone (optional) — Push-to-talk on shared rides — only while you hold the talk button.
- Notifications — Ride status: accepted, on the way, arrived.
- Camera and photos (iOS only, optional) — Choosing a profile picture and scanning a card for payment.
- Internet — Communication with our server and loading the map.
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 while using the app, the microphone for push-to-talk, notifications about the ride status and camera and photo picking on iOS. 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.
The driver who accepts your ride receives your first name, phone number, pickup and destination and your ride notes, and is responsible for further processing.
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
Account, address and ride data remain until you delete your account. Ride records and receipts must be kept for 10 years (accounting duty); after account deletion they are detached from your account. Messages and voice messages are deleted at the latest 30 days after the ride ends. 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.
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