BogBus — Privacy Policy

Last updated: April 2026
The short version: BogBus doesn't collect anything about you. There are no accounts, no analytics, no advertising SDKs, no telemetry, and no third parties sniffing around. Your phone, your data, your business.

What BogBus collects

Nothing. BogBus does not create accounts, does not require sign-in, and does not transmit any personally identifying information to any server operated by us or by anyone else.

Location

BogBus uses your device location only to find the nearest bus stop and to start the dwell timer when you arrive within twenty-five metres of your selected stop. Location data is processed entirely on your device. It is never transmitted, logged, or stored beyond the running session.

You can revoke location permission at any time via the iOS Settings app. The app will continue to work; you'll just need to pick stops manually from the picker.

Network requests

BogBus makes network requests to two categories of service:

Real-time bus data. Live vehicle positions and trip updates are fetched from a caching proxy operated by the developer, which in turn pulls from the National Transport Authority's public GTFS-Realtime feed once per minute. Your device sends only the standard HTTP request — no identifiers, no tokens, no location coordinates.

Stop weather. Current conditions and the 15-minute precipitation forecast for the bus stop you've selected come from Open-Meteo. The request includes only the latitude and longitude of the selected bus stop — never an identifier.

User-location rain. A separate Open-Meteo request fetches the 15-minute precipitation forecast for your actual location, so the rain warning in the focused-bus panel can warn you about getting wet on the way to the stop. The request includes only the rounded latitude and longitude of your device — never an identifier, never combined with anything else, never persisted server-side. If you deny location permission, this request never fires.

Local storage

BogBus stores a small amount of data on your device using standard iOS app storage (UserDefaults):

• The ID of your most recently selected stop, so the app remembers where you left off.

• A per-stop visit count, so the app can quietly judge you for standing at the same pole eighteen times this month.

• The location coordinates of the last stop where a visit was counted, used purely to detect when you've moved more than five kilometres away.

None of this data ever leaves your device. Deleting the app removes all of it.

Analytics, tracking, and advertising

BogBus contains no analytics frameworks, no crash reporters, no advertising SDKs, no attribution networks, no fingerprinting, and no tracking of any kind. There is no Firebase, no Google Analytics, no Facebook SDK, no Mixpanel, no Amplitude, no anything. The compiled binary contains no third-party tracking code whatsoever.

Children's privacy

BogBus does not collect data from anyone, including children under 13. The app is suitable for all ages, though the commentary occasionally leans into mild existential despair about Irish public transport.

Third-party services

The only external services BogBus communicates with are:

National Transport Authority of Ireland — for real-time GTFS data, via the developer's caching proxy.

Open-Meteo — for weather and precipitation forecasts.

Each of these services has its own privacy policy. BogBus has no commercial or data-sharing relationship with either of them; it simply consumes their public APIs.

Data sales and sharing

BogBus has no data to sell because BogBus collects no data. Even if it did, it wouldn't sell it. The whole point of the app is to be the opposite of that.

Changes to this policy

If this policy changes, the updated version will be posted here with a revised date. The principle — collect nothing, transmit nothing — will not change.

Contact

Questions about this privacy policy can be raised on the BogBus GitHub repository. There is no email contact form because there is no data to dispute.

← Back to BogBus