Your privacy

Privacy Policy

How RailJournal collects, uses, and protects information when you browse railjournal.in.

00

Your privacy matters.

At RailJournal, accessible from railjournal.in, one of our main priorities is the privacy of our visitors. This Privacy Policy document contains the types of information that is collected and recorded by RailJournal and how we use it.

01

Log Files

RailJournal follows a standard procedure of using log files. These files log visitors when they visit websites. All hosting companies do this as a part of hosting services' analytics. The information collected by log files include internet protocol (IP) addresses, browser type, Internet Service Provider (ISP), date and time stamp, referring/exit pages, and possibly the number of clicks.

02

Cookies and Web Beacons

Like any other website, RailJournal uses "cookies". These cookies are used to store information including visitors' preferences, and the pages on the website that the visitor accessed or visited. The information is used to optimize the users' experience by customizing our web page content based on visitors' browser type and/or other information.

03

Google DoubleClick DART Cookie

Google is one of the third-party vendors on our site. It also uses cookies, known as DART cookies, to serve ads to our site visitors based upon their visit to railjournal.in and other sites on the internet. However, visitors may choose to decline the use of DART cookies by visiting the Google ad and content network Privacy Policy at the following URL – policies.google.com/technologies/ads

04

Consent

By using our website, you hereby consent to our Privacy Policy and agree to its Terms and Conditions.

05

Product Analytics

RailJournal measures page views, button clicks, and form submissions to improve navigation and content. These events use a random first-party session identifier that is hashed before storage. We do not store form text, button text, usernames, destination URLs, or search queries in this behavioral dataset. Detailed event records are deleted after 90 days; aggregated reporting may be retained longer.

06

Anonymous Train Ratings

You can rate a train without signing in. To prevent repeated anonymous ratings for the same train, we store a first-party browser token as a one-way hash alongside that rating. The token does not contain your name, email address, or review text. Signing in lets you submit an account-based review separately.