Cookie Policy, Legal & Usage

Rail Record Uses Cookies

There are several types of cookies which are used on this website. Cookies are small files stored on your device, to store various pieces of information, such as site preferences (eg logins, security tokens to confirm you’re not a robot).

There are two third-party cookies that it is our legal requirement to declare to you. These are:

  • Google Adsense Cookies – We run Google Adsense ads on some of the live train times pages to help pay for the website. We do not make any profit from this and this only covers a small amount of our expenses. Cookies are stored on your device to match you up to relevant ads, with information collected from other websites. Google may track your visit to the website, as well as third party Adsense partners, in order to show you ads that are personalised to you.
  • Google Analytics Cookies – These store information about your visit on your device. Google will be able to view your visits to the Rail Record website, to identify whether you are a new or returning user. Some of your data will be shared, such as IP address location, demographics and where you came from to arrive on the Rail Record website.

These are the two main types of cookies we use. Whilst the website does use other cookies, none of these store personal information, and are not shared with anyone. You can simply remove these by going to your browser settings and clearing cookies.

You will have the option to accept or deny these cookies either through a cookie bar or a Google Consent popup. 

Some of the generic cookies we use to improve your experience, but do not share or collect personal data, include:

  • Wordfence Cookie – A record of whether you are a human or robot is stored, so you’re not shown a bot-challenge page or blocked out for security reasons.
  • Login – When you use the member area at, upon successful login, you’ll be stored a login cookie for 30 days so you do not need to login each visit.
  • Session Cookies – Some PHP session cookies are used on the live train times, namely once you’re logged in to the member area. This ensures your login is carried over around the site so you can set alerts, allocations etc.