Last updated: October 13, 2026
This policy explains what information Transitly collects when you use the app, how we use it, and the choices you have. Transitly does not require you to create an account, sign in with Apple, or provide your email address to use the app. There is no username or public handle.
Location data. While you are recording a trip, Transitly uses your device's location to follow your route and identify the line, station, and stops you traveled through. Transitly does not access your location when you are not actively recording a trip.
Motion data. During a recorded trip, Transitly may use on-device motion sensors to help distinguish activities like walking from riding a train. This data is used only to detect and record that trip.
Trip data you create. The trips you save, including route, line, origin and destination stations, and timing. You can also enter trips manually instead of relying on automatic detection, in which case location and motion data are not used for that trip.
Anonymous device token. On first use, the app registers with our servers and receives a random device token stored in the iOS Keychain. The app sends that token with API requests so we can authenticate calls, rate-limit, and protect the service. The token identifies the installation, not you as a person. It is not your name, email, Apple ID, or phone number, and obtaining a token does not prove the caller is you.
On-device iCloud identity. When iCloud and CloudKit are available, Transitly silently reads a stable CloudKit user record identifier and, when Apple provides it, your iCloud given name so the in-app Profile can show a display name. That CloudKit identifier and name stay on your device for the Profile experience today; they are not required to use trip recording, and they are not sent to Transitly's servers as an account. If CloudKit is unavailable (for example, no iCloud account or an unsigned development build), the app keeps a random local identifier on the device instead. There is no Sign in with Apple sheet and no create-account flow.
We use the information described above to detect and record your trips and show you your own history, stats, and insights inside the app; to improve our trip-detection algorithms, using patterns drawn from many riders' trips; and to operate, secure, and troubleshoot the service.
When trip data is used to train or improve our detection models, or shared outside Transitly in any form, it is stripped of your anonymous device token and combined with data from other riders first. The result reflects patterns, such as which stations riders commonly transfer at on a given line, rather than any individual person's movements. We do not share or sell raw, individually identifiable trip or location data.
Transitly may, in the future, share aggregated and anonymized ridership insights, such as ridership volumes or transfer patterns on a given line, with transit agencies, researchers, or planning partners to help improve the transit systems riders rely on. Any data shared this way is in aggregate form only. It does not include individual trips, location history, or any information that could identify a specific person or device, and it is not sold to advertisers or data brokers.
We use a small number of infrastructure providers to operate Transitly, including Amazon Web Services for hosting and data storage and Cloudflare for network security. These providers process data only on our behalf, under confidentiality obligations, and are not permitted to use it for their own purposes.
Transitly does not contain advertising SDKs or third-party tracking code. The app is built using only Apple's native frameworks. We do not show ads and do not build advertising profiles from your data.
You can change or revoke Transitly's location and motion permissions at any time in iOS Settings, though this will limit or disable automatic trip detection. You can turn off iCloud for the app in iOS Settings if you do not want CloudKit identity used for Profile; trip recording still works with the local on-device fallback. To request a copy of data we hold on our servers, or to ask us to delete it, email [email protected] from the address you want us to use for the request. In-app data management tools are planned for a future release.
We retain trip and related server-side records associated with your anonymous device token for as long as you use Transitly on that installation. If you ask us to delete your data by emailing [email protected], or you delete and reinstall the app (which discards the local token and on-device profile), we remove the associated server-side trip history we can link to that installation. On-device Profile and CloudKit data are managed by you and Apple on the device; contact us if you need help confirming what was deleted from our servers.
Data in transit between the app and our servers is encrypted using HTTPS. We limit internal access to location and trip data to what is needed to operate and improve the service.
If we make material changes to this policy, we will update the date above and, where appropriate, notify you through the app.
If you have questions about this policy or your data, email us at [email protected].