My Bus Stop

Privacy Policy

Last updated 16 November 2026

No account, no ads, no tracking. There's nothing to sign up for, and the app never asks to track you across other companies' apps and websites.

To show arrivals, the app has to ask a transit service. It sends the stop and lines you chose and, when you look for stops near you, your location. It doesn't keep a record of where you've been.

We collect usage statistics and crash reports to find bugs. They aren't tied to your name or email, and they're never used for advertising.

My Bus Stop ("the app") is made by Amir Hayek ("we"). This policy explains what the app sends, to whom, what it keeps on your devices, and how to remove it. It covers the app on iPhone, iPad, Mac, Apple Watch and Apple TV, and its widgets and Top Shelf.

Getting arrival times

The arrival times come from the open, real-time data that transit agencies publish. To show your board, the app asks your region's transit data service for the stop and lines you picked. When you search, what you type is sent so the service can find matching stops.

Most regions are asked directly, from your device, and each service handles the request under its own privacy policy. The app tells you which service your data comes from at the bottom of Settings.

In New York City, Seattle & Puget Sound, Tampa, Luxembourg and Berlin & Brandenburg, the agency requires a key that can't be kept on your device, so the request goes through a small relay we run on Google Cloud (Cloud Functions for Firebase, in the United States). The relay forwards only what the agency needs, such as the stop, the line, your search or the coordinates for stops nearby, and keeps the agency's reply in memory for between 10 seconds and an hour so repeat requests are faster. Bus positions in Ljubljana, and bus positions and route maps in Stockholm, come through the same relay; for those it is sent only the line. In Taipei, the relay downloads Taipei City's whole-city bus files for everyone, at most every 20 seconds (the stop list every six hours), and answers with the stop or line you asked about, so nothing about your request reaches Taipei; stops nearby are found on your device from the stop list. Its own logs don't record coordinates, stops or searches. Google Cloud's standard request logs may record the address that was requested and your IP address, and are kept according to Google Cloud's retention settings.

Your location

The app asks for your location only while it's open, and only when you choose to use it. It's used to pick your region, to show you on the map, and to find stops nearby, which means sending your coordinates to your region's transit service (through the relay above in New York, Seattle, Tampa, Luxembourg and Berlin & Brandenburg). The app takes one reading at a time and doesn't store it. On Apple TV, "Use this Apple TV's location" takes a single, approximate reading.

You can search for a stop, or move the map and search that area, without sharing your location at all. You can change the permission at any time in Settings โ†’ Privacy & Security โ†’ Location Services โ†’ My Bus Stop.

What stays on your devices

Your saved stops and lines, your recent searches and your settings (colours, appearance, language, wall mode and its schedule) are stored on your device. Widgets and the Top Shelf keep a copy of the latest board so they can show it.

Your saved stops also sync through your own iCloud account, so they appear on your iPhone, iPad, Mac and Apple TV. That data belongs to your Apple Account and is handled by Apple under Apple's privacy policy; we can't read it. Your iPhone also sends your saved stops and the latest arrivals to your paired Apple Watch.

Maps, and the street address shown for a stop, come from Apple Maps. In New York City, stop searches also use Apple's map search.

Usage statistics and crash reports

The app uses Firebase from Google for usage statistics (Google Analytics for Firebase), crash reports (Crashlytics), remote settings (Remote Config) and to check that requests to our relay come from the real app (App Check).

Usage statistics include Firebase's standard events, such as the app being opened, and a few of our own: the welcome screens being shown and finished, the Apple Watch app being installed and synced, and a region's live data going down and coming back. Firebase also records the device model, OS version, app version, country and a random identifier for the app installation. None of our events contain your stops, lines, searches or location.

Crash reports include the state of the app when it crashed. When a transit service fails to answer properly, the app also sends an error report so we can fix it. That report can include the address the app requested and the first part of the service's reply, which can contain stop names, line numbers or the text of a search you made. Keys and coordinates are removed from these reports before they're sent.

This data isn't linked to your name, email or Apple Account. The app doesn't use the advertising identifier, doesn't ask for tracking permission, and doesn't share anything with advertisers or data brokers.

Feedback you send us

When you send feedback from the app, it becomes an entry in a private issue tracker on GitHub. It contains what you wrote, the email address if you chose to give one, any screenshots you attached, and your app version, device model and OS version. Location and camera details are removed from attached images before they're uploaded. Only send what you're happy for us to read.

My Bus Stop on the web

The web version at amirhayek.dev/MyBusStop/web asks most regions' transit services directly from your browser, and only offers regions whose services need no key. Israel is the exception: bus.gov.il doesn't let a browser read its answers, so in Israel the web version's requests go through a second, keyless relay we run on Google Cloud (Cloud Functions for Firebase, in Tel Aviv). It forwards only the stop, line or search you asked about, and keeps bus.gov.il's reply in memory for between 10 seconds and an hour. In Philadelphia, SEPTA's timetable doesn't let a browser read it either, so the next departures at your stop come through the same relay, which is sent only the stop and the line and keeps the reply for a minute; bus positions come from SEPTA directly, and stops from a file on this site. In Taipei, Taipei City's bus files can't be read by a browser either, so they come through the same relay, which works as it does for the app: it is sent only the stop or line you asked about, and stops nearby are found in your browser. Its own logs don't record stops or searches; Google Cloud's standard request logs may record the address that was requested and your IP address. Outside the listed regions, arrival times come from Transitous, a community-run service built on transit agencies' open data, which receives the stops, lines and searches you ask about.

Your location is used only when you tap Find stops near me, after your browser asks for permission. It's sent to your region's transit service to find stops around you (in Israel, to Transitous; it never goes through our relay), and isn't stored. Your saved stops, line colours and theme are kept in your browser's own storage on that device, along with copies of stop lists so the next visit is faster. Clearing the site's data in your browser removes them all.

Board links and Home Assistant. Copy link to this board puts the stop and lines you chose into the link itself, after the #, so the link carries them to whoever you send it to without them ever reaching our server or analytics. The My Bus Stop card for Home Assistant keeps the same board in your dashboard's own settings, on your Home Assistant, and shows it from this site; a board shown in a card keeps nothing in the browser's storage. The card's editor uses this site's stop picker, whose saved stops stay in that browser as above.

Like every page on amirhayek.dev, the web version counts page views with Google Analytics. It sends no stops, lines, searches or location to it. Fonts load from Google Fonts.

Who else is involved

ServiceWhat it's forWhat it receives
Your region's transit data serviceStops and arrival timesThe stops, lines and searches you ask about, and your coordinates when you look for stops nearby
Google Cloud (our relay)New York City, Seattle & Puget Sound, Tampa, Luxembourg, Berlin & Brandenburg and Taipei in the app, and bus positions in Ljubljana and Stockholm; Israel, Taipei, and Philadelphia's timetable, in the web versionThe same requests, forwarded to the agency; your IP address in standard request logs
Apple (iCloud, Maps, App Store)Syncing saved stops, maps and addresses, distributionYour saved stops in your own iCloud; stop locations for addresses; New York stop searches
Google FirebaseUsage statistics, crash reports, remote settings, App CheckUsage events, device information, crash logs and failed-request reports
GitHubFeedback inboxOnly what you send from the feedback form
TransitousThe web version: outside its listed regions, and finding stops near you in IsraelThe stops, lines and searches you ask about, and your coordinates when you look for stops nearby
Google Analytics and Google FontsThe web version's page views and fontsStandard page-view data and your IP address; no stops, lines, searches or location

How long things are kept

Your choices

Children

The app isn't directed at children under 13, and we don't knowingly collect personal information from them.

Changes to this policy

If the app's data handling changes, this page changes with it and the date at the top moves.

Contact

Amir Hayek, hayek_dev@icloud.com.