This notice describes the iCABS Passenger Android and iOS apps and their connected Passenger web screens. The apps combine device-native journey and map controls with connected booking, account, payment and chat screens; older Android versions use the connected WebView interface. The Driver app has a separate notice.
Who handles your information
ICABS TRAVEL GB LIMITED, trading as iCABS LIVERPOOL, operates the Passenger service. Contact [email protected] about your account, privacy or data deletion. Business information is available at icabstravel.co.uk.
Account and journey information
Your name, email, phone number, customer ID, optional profile image and account status support sign-in, booking, contact and support. We send verification codes through the business email or SMS delivery service. You may also set an optional password after confirming a code to a verified contact. Passwords are stored as one-way hashes, and sign-in attempts are limited. Hashed identity and network identifiers support short-lived password rate limits. Account sessions and a protected remembered-device token keep you signed in. After you log out, the remembered return option requires you to select it; it does not automatically sign you back in.
Pickup, ordered stops, destination, date and time, selected rider name, passenger and luggage requirements, fare, payment arrangement, booking status and journey history support your trips. Information needed to perform a booking is available to authorised dispatch staff and the assigned driver. Please only provide another rider's information when you are authorised to do so.
Location and pickup sharing
With your device location permission, the app uses approximate or precise location to position you on the map and suggest your pickup. When an eligible booking has an assigned driver, pickup-location sharing can send your current location to iCABS and that driver until pickup. It stops when the trip is on board or closed, or when you stop sharing.
An ongoing pickup-sharing service may continue while the app is minimised and shows an Android notification with a stop control. It uses your existing location permission; the app does not request Android's background-location permission. You can stop the service from its notification or change location permission in Android Settings. On iOS, eligible pickup sharing can continue while the app is minimised using an existing location grant, with the system location indicator and an in-app stop-sharing control. The iOS app does not request Always location access on launch. Without location permission, you can enter addresses manually.
Payments
Card and eligible wallet payments are handled through Stripe's payment screens. Stripe processes the full card details; the iCABS wallet displays the card brand, last four digits and expiry and uses Stripe customer/payment-method references. You choose whether to save a card. Authorisations, payment status and captured amounts are associated with the relevant booking. A card authorisation can place a hold before the trip, with capture through the booking completion process; an eligible booking with an outstanding payment can use the central Pay now screen. Existing authorisations are checked to avoid duplicate payment, and Pay now is hidden for completed bookings.
Wallet availability depends on your device and payment provider. The payment provider and relevant bank or wallet provider process the payment information under their own notices.
Messages, files and notifications
Trip chat, support messages and any files you choose to upload are processed to provide journey communication and support. Trip messages are shared with their intended recipient. Chat is disabled once the booking is completed. Driver contact details are hidden from the Passenger history screen one hour after recorded completion.
If you allow notifications, Firebase Cloud Messaging uses a device registration token to deliver trip and message updates. On iOS, delivery also uses Apple Push Notification service. Notification access can be changed in your device Settings. The app's file picker gives access to the items you select, rather than uploading your whole photo library or device contact list.
Maps, providers and technical information
Apple Maps / MapKit provides the native iOS planning map, and Google Maps SDK provides the native Android planning map. Google Maps and the configured address-search and route services support connected screens, address lookup and route calculation. These providers process information needed for those features. Stripe processes payments, Google and Apple provide app and notification services, and the configured business email/SMS services deliver account codes and service communications. Web resources such as fonts and security services can receive ordinary connection information. These providers have their own privacy notices.
IP addresses, app/device versions, session and device identifiers, notification tokens and service/security logs support operation, security and fault investigation. The Passenger apps do not request advertising identifiers and their Firebase Analytics collection is disabled. Descriptions of website advertising or newsletters on other pages do not describe advertising features in this Passenger app.
Operational information is stored on the business server and accessed by authorised staff and service providers for the relevant purpose. A provider may process information outside your country; contact iCABS for information about a particular provider or transfer.
Apple privacy policy · Google privacy policy · Stripe privacy policy
Interface language
Android's optional language setting uses built-in iCABS interface language packs stored in the app. Selecting a language does not send text to a translation provider or download a translation model. Names, addresses, messages, typed form values and payment details are not translated by this feature. Some service, legal and payment-provider information remains in English or follows the provider's own language setting. You can return to English in Account → Language.
Device storage and security
The app uses HTTPS for its business connections, account access controls and protected session storage. The apps retain session cookies, theme settings, recent addresses and rider selections on your device. Home, Work and custom saved addresses can be linked to your customer account. Some other selections remain customer-scoped on that device. The native maps keep small route caches in memory and clear their route history on sign-out. Clearing local app data does not delete server-side booking or account records. No system can guarantee absolute security. Tell support if you suspect that an account has been exposed.
Retention, deletion and your choices
Retention depends on the record and its purpose. Account and booking information supports the service; some journey, payment or security records may remain necessary for legal obligations, fraud prevention, claims, disputes or unresolved payments. Support can explain the information retained, its purpose and applicable retention period. Backup copies follow the business backup lifecycle.
Request account and associated personal data deletion. The request page works without signing in or reinstalling the app. It directs your request to the existing iCABS support email for ownership verification and processing, including relevant service-provider records. Logging out or uninstalling alone does not erase your server account.
You can ask support about access, correction, deletion and other rights applicable to your information. You can withdraw optional device permissions in your device Settings. Some location or notification features will then be unavailable. This Passenger service is not designed as a child-directed app.