Pigeon NYC Subway

/ Privacy & Support Updated 1 Oct 2026

Privacy Policy

Pigeon NYC Subway is a subway map and arrivals app for iPhone. This policy describes exactly what the app does with information, written against what the code actually does.

The short version

  • The app works without an account. Usage and ad counts are sent automatically; Delay Alerts registration is optional.
  • Your location is used on your phone and is never transmitted anywhere.
  • One optional feature — Delay Alerts — sends a small amount of data to a server, because sending you a push notification is impossible without it.
  • The app shows a small number of ads and station events, chosen and published by us. No ad network is involved, nothing about you is used to decide what you see, and no ad measures or reports back on you.
  • There is no analytics product and no third-party analytics SDK, no tracking of you as a person, and nothing is ever sold or shared for marketing. The app counts how its own screens are used, grouped by app session and never by person — section 6a says exactly what that means.

01 What is collected

Almost nothing, and nothing that describes you. Browsing the map, searching stations, checking arrivals, saving favorites, and planning trips all happen on your phone. The data that leaves it is described below: Delay Alerts registration and settings updates, ad counts (section 6), and usage counts with a session ID (section 6a).

If you enable Delay Alerts, the app sends the following settings to its server. Later changes, including switching alerts off, are also sent:

Delay Alerts registration and settings updates
FieldWhat it isWhy it is needed
installationIDA random identifier created by the app for this install. Not your Apple ID, not your device's serial, not linked to your name.Keeps one set of settings per install so a refreshed push token updates the existing record instead of creating duplicates.
deviceTokenThe push token Apple issues to this app on this device.Apple requires it to deliver a notification. Without it there is nowhere to send the alert.
lineIDsWhich subway lines you chose to be alerted about.So you are only notified about your lines.
windowStart / windowEndThe start and end of the daily window you picked.So you are not woken up outside the hours you chose.
daysWhich days of the week you chose, as numbers.So a weekday commute alert does not arrive on a Sunday.
timeZoneYour device's time zone name, e.g. America/New_York.So your chosen window means the right hours.
enabledWhether alerts are on.To know whether to send anything.
reconcileOnly (migration only)A flag sent when an older app stored OFF without recording whether alerts were ever registered. It is not stored on the server.Stops an existing registration without creating a new one for someone who never enabled alerts.
revisionA settings change number, stored as settingsRevision on the server.Prevents an older request from undoing a newer setting, including turning alerts off.

The server also keeps an expiry time and alert-delivery state (previously reported severity, daily send count and the time of the last alert) to expire inactive records and avoid repeat notifications. No email address, name, account or password is requested — the app has no sign-in of any kind.

02 What stays on your device

Favorites, recent searches, onboarding state and local diagnostics stay on your iPhone. Alert settings and pending settings changes are also kept locally until they can be sent as described in section 1. Deleting the app removes this local data.

  • Favorite stations and favorite events
  • Recent station searches
  • Whether you have seen the intro screens
  • Your Delay Alerts choices (also sent to the server, per section 1)
  • Crash and hang diagnostics, recorded through Apple's MetricKit and written only to the device's own log. If you have opted in to sharing analytics with developers in iOS Settings, Apple may pass Apple's own crash reports along — that is Apple's system-wide setting, not something this app collects separately.

03 Location

The app asks for location access only while you are using it, to center the map on where you are and show nearby stations.

Your coordinates never leave your phone. They are not sent to the app's server, not attached to Delay Alerts, not logged, and not shared with anyone. The app works if you decline; location-based centering and the Current Location trip endpoint are unavailable.

04 Delay Alerts

When Delay Alerts is on, a scheduled job regularly checks the MTA's public service-alert feed. It sends a notification when a watched line becomes classified as having a serious delay or service disruption, during your selected days and hours. An ongoing issue is not repeatedly sent unless it eases or recovers and then becomes serious again. The number of notifications per day is limited, and minor changes do not trigger a notification.

The data in section 1 is stored using Google Firebase (Cloud Firestore and Cloud Functions) on servers in the United States. Push delivery goes through Apple's Push Notification service, as it must for any iPhone notification.

How to stop alerts. Turning Delay Alerts off sends a stop request to the server. The app shows whether the settings were saved. If the request fails, it is kept on your phone and retried when you reopen the app or tap Retry while connected. Alerts may still arrive until the server saves the change. You can switch notifications off for Pigeon in iOS Settings at any time. To delete the stored record as well, use the contact in section 11 — see section 8.

05 Third parties your phone talks to

Using the app makes ordinary web requests to a few places. Each of them sees what any website sees — your IP address and the request itself — Your coordinates are not included. Firebase receives the registration, settings and counts described below, and Apple receives the push token needed for delivery.

  • The MTA — for live arrival times and service alerts.
  • Google Firebase — the list of currently published ads and station events is fetched, and their images are loaded from the same place. The request carries no identifier and is the same for everyone.
  • Google Firebase — for Delay Alerts registration and later settings updates, including OFF (section 1), and for ad and usage counts (sections 6 and 6a).
  • Apple — to deliver push notifications.

Server logs. Google Cloud request logs record technical request metadata, including IP address, user agent and request time. Rate-limit warnings can also include an IP address, and Delay Alerts processing logs can include the installation ID when a registration is removed, disabled or fails to process. These logs support security and operation of the service and are retained for 30 days. Separate administrative and system audit logs are retained for 400 days.

Ad and event images are stored and served by us on Firebase Storage, so loading one does not introduce another company. If an ad ever links out to a website, opening that link is an ordinary visit to that site and their policy applies from that point — the app does not tell them anything about you, and nothing is passed along in the link.

06 Ads and station events

Some stations show a card for an event or a local business. These are the app's way of paying for itself, and they work differently from advertising in most apps — the difference matters, so it is worth being specific.

  • Every ad is chosen and published by us by hand. There is no ad network, no exchange, and no third-party advertising code anywhere in the app.
  • Which ad you see does not depend on you. It depends only on which station you are looking at. Two people opening the same station see the same card.
  • The ad-count payload contains no personal or device identifier. The app does count how many times each ad was shown and tapped, but the count is a total across everyone: the request carries no installation id, no device token and no timestamp, and the stored record is an ad, a date, and three counts: impressions, card taps and external-link taps. The ad statistics database does not store a per-device viewing history. Separate server request logs are described in section 5.
  • An advertiser learns nothing about you: not your location, not your device, not whether you in particular looked at their card.
  • The app requests the list of what is currently published. Ads that have finished, ads scheduled for later, and the notes behind them are never sent to the app and cannot be read from it.
  • Tapping a card opens a page inside the app. If that page links to a website, following it is an ordinary visit to that site.

An earlier version of this page promised to say so before any counting began. The counting described above started on 7 September 2026, and this is that notice. It stayed within what was promised — totals across everyone, never a record of what any one person saw — and if that ever needs to change, this section will say so before it does.

Counting how the app itself is used

The app is also built to count which of its own screens are opened and how long they stay open — whether people use Directions more than Line Status, and where the time goes. This began on 19 September 2026. Notice of it was published here in advance of that date, which is what section 10 promises; this sentence now records when it actually started.

The counts are grouped by app session, not by account. A random session ID is created when the app process starts and stays the same until that process ends; backgrounding the app or crossing midnight does not replace it. Pending batches, including this ID, are saved on the phone for later delivery. Counts from the same session can be grouped together, but they do not record the order of individual actions. These batches contain no installation ID, push token, advertising identifier or IP address.

These counts are used to understand feature usage. They are not joined to notification registrations or used to build a cross-session device profile.

Nothing about where you are, which stations you look at, or what you type into search is included. The batches contain event counts, screen names and seconds, the session ID, and the app version and build number. The server adds a receipt date, timestamp and expiry time.

The counts are deliberately approximate. Up to ten pending batches are saved on the phone and sent on a later flush; older batches are dropped if the queue exceeds ten.

07 What never happens

  • No advertising SDK, ad network, or third-party advertising code is included in the app, and no ad is targeted at you.
  • No analytics product, no third-party analytics SDK, and no tracking of you as a person. The app counts which of its own screens get opened and for how long, described in section 6a; those counts are not attached to you, your device, or a persistent installation identifier. Pending batches can survive an app restart, as described in section 6a.
  • Nothing records what you search for, which stations you look at, or where you travel.
  • No cross-app or cross-site tracking, and no advertising identifier (IDFA) is requested or used.
  • Nothing is ever sold, rented, or shared for marketing purposes.
  • No profile about you is built, and nothing is used to make automated decisions about you.

08 How long it is kept, and deleting it

If you never turn on Delay Alerts, no notification registration is created. Ad and usage counts are still collected as described in sections 6 and 6a.

If you enabled alerts, the server keeps the registration described in section 1. Turning alerts off disables delivery but does not immediately delete the registration. If an OFF request arrives before registration completes, a minimal record of the installation ID, OFF state, revision and expiry is kept to prevent a delayed ON request from re-enabling alerts. Records are scheduled to expire 180 days after their last settings update or alert attempt; expiry deletion is asynchronous. A record is also removed when a send attempt receives Apple's Unregistered response. Deleting the app does not immediately notify our server; you can request deletion using the contact below.

Daily totals contain no session or installation identifier. The ad counts in section 6 are an ad, a date and three counts. The daily usage totals in section 6a are event counts, screen names, seconds, a session count and a day. Neither carries anything that points back to a phone or a person, so there is nothing in them to find and nothing to delete on request — and they are kept as ordinary business records rather than on a clock. The raw batches behind section 6a's totals also contain the session ID, app version, build and receipt timestamp. They are assigned an expiry 400 days after receipt; an active server TTL policy removes expired records asynchronously. A daily count of how many notification registrations went away is kept the same way — a date and a number, nothing else.

To request deletion directly, email pigeon.subway.nyc@gmail.com and ask. It helps to include your installation ID, which you can find on the notification settings screen in the app. Requests are handled within 30 days. You do not need to give a reason, and nothing is asked in return.

09 Children

The app is a general-audience transit tool and is not directed at children. It does not knowingly collect information from anyone under 13. If you believe a child's information was submitted, email the address above and it will be deleted.

10 Changes to this policy

If this policy changes, the date at the top of the page changes with it. Material changes — anything that widens what is collected or who receives it — will also be noted in the app's App Store release notes, so it is not a silent edit.

11 Contact

Pigeon NYC Subway is made by an independent developer. Questions about privacy, data deletion, or anything else in this document:

pigeon.subway.nyc@gmail.com


Support

There is no ticket system and no phone tree. Email reaches the person who wrote the app.

→ Getting help

Email pigeon.subway.nyc@gmail.com. Most replies come within a few days.

Bug reports are much easier to act on with: your iPhone model, your iOS version, the app version from the App Store listing, and what you were doing when it went wrong. A screenshot usually settles it faster than a description.

→ Common questions

Arrival times look wrong or are missing

Arrivals come straight from the MTA's live feed and are shown as received, without adjustment. When the MTA's feed is delayed or a train is not reporting, the app has nothing better to show. If times are wrong across every station for a long stretch, that is worth an email — it usually means a feed format change.

Delay Alerts are not arriving

Check that notifications are allowed for Pigeon in iOS Settings, Delay Alerts is on, at least one line and day are selected, and the current time is in your chosen window. Check that your alert settings were saved; retry while online if they were not. Alerts are for newly serious delays or service disruptions, not every minor change, and the number per day is limited. An unchanged ongoing issue is not sent again.

I want to turn alerts off, or delete my data

Switch Delay Alerts off and check that the app confirms the settings were saved. If offline, reopen the app or tap Retry while online; alerts may continue until the server receives the change. You can also turn off notifications for Pigeon in iOS Settings. To delete the stored record as well, email the address above — see section 8 of the privacy policy.

The map will not center on me

Location permission is requested only while the app is open. If you declined it, enable it under iOS Settings → Privacy & Security → Location Services → Pigeon. Everything else in the app works without it.

A station is missing or in the wrong place

Station positions are matched by hand against the official diagram, so mistakes are possible. Email the station name and what looks wrong.

→ About the data and the map

Live arrival times and service alerts come from the MTA's public developer feeds. The app is an independent project and is not affiliated with, endorsed by, or operated by the Metropolitan Transportation Authority. Service information is provided as-is and should not be your only source when timing matters.