Privacy Policy
We believe in transparency and protecting your privacy. Here's how we handle data on trains.fyi.
Data Collection
trains.fyi is designed with privacy in mind. We collect minimal data necessary to provide our service:
- Usage analytics to understand traffic patterns and improve our service
- Basic device information for app functionality and debugging
- Location information you enable for nearby-train features, and location information included in content you choose to submit
We do not:
- Sell personal information
- Use your assistant connection to read your conversations
- Give connected assistants your password, email address, or payment details through our account-status tools
Cookies, analytics, and advertising
The website uses browser storage for sign-in and preferences, Google Analytics for usage measurement, and advertising integrations on eligible pages. These providers may process device, network, and usage information and use cookies or similar technologies. Browser and device settings can limit storage and location access.
Safety notices and consent
Agreeing to the Terms or acknowledging a safety notice does not grant permission for optional location collection or marketing. Those choices are separate.
Accounts and subscriptions
When you create an account, Firebase Authentication stores your account identifier, email address, and sign-in information. Account features store the preferences and activity you choose to save. We use RevenueCat and the relevant billing provider to manage subscriptions and check Pro access. Newsletter signup is optional and is handled separately from account creation and assistant authorization.
Connected assistants
Basic public train lookups can be used without a TrainsFYI account. If you connect an assistant such as ChatGPT or Claude, you explicitly authorize it to check whether your account is connected and currently has TrainsFYI Pro access. The current account-status tools return those status values, not your email, payment details, saved activity, or conversations.
We store the account identifier, requesting client, granted permissions, connection dates, and hashed authorization credentials needed to operate and revoke the connection. A short-lived, secure browser cookie binds the authorization request to your browser. Sign-in and assistant connection pages do not load our website advertising or analytics integrations.
Access tokens expire after 15 minutes. Connections expire after 30 days unless you reconnect. Expired authorization records are cleaned up daily in bounded batches; client registrations are retained so clients can reconnect. Disconnecting immediately invalidates the connection, but expired records can remain until cleanup. Account deletion removes account-linked authorization codes and grants.
You can revoke access from Connected assistants or delete your account from the account settings. Disconnecting an assistant does not cancel a subscription or remove data already received by that assistant. Its provider’s own privacy policy applies to its handling of tool results.
Service providers
We use hosting, authentication, billing, email, analytics, and advertising providers to operate the service. Data needed for these functions is processed by those providers; it is not sold by TrainsFYI. Public OAuth endpoints also use short-lived request counters for abuse protection. Do not put passwords or other private information into train-search questions.
Your choices
You can manage account settings, remove saved content, revoke assistant connections, and request access, correction, or deletion by contacting us. Public contributions may be visible to other users. Applicable privacy rights depend on your location.
See the Terms of Service and Rail Safety Notice.
Contact
If you have any questions about our privacy policy or data practices, please contact us at info@trains.fyi
Document version: 2026-10-02 · Updated: October 2, 2026