Terms of Use

Role of CroCab

CroCab is a technology and dispatch platform operated by Mobilitas Magna j.d.o.o. It enables ride requests, assignment and tracking. The assigned partner and driver provide the transport service under their own permits and obligations.

Accounts and accurate information

Users must provide accurate, current information and protect their credentials. The same CroCab account and credentials are used in the Android app and the passenger PWA at app.crocab.com; signing in on one browser or device does not automatically sign in another. Users are responsible for activity through their account unless unauthorised access has been reported.

Ride requests, reservations and prices

The signed-in PWA at app.crocab.com provides the same supported passenger booking, price display, reservation, tracking and active-ride management flow as the Android passenger app. A request sent through the separate public form at crocab.com is not a confirmed reservation until dispatch validates the route, details and availability. Reservations may be requested from 30 minutes to 30 days in advance. The English calendar uses English month names, while the selected date is displayed as dd.mm.yyyy with 24-hour time. Check the pickup time and contact details before submitting. The app supports a pickup, destination and up to three ordered intermediate stops. The system automatically uses its recommended road route without offering a route-type choice, and shows the maximum price for the complete sequence before confirmation. The final button states “Order with obligation to pay” or “Reserve with obligation to pay”; pressing it submits the order at the displayed price. The accepted price does not increase because of a wrong turn, traffic conditions or visual navigation rerouting alone.

After a ride starts, the passenger may propose adding or removing future intermediate stops, up to three in total. Completed stops, pickup and final destination cannot be changed. The system recalculates the whole amended route using the already selected category and original accepted tariff calculation, then displays a new total price before any decision. Route and price change only after the passenger explicitly accepts the new offer; rejection or expiry keeps the previous route and price. An accepted amendment is recorded as a revision of the same ride, is shown to the driver immediately and does not create a new ride. No changes are possible after ride completion or fiscal receipt issuance.

Road routes from 100 km to 1,000 km receive an automatic linear discount: 10.00% at 100 km, increasing gradually to 20.00% at 1,000 km. The discount is included in the displayed maximum price and its percentage is shown before confirmation. This discount does not apply below 100 km. App estimates are limited to road routes of up to 1,000 km.

A passenger may save a preference for a cooler or warmer cabin, a quiet ride without conversation and music switched off. These preferences remain saved until changed or cleared and are shown to the driver only after assignment. They are passenger preferences, not unconditional guarantees where safety, weather or the vehicle's technical capabilities require otherwise.

The additional needs “child seat”, “pet” and “package” help match the passenger, luggage and available vehicle with a partner. “Package” means an item carried by the passenger as part of their own ride and is not a separate courier or delivery service.

A ride ordered ahead uses the published day or night advance-booking starting price for the selected category at the scheduled pickup time. The increase is shown and accounted as one combined starting price, not as a separate fee, and is included in the maximum shown before confirmation. The same starting-price rule is applied to a ride entered by dispatch and its connected taximeter.

A driver may claim a reservation in advance. The passenger is notified after acceptance and again when the driver confirms departure. Acceptance by a particular driver does not guarantee that the same driver will perform the ride. If departure is not confirmed by the calculated deadline or the driver becomes unavailable, CroCab may immediately return the ride to automatic nearest-available-driver dispatch. CroCab will try to find a replacement, but vehicle availability cannot be unconditionally guaranteed in circumstances outside the reasonable control of the platform and partner.

For an on-demand ride, CroCab searches for an eligible driver for no more than 10 minutes per attempt. If none is found, the passenger may stop or start no more than two additional ten-minute attempts, and may cancel before the search expires. An explicit driver rejection sends the offer onward; after the third rejection of the same ride, that driver is automatically taken offline. Returning an already accepted ride to dispatch is a separate operational action and does not count as an offer rejection.

Incident, continuation and ending the service

After a ride starts, the driver and vehicle cannot be changed through the ordinary flow. If a collision, breakdown, safety event or another justified incident occurs, the driver freezes the leg and sends confirmed data to CroCab. The passenger may continue the same service with another active and eligible CroCab driver or end it at the incident location. A driver of any active CroCab partner that accepted the current agreement may continue it, including an owner-driver with no employees. Outside drivers are not used.

A replacement search lasts no more than 10 minutes per attempt. The passenger may request no more than two retries or stop waiting at any time and move to calculation and payment for the service already performed.

If the passenger ends the service after an incident, the system immediately shows the server-calculated amount and requires a cash or card selection. The passenger must pay that amount. For a pre-priced platform ride, the amount uses the originally accepted tariff and confirmed distance and duration; the starting price is applied once, the original discount remains, and the total cannot exceed the accepted price. A Taximeter service uses the total of confirmed legs under the Taximeter rules. If collection fails or is refused, the full calculated amount remains recorded as payment due; it is not marked paid or reduced to EUR 0.00.

Receipt

The entire linked service, including all incident legs, has one passenger receipt, one original billing partner and one CroCab commission. A partner that performs or collects a continuation is recorded separately for internal settlement without changing the passenger-receipt issuer. A standard PDF and an A4 view may be available for that same fiscalised receipt. Both have the same fiscal identity, amount, ZKI/JIR data and issuer; the A4 view does not create another receipt.

Cancellation and safety

A passenger may cancel before the ride starts. After it starts, the ride ends through ordinary completion or the controlled incident process with calculation of the performed part. Any special condition or fee must be displayed before confirmation. Passengers and drivers must act safely, lawfully and respectfully. CroCab may keep a driver offline until an operational or safety review is completed and may restrict access to protect the system and its users.

Ratings and comments

After a completed ride, passengers and drivers may submit relevant, truthful feedback. CroCab may review or hide reported, abusive, discriminatory or unlawful content.

Complaints and support

Use the Complaints page for issues concerning the CroCab platform. Questions about transport or a fiscal receipt may also be directed to the partner shown in the completed ride.

Changes

Terms may change due to product development, regulation or security. Material changes receive a new version and, where required, must be accepted in the app.

Receipts and subsequent nonpayment reports

Issuing and fiscalising a receipt are separate from confirming receipt of money. A completed and processed service receives its receipt; any nonpayment is reported against that receipt. Passengers pay the stated amount and may send Admin an objection or evidence of previous payment. Passenger and driver communication about this incident is mediated by Admin. Confirming later collection does not issue another receipt or change its fiscal identity. Where the actual payment requires a different payment method on the receipt, the issuer and Admin must follow the prescribed invoice correction process.

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).