Privacy policy

For the iOS app KongBus (港巴士), bundle com.japality.hkbus.

Last updated: 29 August 2026 · Developer: Japality

KongBus is a client-only app. Japality does not run accounts and has no app server that receives your trips or location history. The app queries public Hong Kong APIs from your device.

1. What we collect

Japality does not run accounts, does not sell your favourites or trips, and has no server of ours that receives that data. The app never asks you to register an email or phone number.

To show one limited-ad banner on Me, Google AdMob may process device and ad-interaction data — see section 6. Japality does not hand your exact arrival queries or ride history to the ad network.

2. Location

If you grant When In Use location, the app uses it on the device to show nearby stops, centre the map, walk to a stop, plan a journey, and update ride progress.

Location is not uploaded to a Japality server (there is none). When you search a walking route or a place name, coordinates are sent to the relevant Lands Department public APIs. Arrival queries usually send a stop or route id, not a continuous track of your movements.

You can deny location. The app still works. The map shows a Hong Kong overview and does not pretend you are somewhere else.

Ride progress updates only while the app is open. We do not use location in the background, and we never ask for Always location.

3. Data sent to third parties

To show arrivals, maps and traffic news, your device may call public endpoints such as:

Those requests include technical data such as IP address and User-Agent, handled under each organisation’s own policies. Japality cannot control third-party server logs.

4. Data stored on your device

If iCloud or device backup is on, these local settings may be included. You can clear cache or favourites in the app.

5. Notifications and Lock Screen

KongBus does not send ride notifications and does not show ride progress on the Lock Screen or Dynamic Island. The ride screen stays in the app.

6. Advertising (Google AdMob)

Me may show one AdMob banner (about 320×50) at the top. If it fails to load or consent is missing, no space is reserved. Nearby, Map and Go have no ads.

The app does not request App Tracking Transparency (ATT) permission, does not access the IDFA, and does not track you across apps or websites. Every ad request is forced to limited-ad and non-personalized treatment. Google Mobile Ads personalization treatment and the publisher first-party advertising ID are also disabled.

Limited ads do not mean no data processing. Google serves the ad and may process the following to deliver it, prevent invalid traffic or fraud, and maintain security:

The app does not attach the precise location you grant for Nearby, walking or rides to an ad request. Limited ads are not selected using your past behavior in other apps or websites.

Japality does not sell your favourites, rides or exact arrival queries to advertisers. We do not send trip history to our own server.

Users in applicable regions such as the EEA, UK and Switzerland may first see Google’s consent form (UMP). Regardless of that choice, the app only requests limited ads; Google might not be able to serve an ad. You can change Google consent under Me → Ad privacy options when that row is shown. This option never enables personalized ads or IDFA.

The app is not directed at children under 13. Ad content is capped at Teen. See the Google Privacy Policy and AdMob help.

There is no Firebase Analytics or other extra analytics SDK.

7. Children

The app is for general transit use. It is not directed at children under 13 and ads are not treated as child-directed. Ad content is capped at Teen.

8. Your choices

9. Changes

If our practices change in a material way, we will update the date on this page. The latest version at this URL applies.

10. Contact

Developer: Japality
Website: https://app.japality.com/hkbus/i/marketing/
Support: https://app.japality.com/hkbus/i/support/
This policy: https://app.japality.com/hkbus/i/privacy_policy/en/