CroCab Driver · Mobilitas Magna
CroCab Driver Privacy Policy
This translation is provided for convenience. The Croatian text is authoritative.
This policy covers the CroCab Driver app and authorised driver accounts, including a partner owner who drives personally.
Controller and sources
Mobilitas Magna operates the CroCab platform. Authorised administration creates and approves driver accounts; the app has no public registration. Information comes from you, the partner enrolling you, app use, related rides and requests. The transport provider separately handles its duties as employer, carrier and receipt issuer.
Information and purposes
- Identity and access: name, contact information, user identifiers, sign-in and account-security details.
- Eligibility: partner, vehicle, registration, categories, status and documents/permits supplied by you or the partner; a profile photograph if provided.
- Work and rides: online status, offers and responses, pickup, destination, route, time, distance, taximeter, completion, incidents, payments, receipts, settlements and commissions.
- Communication: ride messages, ratings, comments and support reports.
- Device: notification tokens and installation identifiers for offers; crash and ANR records, app/OS versions and technical diagnostics.
We process information needed for secure access, assigning and performing transport, communication, settlement, support, preventing abuse and legal duties. The app has no advertising or Firebase Analytics.
Precise driver location, including background use
The driver's precise location is collected and transmitted while online or on an active ride, including when the app is in the background or the screen is locked. It supports offers, arrival, ride tracking, navigation, taximeter and safety. Tracking stops when you are offline and have no active ride. Location is not used for advertising.
The assigned passenger sees your position and information needed to identify the driver and vehicle. Authorised dispatch and your partner have access within their operational roles. A tracking notification is shown, and Android permissions are under your control. Online work requires location access. Contact dispatch to resolve ride, safe shift-completion or technical issues.
Legal bases and operational decisions
Bases include performance of a contract or requested pre-contract steps where you are a contracting party, legal duties and legitimate interests in safe transport, authorised access and handling complaints. Where consent is required, it is requested separately and can be withdrawn. An Android permission alone is not the legal basis for every processing activity.
Offers and work availability depend on location, ride state, document validity, vehicle and partner/platform rules. You can challenge an offer or access restriction and request human review through support.
Taxi driver card verification
For a manual check and before every attempt to go online, CroCab sends the stored seven-digit card number to the official AKD validity-check service. AKD receives the card number and technical network-request data; we do not send ride, location, passenger, payment or communication content.
CroCab records whether the result is valid, invalid or temporarily unavailable, the check time, its trigger and a security fingerprint of the response without retaining the full AKD page. Admin can see the number and status to manage work eligibility; the linked transport partner sees a masked number, status and access-block notification. An invalid card automatically prevents the driver from going online; the driver may request human review and correction. Temporary AKD unavailability does not turn the last confirmed status into invalid, but a new attempt to go online waits for a successful check.
Recipients, security and transfers
The assigned passenger, authorised dispatch and carrier receive information needed for the ride within their roles. Authorities receive information where legally required. Technical services are provided by Supabase, Google Firebase (Cloud Messaging and Crashlytics), Cloudflare and TomTom. For map display, road-access resolution, routing, traffic and ETA, TomTom receives only the required coordinates, ordered route points and departure time when needed for a traffic estimate. All TomTom requests pass through an authenticated CroCab server-side proxy; we do not send TomTom a name, email address, phone number, CroCab account or ride identifier, message content, receipt data or payment data. CroCab uses a copy of official open address and spatial data from the Croatian State Geodetic Administration to verify Croatian streets, house numbers and local-government units; the Administration does not receive an individual app query. Opening external navigation or choosing receipt printing/sharing transfers the details needed for that action to the selected app or printer.
Traffic to CroCab servers uses HTTPS/TLS and access is limited by role. Transfers outside the EEA use an appropriate GDPR mechanism, such as an applicable adequacy decision or standard contractual clauses. Details of recipients and safeguards are available from our contact.
The TomTom API key remains on the CroCab server and is not embedded in the Driver app.
What is deleted, what is retained and for how long?
Deletion covers information whose processing purpose has ended. The accounting retention period does not automatically apply to all GPS history, all messages or an entire profile. Where there is no single statutory period, we use the following criteria:
Driver profile, contact, photograph and documents
Information required for sign-in and proof of eligibility is retained while Driver account access is authorised. After access ends or a valid request, information no longer needed is removed. Only the portion required to evidence a completed service, comply with law or address a specific dispute is retained for the applicable period below. Deleting information essential to the account may end access to the app.
Location, ride status, messages, ratings and support
These are retained while needed to perform the ride or handle the request. Where a specific record is needed for an open complaint, collection, safety incident or legal claim, only the necessary part is retained until the matter is closed and the applicable period to establish or defend that claim ends. Our response identifies the retained records, the reason, and the deadline or event that ends retention. Stopping location transmission does not automatically erase existing records.
Fiscal receipts and accounting documents
Documents underlying entries in the journal, general ledger or subsidiary books are retained for at least 11 years, starting on the final day of the financial year to which the books containing those entries relate. This includes required issuer, operator, service, amount and payment details forming part of the document. Fiscalised structured eInvoices have a special period of six years after the end of the year of issue where the Fiscalisation Act's conditions apply. An ordinary receipt PDF or printout is not, by itself, such an eInvoice. Accounting books and other related records have their own retention requirements.
Diagnostics and notifications
Firebase Crashlytics retains crash records and associated identifiers for 90 days before starting removal from live and backup systems. Requests may cover CroCab notification tokens and device identifiers no longer needed. Firebase retains installation identifiers until deletion is requested through its API; removal from live and backup systems then takes up to 180 days under the provider's policy. These periods are not blanket automatic deletion of all CroCab data.
Limited retention and backups
A dispute or legal retention duty is assessed for the specific record, not used as an unlimited reason to keep all information. Retained information has restricted access; unnecessary links are removed or pseudonymised where possible without changing legally required documents. We send appropriate deletion requests to processors and inform you of the applicable backup cycle and any later completion of removal.
Deletion and other rights
Use the CroCab Driver data-deletion page for request steps, deleted/retained categories and periods, or email crocab@crocab.com. You may request access, rectification, restriction and portability, object where applicable, and contact AZOP.
Sources and applicable rules
Unpaid receipt incidents
After a receipt is issued, the driver may report its amount as unpaid. We process its receipt and ride link, report, collection state, messages to Admin and resolution audit. Registered passengers receive a notification and may send Admin an objection or evidence of payment. A report is not an automatic decision on a dispute. Access is limited to the related passenger, authorised driver, relevant partners and Admin. Passenger, driver and partner messages to Admin use separate conversations. Processing supports service performance, complaints, collection and legal claims. We assess the need and period for retaining each dispute record under the retention rules on this page, and remove or pseudonymise unnecessary information.
Dated campaign benefits
The supplemental discount rules explain eligibility, calculation, long-route priority, account-level usage and associated data processing. They apply when a campaign benefit is displayed and used. Read discount rules (2026-09-05-discounts-v1).