Privacy

Train lookups

Railwatch provides public train information without an account. A lookup sends the information needed to answer it, such as train number, station, route, and date. You do not need to send a name, ticket, payment details, precise personal location, or email and calendar content.

When an assistant calls Railwatch, Railwatch receives the tool request rather than needing access to your whole conversation. Your assistant provider controls what it sends and handles its own conversation history under its policies.

Website storage

The website saves up to six recent train searches in your browser’s local storage. Clear the site’s browser data to remove them. This feature does not create a Railwatch account.

Service diagnostics

Hosting services process technical request information needed to serve and protect the website, including network information, requested URLs, and errors. Railwatch uses request limits and may record service errors and performance information.

When Sentry monitoring is enabled, diagnostics are sent to Sentry. The website is configured to sample session replays and capture replays when errors occur. Text and inputs are masked and media is blocked in replay configuration. Error reports and performance information may still contain page URLs, browser details, and request context. The assistant API does not run browser session replay.

Data providers and other services

Train schedules and tracking come from external rail data sources. Following a link to Amtrak or an assistant provider takes you to a service with its own privacy practices. Railwatch’s lookup tools do not request permission to read private assistant accounts.

Questions and requests

Use Railwatch support for privacy questions or requests about information you believe Railwatch holds. Avoid sending sensitive travel or payment details with an initial request.