Your privacy matters.

Effective: 24 October 2026. Operator: Passo Mobility, Ethiopia. Privacy contact: thailu70@gmail.com. Service support: info@passo.live.

Information we handle

Account and application information: name, phone number, email where supplied, account role, company association, hashed password, verification status, route choices or proposals and proposed monthly vehicle fee.
Driver and company verification: driving licence and vehicle details, registration and insurance documents, identity or business documents, profile photo and emergency contact details that you provide. Please tell your emergency contact before sharing their information.
Travel and payments: subscriptions, routes, assigned vehicle and driver, ticket and seat details, boarding records, payment amount, status and provider references. Guest intercity booking also uses the passenger name and phone supplied with the booking.
Location: driver GPS coordinates, timestamp, speed where available and departure-location checks when you enable the relevant features and grant permission. Location supports arrival information, vehicle tracking and boarding checks. Background sharing, when enabled, uses an ongoing Android notification and can continue while the app is minimized. You can stop sharing in the app, sign out, or revoke location permission in your device settings; some driver functions then become unavailable.
Service and security information: support complaints, verification attempts, IP address and server request/security logs. Server logs are configured to omit passwords and redact recognised sensitive query parameters.
QR-scanner technical data: the Google ML Kit barcode-scanning SDK processes camera images on your device. The SDK also sends installation identifiers, device and app information, and SDK performance, event and error information to Google for diagnostics and usage analytics. This technical collection is separate from the boarding token decoded from a QR code, which Passo sends to its server for validation.

How we use it

We use this information to register and verify accounts, review transport applications, assign transport, issue and validate boarding passes, process and reconcile payments, send service or verification SMS messages, provide vehicle arrival information, respond to support requests, and protect the service against abuse. GPS permission is optional at the device level, but it is required for driver location-dependent functions.

Who receives information

Authorized Passo administrators and the relevant transport company receive information needed to review applications and operate their transport service. Assigned drivers receive the passenger and boarding information needed for their journey. Passengers receive relevant assigned-driver contact, profile and vehicle information.
Our SMS provider (Afro Message) receives the destination phone number and message needed for verification and transport notifications. Payment providers, including Telebirr where configured, receive the payment information needed to process a transaction. Their own privacy policies also apply to information processed in their services.
The hosting service supporting our VPS processes server data. OpenStreetMap map services may receive network requests, including IP address and requested map areas, when maps load. We may also disclose specific records when needed to comply with applicable obligations or investigate fraud, safety incidents or disputes.
Google receives the ML Kit technical data described above over HTTPS. Camera images used for QR recognition are processed on the device; this does not describe profile photos or documents that you separately choose to upload to Passo. See Google's ML Kit data disclosure and Google's privacy policy for its handling of SDK data.

Verification documents are served through authenticated access controls. A profile photo is different: it may be shown to your assigned transport participants after approval. Do not upload unrelated personal records.

Retention and account deletion

You can start deletion in the Android app under Privacy & account, or use the public account-deletion page. Sign in, review the consequences, enter your current password and confirm deletion. You do not need to reinstall the app to use the web page.

Account closure removes sign-in phone and email, replaces the password with an unusable value, removes live profile and emergency-contact details, and removes uploaded private documents. It cancels current subscriptions and boarding passes, stops account access and removes the driver's current live vehicle location. A failed physical-file deletion remains in a retry queue until cleanup succeeds; the closure receipt reports this status.

We retain a non-login account identifier and deletion receipt. Historical payment/refund records, journey and safety records, existing complaints and security audit records may remain where needed for accounting, fraud prevention, safety, disputes or applicable obligations. The deletion flow lists these categories before confirmation. Deletion does not automatically issue a refund. Backup copies can remain until replaced; after a restoration, deletion records must be reapplied. We do not promise a retention period that has not been established for a particular record.

A driver with an active trip or assigned paid passengers, or a company with active drivers or committed journeys, needs an operational handover before automatic closure. The deletion screen explains the blocker. Contact the privacy team to arrange closure without disrupting other people's transport. Administrator account closure requires a handover.

Guest intercity tickets are separate from app accounts. For deletion of a guest booking or other retained information, email the privacy contact with enough information to identify the request. We may ask for proportionate ownership verification. Do not email passwords, OTP codes or identity-document images unless a secure verification method has first been agreed.

Your choices and security

You may request access, correction or deletion through the privacy contact. You can manage location permissions in Android settings and update available account information through the service. Network access uses HTTPS. Passwords are stored as hashes on the server; access restrictions and verification gates help protect private records. No system is risk-free.

Adults-only use and children’s transport

You must be 18 or older to create a Passo account or use the Passo app and account portals. Children must not create or use their own Passo accounts. A parent, guardian or authorized adult institution representative may arrange transport for a child and manage the necessary passenger details. A child receiving transport is a transport beneficiary, not a child account user. Contact the privacy team about access, correction or removal of a child's transport information, or if you believe a child has created an account.

Policy changes

This policy is updated when the service or its data handling changes; the effective date above identifies this version.