Headway

Privacy Policy

Last updated: November 18, 2026

This policy explains what data Headway collects when you use the app, website, or chat connector.

Headway chat connector

Nick Faughey, operating Headway under the Axis Maps name, provides the connector for public rail lookups without a Headway account.

What we receive and how we use it

Your chat service sends Headway the structured inputs for each lookup, such as a station name, train number, operator, service date, or a reference from an earlier lookup. Headway uses those inputs to find public rail information and returns the result to the chat service. The connector does not need your full conversation. We do not save a history of connector lookups or results.

We process request metadata, such as the connecting IP address, request path, time, and response status, to run the connector, limit abuse, and troubleshoot errors. The connecting address may belong to your chat service or another intermediary. Temporary traffic records expire within 10 minutes of the last activity. Operational metrics, including request counts, timings, and error categories, are retained for up to seven days. We retain anonymous aggregate statistics about connector usage, app arrivals, and subsequent app activity for up to 24 months. Our API does not keep individual connector request logs.

Google Cloud hosts the connector. Cloudflare routes and protects traffic and may collect sampled connection metadata, such as the connecting IP address and request path. See Cloudflare's privacy policy. Axis Maps does not sell connector data or use it for advertising or model training.

Your chat service and your choices

Your chat service handles your conversation and any results it receives under its own privacy policy. Disconnect Headway in that service to stop future requests. Use the service's controls to manage or delete your conversations.

For privacy questions or requests, email [email protected]. Without a Headway account on the connector, we may be unable to link a request to you. See the Headway connector terms.

What the app and website collect

Location data (optional)

If you tap the locate-me button on the map, iOS asks you to grant Headway permission to use your location while the app is in use. With permission granted, Headway shows your position as a blue dot on the map so you can see where you are relative to nearby trains.

Your location stays on your device. It is never transmitted to Headway's servers, never logged, never used to identify you. You can revoke permission at any time in iOS Settings → Privacy & Security → Location Services → Headway.

Your Headway account (optional)

Headway works fully without an account. If you choose to sign in — to sync across devices or to purchase Headway Pro — you can use Sign in with Apple, Google, or an email and password. We use Auth0 to handle the sign-in securely; Headway never sees your password.

When you sign in we store, on our servers, your email address and a stable account identifier. We use them only to keep your account, sync your saved trains, stations, services and boards, remember whether you have Headway Pro, send the alerts you ask for, and understand how Headway Pro is used (see "How you use the app" below). This data is never sold, never used for advertising, and never used to track you across other apps or websites. If you use Sign in with Apple, you can hide your email with Apple's private relay and we'll only ever see the relay address. You can sign out at any time in Settings, and you can delete your account yourself — see "Deleting your account" below.

After a successful sign-in, newer versions also report the app, platform and app version to our servers. We record the time we receive that report and associate it with your account to understand account usage and troubleshoot sign-in issues. The record also includes the keyed hash of the app's installation identifier (described below). We do not store a password, access token, location or IP address with these records. Restoring an existing session does not create a new sign-in report. Sign-in records are deleted when your account is deleted.

Saved trains, stations, services and boards

When you bookmark a train, the train number and route name are stored in your iPhone's local app data (UserDefaults). When you bookmark a station, its identifier, name, and the agencies that serve it are stored the same way. When you save a service — a station, a line and the direction you travel — we store those identifiers plus their names, the line's colour, and the times you saved and removed it, again in local app data. Departure boards you arrange are stored the same way. If you are signed in, all of these are also synced to our servers so they appear on your other devices — tied to your account and nothing else. Signed out, they never leave your device.

Search keeps a list of the last 20 trains, stations and lines you opened, so it can offer them again. That list lives only in your iPhone's local app data; it is never synced or sent to us.

Saving a service does not turn on notifications and does not share your location. If you have already allowed Headway to use your location, your saved services are sorted with the nearest station first; that sorting happens on your device and your location is never sent to us. Removing a saved service keeps a record that you removed it, so the removal is not undone by another device that still has it.

Diagnostics and crash reports

If Headway crashes or hangs, iOS collects a diagnostic report via Apple's MetricKit framework. Headway uploads these reports to our servers so we can find and fix bugs. Reports contain technical data only — stack traces, device model, OS version, app version — and no personal information: no identifiers, no location, no usage history. Apple aggregates and anonymises these reports on your device before Headway ever sees them.

How you use the app (product analytics)

Headway records a small set of events about how the app is used — foreground use, screens and feature categories, search result counts and selections, saved-item changes, filters, permission prompts, tracking starts and stops, and whether an in-app announcement was shown, opened or closed. We also record whether the Pro upgrade screen was shown or closed, product loading, plan selection, sign-in outcomes, and purchase or restore outcomes. We do not collect search terms or the train or station selected. Each event carries the app version and build, platform and distribution channel, configuration version, access tier, random session and flow identifiers, event order, and a random identifier created when you install the app. We store that installation identifier only as a keyed hash; reinstalling the app creates a new one. Events contain no location, no train or station you looked at, and no free text.

On the web, Headway also records which search engine or AI assistant sent a visit, as a category from a fixed list, along with the kind of page the visit landed on, such as a line or station page. We never record the address, path or search words of the page that referred the visit, or which line or station it was.

These events go only to our own servers. Activity is recorded against your server-verified account when you are signed in, and because a sign-in is recorded with the same installation identifier, events from a device you have signed in on can be connected to your account. Sign-out and account changes start a new anonymous identity segment; we do not assign earlier anonymous activity to the next person who signs in. We use these events to understand how often Headway is used, which features are useful, and how people move through the Pro purchase flow. We delete each event 90 days after we receive it.

Website traffic (Google Analytics, web only)

Headway on the web (headwaytransit.com) and the Axis website also use Google Analytics to count visits: the pages you view, the site or campaign link that sent you, and your browser, device type and approximate location. Google Analytics sets its own cookies on our sites to tell one visit from the next, and Google processes this data under its own privacy policy. We use it only to understand how many people visit and where they come from; we do not use it for advertising. The iOS app does not include Google Analytics.

Purchases (tips and Headway Pro)

Headway offers optional tips and a paid Headway Pro subscription (with a one-time lifetime option) as in-app purchases. Payment is processed entirely by Apple — we never receive or store your name, payment details, or billing information.

For Headway Pro, so that your purchase works across your devices, we store a record on our servers of which Pro product you own and whether it's active, tied to your account. Apple sends us a signed confirmation of each purchase and renewal (never your card or billing info) so we can unlock Pro for your account. We keep the details Apple signs — the product, Apple's transaction identifiers, the price and currency, and the App Store country — as our record of the purchase.

For tips, if you are signed in and do not have Headway Pro, the app also sends Apple's signed record of your past tips to our servers, so that past supporters can be recognised. If a tip is recognised in this way, we keep the same purchase details for it, tied to your account.

Live Trip Tracking

When you start tracking a trip as a Live Activity, Headway sends your device's Apple push token and the trip you selected (train, boarding and destination stops) to our servers so we can deliver lock-screen updates for that trip. If you are signed in, the registration is also linked to your account. It is used only to send updates while the tracking is active, and is deleted when the trip ends, when you stop tracking, or automatically within 12 hours.

Journey alerts (Headway Pro)

If you turn on alerts for a journey, Headway sends our servers your device's Apple push token, whether you allowed notifications, and the journey — the train, its date, and your boarding and destination stops — tied to your account, so we can notify you about that journey. When you sign out, the device stops receiving alerts. We keep a record of the alerts we sent.

Deleting your account

You can delete your Headway account from inside the app: Settings → Account → Delete Account on iPhone, or the account panel on the Headway website. Before you confirm, we show you what deleting will do. You can also email [email protected] if you cannot sign in.

Deleting removes your account and every sign-in linked to it — Apple, Google and email — in one step, together with the saved trains, stations, services and boards synced to it, your sign-in records, your journey alerts and the push registrations and device tokens behind them, your live-tracking registrations, and the record of which Headway Pro product you own. Headway Pro access that came from a gift or an early-supporter grant is lost with the account and cannot be restored. Your sign-in at our sign-in provider is deleted too. The deletion cannot be undone, and signing in again creates a new, empty account: nothing from the old one carries over.

What stays. Saves held only on your device stay on your device — deleting the account does not reach into your phone. We also keep the records of payments we actually took, because we have to, and the product-analytics events described above until they age out; both are detached from your account when it is deleted, so they no longer identify you.

Subscriptions are separate. Deleting your account does not cancel a Headway Pro subscription bought through Apple — Apple keeps billing until you cancel it in your Apple subscription settings. If you bought Headway Pro on the web and it is still set to renew, cancel it first: we will not delete the account while a web subscription would keep billing, and the app will tell you so.

What Headway does NOT collect

Network requests

To show live train positions, Headway fetches data from our API at api.axismaps.ai. The API aggregates live transit data for Amtrak, WMATA Metrorail, MARC, SEPTA Regional Rail, VRE (Virginia Railway Express), MBTA Commuter Rail, Tri-Rail, RTD Denver commuter rail (A/B/G/N Lines), LIRR, and Metro-North; the app talks only to our API, never to those agencies' upstream feeds directly. These requests carry standard HTTP headers (iOS User-Agent, app version), and some of them — opening the app, a sign-in report and the product analytics above — also carry the random installation identifier.

When the app starts, we record that it started: the app, platform and version, the installation identifier's keyed hash, and a hash derived from your IP address and User-Agent. We do not store the IP address itself with these records.

If you sign in, the sign-in itself happens through our identity provider at auth.axismaps.ai (powered by Auth0), and requests you make while signed in carry a token that identifies your account to our API so it can return your synced bookmarks and Pro status.

Apple maps tiles are served by Apple under their own privacy policy. See apple.com/legal/privacy.

Children

Headway is rated 4+ on the App Store. We do not knowingly collect any data from anyone, of any age, beyond what is described above.

Changes to this policy

If we change what data Headway collects, we'll update this page and bump the "Last updated" date at the top. We announce material changes to the iOS app in the App Store release notes.

Contact

Questions about this policy or about Headway? Email [email protected].