Your movement should not become everybody's business.

Scope

Who and what this notice covers.

This notice applies to the Yellow Yellow mobile apps, public website, internal release preparation and planned founding feedback services for passengers, drivers and vehicle owners in Ghana.

Information collected

Only information connected to a defined service need.

All account holders

• A verified phone number used privately for sign-in, verification, account security and recovery, together with account identifiers, device session and security records.
• Name and profile details supplied during setup, including an optional passenger or owner profile photo.
• Support, safety, complaint and feedback information you choose to provide.

Passenger and trip information

• Pickup, destination, live trip location, route, fare, payment method and ride status.
• Saved places and recent destinations associated with your trusted account.
• Trip and nearby-conversation messages, fare proposals, acceptance records, call-request history, unread/read status, ratings and review information where enabled. Counterparties see permitted names, roles or private aliases, not one another's authentication phone numbers.
• An optional trusted-contact name, phone number and revocable live-trip link record when you enable sharing.

Driver and vehicle information

• Driver profile, vehicle registration relationship, vehicle type and colour.
• A clear driver recognition photo shown only to the matched passenger during an active ride.
• The configured primary operating area used to limit normal pickup assignments.
• Private driver's-licence, motor-insurance and roadworthy images, declared expiry dates, validation results and human-review records for every submission.
• Driver location while online or completing an authorised trip, plus trip and assignment history.

Owner and commercial information

• Owner profile and lawful relationship to linked vehicles and drivers.
• Account-bound access periods, payments, receipts, reversals and reconciliation records.
• For controlled system tests and the planned capped feedback cohort: invitation, approved roles, participation status and whether the record is a real participant or an excluded system-test account.
• Driver-approved linked-vehicle movement and aggregate completed-trip and quoted-fare totals during an active 24-hour consent window.
• Monitoring requests, decisions, expiry and revocation records used to prove consent.

Purpose

How Yellow Yellow uses information.

• Verify accounts, protect one-active-device sessions and control access to passenger, driver and owner tools.
• Find nearby available drivers, calculate routes and fares, assign rides and show trip progress.
• Help a matched passenger recognise the assigned driver without recurring selfie checks or biometric face matching.
• Support trip communication, safety review, incident handling, fraud prevention and dispute resolution.
• Provide vehicle and document-expiry reminders without replacing state-agency enforcement.
• Keep external participation paused now, then restrict the planned free feedback cohort to invited people, enforce its real-participant cap and prevent role or account sharing.
• Prepare future account-bound access, receipt and accounting controls after company merchant onboarding without collecting access payments during the first feedback cohort.
• Measure reliability, demand, growth and service quality using aggregated or minimised information where possible.
• Improve accessibility, pricing fairness and product decisions under documented AI and human-approval rules.

Yellow Yellow does not set a passenger's fare from their inferred income, phone model, neighbourhood, urgency, disability or another private personal characteristic.

Location

Live location has strict boundaries.

Passenger location helps set pickup, display nearby drivers, route the assigned vehicle and support trip safety. Driver location helps match requests, navigate to pickup and destination, and show authorised trip progress.

• The current build uses foreground location for idle Online availability and separately permissioned background location for an active authorised trip. Locked-screen idle availability is planned, not yet supported. Any expansion requires updated disclosure, permissions and testing.
• Before booking, nearby Driver markers use reduced location precision. Exact pickup is disclosed to the assigned Driver after mutual ride acceptance, not merely because a marker is tapped.
• A passenger sees the assigned vehicle's relevant approach and trip progress, not an unrestricted driver history.
• An Owner sees linked-vehicle movement and aggregate trip/quoted-fare totals only after a fresh Driver decision and only for the next 24 hours.
• The Driver may decline or revoke Owner monitoring; it never renews automatically.
• A Passenger or Driver may create a live-trip link for a trusted contact. The app opens the phone's share sheet and never sends the link automatically.
• Trusted-contact links expire when the trip ends, when revoked, when the user changes the sharing preference, or at their maximum safety timeout.
• After a passenger's trip starts, the passenger app stops repeatedly requesting or drawing route paths under the founding cost-control design.

Service providers

Information is shared only for a defined function.

Ordinary in-app communication uses permitted names, roles or private aliases rather than authentication phone numbers. Routine staff dashboards and document-review queues also omit authentication phone numbers. The cellular-calling option being prepared for the next release is different: a Driver chooses whether to share their verified contact number for eligible ride enquiries, and a Passenger sees a notice before opening the phone dialler. The caller's number may be visible to the Driver. Numbers and call records may remain on either phone or with the network operator, outside Yellow Yellow's control.

For the planned cellular route, a Passenger chooses separately whether to share a pickup location after the call. Tapping a vehicle or opening the dialler does not itself share the exact pickup. Keep mobile data on for app updates and pickup sharing. Yellow Yellow does not record cellular calls; network charges and the network operator's terms apply. In-app internet audio and recording are not part of the planned cellular launch. Limited app interaction or call-request metadata does not prove that a cellular call connected or record its contents.

Yellow Yellow may use service providers for cloud hosting, maps and routes, SMS verification, push notifications, app distribution, security, analytics and professional legal or accounting support. Payment providers may be added only after approved company onboarding; no access payment provider receives feedback-participant payment data during the current hold or planned free first cohort. Each provider should receive only the information needed for its authorised role.

Authorised staff review transport documents. Automated AI document screening is not used, and transport-document images and declared fields are not sent to AI providers for review.

Information may also be disclosed when required by lawful authority, to protect a person from serious harm, to investigate fraud or a safety incident, or as part of a legally governed business transaction. Yellow Yellow does not sell private trip or identity information for advertising.

Retention

Keep what is necessary, then delete or anonymise it.

Retention depends on the information's operational, safety, dispute, accounting, tax, fraud-prevention or legal purpose. Yellow Yellow is documenting a formal retention schedule before unrestricted launch.

• Recent passenger destinations are designed to expire after a limited period unless deliberately saved.
• Financial and tax evidence may be kept for legally required periods.
• Capped-pilot invitation, approved-role and participation records may be retained to prove the cap, investigate abuse and evaluate the pilot.
• Identity and safety records require stronger access restrictions and purpose review.
• Aggregated or anonymised statistics may be retained when they no longer identify a person.

Security

Layered protection, not a single password.

Yellow Yellow uses phone verification, device-bound revocable sessions, role-based access, private storage, encrypted or protected sensitive fields, database constraints, audit records and controlled administrator functions. No system can promise absolute security, so suspected incidents are contained, assessed, documented and escalated under the breach-response process.

Never send OTP codes, payment secrets, profile photos, identity documents or private trip details through the public-information assistant or public social channels.

Your choices

Access, correction and account concerns.

Subject to applicable Ghanaian law and proportionate identity verification, users may request access to relevant personal information, correction of inaccurate records, deletion where no overriding retention duty applies, or review of an account or automated outcome.

A signed-in user can choose Delete account on the app's Account screen. Access then closes on every trusted phone, live Driver availability is removed, and the account enters a controlled erasure and retention review normally due within 30 days. The separate account-deletion page explains the process and provides a route for users who cannot sign in.

Some location permissions may be managed through the phone's settings, but disabling required location access can prevent nearby-driver discovery, driver matching or live trip functions.

Requests & contact

Use a monitored channel for privacy and support requests.

Email support@yellowyellowmobility.com and put Privacy request in the subject, or call +233 24 291 3171, +233 55 584 9302 or +233 24 207 5603. For account closure, use the in-app control or the account-deletion request page. During invited testing, you may also use the in-app support route supplied with the pilot instructions.

House No. GU207, Kanvili Kpawmo St, Tamale, Northern Region, Ghana. GhanaPostGPS: NS-190-0483. Postcode: NS-190.

On this public website, the Public Information Agent can explain approved privacy principles but receives no account context: the website does not sign you into an account or receive an app session token. In the signed-in app, a verified account session may use a limited read-only summary of only that person's own access, onboarding status and aggregate usage. It never displays exact routes, another user, document or chat contents, or payment records; it cannot authenticate data-rights requests or decide a private account matter. Public-information logs retain a category marker instead of the original question, and personalised self-guidance answers are not retained.