Privacy policy

Information we receive

When you visit the website

The site is a static content site. When a page, image or demo video is requested, the hosting, delivery and media providers may receive ordinary technical information such as your IP address, browser and device details, referring page, requested URL and the time of the request. This information is used to deliver the site, protect it from abuse and keep it working. We do not use it to build visitor profiles.

The site does not intentionally set analytics or advertising cookies. Links to Apple, email providers and other websites take you to services with their own privacy practices.

When you use the app

• Location. If you grant permission, the app uses precise location on your device for the map, nearby stops, nearest-favourite widgets and location-based alight reminders. If you ask for transit directions, the selected start and end coordinates are sent to our backend and forwarded to OneMap to calculate a route. We do not keep a continuous location history or use location for advertising.
• Local preferences. Favourites, saved services, recent selections, settings, optional home-location details, widget preferences, reminder settings and similar information are stored on your device or in the app group used by its widgets.
• Transport requests. To return bus arrivals, routes, MRT information and traffic data, the app sends the request details needed for that feature, such as a bus stop code, service number, route coordinates, selected date or time. Our API and the public transport providers it uses also receive normal network metadata.
• Operational logs. Our API may log an IP address, user-agent, request path, query parameters, response status and timing to diagnose outages, prevent abuse and improve reliability. A bus-arrival request can therefore include its bus stop code and service number. These logs do not include request bodies and are sent to Axiom and Firebase/Firestore through our logging services.
• Notifications and Live Activities. If you enable notifications or Live Activities, the app sends an Apple push device token, an optional Live Activity push-to-start token, device type, system version and app version to our backend. We store these details with our infrastructure provider so we can deliver and manage the requested notifications.
• Product analytics. BusSing uses PostHog for product analytics. Depending on the feature, it may receive screen and feature events, purchase and paywall events, app version, build number, iOS version, device model and other broad usage details. The app's analytics code excludes search text, coordinates, address details, feedback text and push tokens from event properties.
• Purchases. Apple handles App Store payments. To check BusSing Express access, RevenueCat may process an anonymous app user identifier, product and purchase history, subscription or entitlement status, renewal status and transaction information. We do not receive or store your payment card details or Apple ID password.
• Feedback and support. If you email us, we receive your email address and the message you choose to send. In-app feedback can include your message, app version and device token. Arrival feedback can also include the relevant bus stop code, service number, arrival details and the time of the report. The in-app feedback board is provided by UserJot and may process what you submit under its own privacy policy.

How we use information

We use information to:

• provide bus arrivals, routes, MRT planning and traffic data;
• show nearby stops and run location-based reminders;
• deliver notifications and operate Live Activities and widgets;
• verify purchases, restore access and manage BusSing Express;
• understand feature use and improve reliability and performance;
• respond to support requests and feedback;
• protect the app and services from abuse; and
• meet legal, accounting and security requirements.

Depending on the situation and the law that applies, we rely on your permission, the need to provide a feature you request, our legitimate interests in running and improving BusSing, and legal obligations. We do not ask for data that is not needed for the feature you choose to use.

Who receives information

We share only what a provider needs for the service it performs. Our providers may change over time, but the current categories include:

• Apple. Apple provides the App Store, payment processing, push notifications, MapKit services and, if you opt in to Apple's sharing settings, analytics and diagnostics.
• RevenueCat. Purchase and entitlement management for BusSing Express.
• PostHog. Product analytics for app features and reliability.
• UserJot. The optional in-app feedback board.
• Hosting and infrastructure providers. Our app backend and data are hosted or processed using providers including Fly.io, Vercel, Render, Supabase and Cloudflare. They support API delivery, storage, notifications, logging and the website.
• Operational logging providers. Axiom and Firebase/Firestore receive limited request logs for reliability, security and debugging.
• Transport data providers. The app uses public or government-backed sources such as LTA DataMall, OneMap and traffic camera feeds to return transport information. Their own terms and privacy notices apply to their services.

We may also disclose information if required by law, to respond to a lawful request, or to protect users, the public, BusSing or our rights. We do not sell, rent or share personal data with advertisers or data brokers.

Purchases and subscriptions

BusSing Express purchases are made through Apple. Apple handles your payment method, billing, refunds and subscription management. Apple and RevenueCat may retain purchase and entitlement records for as long as needed to validate transactions, restore purchases, provide paid access, prevent fraud and meet legal or accounting obligations.

Manage or cancel a subscription in your Apple ID settings. You can also use the restore-purchases option in the app. See the BusSing App Store listing for the current App Store privacy details.

Storage, retention and security

Local app data stays on your device until you remove it, reset the relevant setting or uninstall BusSing. Requests and device tokens are kept only while needed to provide the requested feature, operate the service, investigate abuse or meet legal requirements. Feedback, support messages and analytics are kept for the period needed for those purposes and then deleted or de-identified where practical.

We use HTTPS for network connections and reasonable technical and organisational measures to protect information in our possession or control. No internet service can promise complete security. Some providers may process information outside Singapore. Where required, we use safeguards intended to provide a level of protection comparable to the protection required by applicable law.

Your choices and requests

• Turn off location in your device's Location Services settings. BusSing will still work without nearby-stop and other location-based features.
• Turn off notifications or Live Activities in your device settings. Contact us if you want us to remove a notification or Live Activity token held by our services.
• Review Apple's Analytics and Improvements settings to control Apple's sharing of diagnostics and usage data. Those settings do not control BusSing's separate product analytics; contact us if you want to ask about that data.
• Email us to request access to, correction of or deletion of personal data held by BusSing, to withdraw permission where applicable, or to ask a privacy question. We may need to verify your identity and some legal exceptions may apply.

If you are in Singapore and your concern is not resolved after you contact us, you can raise it with the Personal Data Protection Commission.

Children's privacy

BusSing is a general public-transport app and is not directed at children. We do not knowingly collect personal data from children. If you believe a child has sent us personal data, contact us and we will review the request.

Changes to this policy

We may update this policy when the app, website, providers or legal requirements change. We will publish the new version here and change the date at the top. If a change is material, we may also point it out in the app or on the website.