Journey searches
PNR and journey inputs are sent to the site’s server only to answer the request. They must not be placed in URLs, analytics events or application logs. Live providers may process the query under their own terms.
Reminder data
A PNR alert requires explicit consent and an email address. The PNR is encrypted with a server-only key; the database stores ciphertext, an IV and scheduling metadata. Reminder records should expire automatically after the journey or retention period.
Analytics
RailSahayak 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
Secrets belong only in protected hosting variables. Database row-level security, least-privilege keys, encrypted transport and scheduled deletion are required. No internet service can promise absolute security.
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.