Your train, watched for you

Information We Collect

Raily ("the App") does not collect personally identifying information (such as your name or email) on our servers. However, to deliver background notifications (delay, platform-change and arrival alerts), the App sends the limited data below to the Raily backend. We also collect the product analytics described below to improve the app. This data is not linked to your identity for advertising and is never used for cross-app advertising tracking.

• Device identifier (APNs device token): sent and stored as the destination for push notifications.
• Tracked-train information (train ID, train number, route, boarding and alighting stations, the device’s display language, and the next train of the same journey): for trips you choose to track, sent and stored to monitor status and send you alerts, including the disruption “next move”.
• Journeys, travel history, reservation details, photos and notes: stored on your device in SwiftData. Booking references, coach and seat values you enter, photo contents, note text and recorded locations are not sent to our backend, analytics, notifications, iPhone widgets or Live Activities.
• Apple Watch companion: saved train segments, boarding and alighting stations, times, service status, connection information, coach and seat values sync to your paired Apple Watch through Watch Connectivity. Booking references, photos, notes and account information are excluded. The Watch stores the latest snapshot for offline reading and shares it locally with the app’s Watch widgets. Coach and seat values are not displayed by Watch widgets. Changes and deletions on iPhone reach the Watch on the next successful sync; the last saved snapshot remains while disconnected.
• Manual backups: you can export a JSON file containing journeys, saved trains, booking references, coach and seat values, photos, notes and recorded locations to a location you choose in Files. Account information, purchases and push tokens are excluded. This is not automatic sync. If you choose iCloud Drive or another provider, that service stores the file. You control deletion of exported files.
• Product analytics: a per-install identifier, event time, app version and interaction events such as search, save, journey start/completion, Moment creation, story viewing and purchase are sent to our backend. Journey start/completion, Moment creation and reliving events contain no journey IDs, station names, locations, photos or note text. Failed saves do not emit success events.
• Sign in with Apple: if you sign in, your name and email are stored only in the device UserDefaults; the Apple user ID is stored in Keychain. A derived account identifier is sent to RevenueCat to link purchases. Apple lets you hide your email via its private relay.
• Pro check (disruption “next move”): to decide whether to show a recommendation, the App sends our backend its RevenueCat customer identifier and the train IDs of the first journey watched for free. The backend asks RevenueCat for the purchase status with that identifier. The first journey is stored with the identifier and train IDs, together with a short, non-reversible hash of the connecting IP address and the date to prevent abuse (the IP address itself is not stored).
• App integrity check (App Attest): to confirm that requests to our backend come from the genuine Raily app and to prevent abuse of our API, the App uses Apple’s App Attest. iOS creates a key for this app in the device’s Secure Enclave, and Apple’s servers certify it. The private key never leaves the device and cannot be read by us. When the key is created, the App sends our backend the key identifier and the Apple-issued certificate (which contains the public key); after that, it attaches a signature made with this key, the key identifier and the device’s clock to some requests. The backend stores the key identifier, the public key, a signature count, how the App was installed (such as App Store or TestFlight) and its version when the device reports them, and when the key was registered and last used. This record is not stored together with your device token or account.
• Advertising tracking: this data is not used for advertising or tracking across other companies' apps and websites.

Train Data

To show schedules and live delays, the App sends search queries (e.g. train numbers) to the Raily backend or public rail-data providers. These requests contain no personally identifying information.

Data Deletion

Journeys, reservation details and Moments can be deleted in the App. Signing out alone does not delete journeys, reservation details, photos or notes. Deleting the App removes its local data, but does not delete exported backups. Pending notification data expires after at most 15 minutes and is removed by the monitor. Server-side automatic retention for analytics events is not configured in the current implementation. App Attest keys stop working after the App is reinstalled, the device is migrated, or it is restored from a backup. Server-side automatic retention for App Attest key records is not configured in the current implementation either.

Children's Privacy

The App does not knowingly collect personal information from children under 13.

Contact

Questions? Reach us through the contact form above.