Journey searches
PNR and journey inputs are sent to the site’s server only to answer the request. PNRs are submitted in a POST body, not a page URL, and are excluded from analytics and application logs. Other searches can include station codes and train numbers in request URLs. Live providers may process the query under their own terms.
Reminder data
PNR email alerts are paused and new subscriptions are not accepted. Calendar files are generated on your device and must be imported into your calendar. Recent train searches and favourites store only train numbers and station codes in this browser until you remove them or clear site data. No PNR or journey date is saved with favourites.
Analytics
RailQ can record page views, tool names, broad outcomes and an anonymous session identifier. Full PNRs, passenger names, email addresses and form contents are excluded. IP handling depends on the configured analytics provider and should use available privacy controls.
Advertising and cookies
Advertising services may use cookies or similar identifiers after the consent setup required for the visitor’s region. Ads are labelled and kept separate from railway results. Do not enable personalised ads before the necessary consent and policy configuration is complete.
Security and retention
Technical monitoring stores hourly counts, response durations and error categories, without PNRs or passenger details. Problem reports contain a tool name and problem code. Monitoring records older than 30 days are cleaned during subsequent monitored requests. Contact messages contain the details you submit and remain until the operator deletes them; you can request deletion through Contact. Hosting and railway providers process requests under their own policies.
Your choices
Visitors can avoid reminders, reject optional cookies where offered and request deletion of contact or reminder data through the contact page. Identity verification may be required before fulfilling a request.