Privacy
This privacy page explains what trainchartvacancy.com collects, which is very little. There are no accounts and no analytics. This site shows ads served by Google AdSense, and Google sets cookies to do that; the Advertising section below says what that means. We never ask for, accept or store a PNR number or a passenger name. The records we keep are server logs, anonymous page-speed lines, a 48-hour cache of availability answers, and any email you send us.
Last verified .
What we hold, and for how long
The short version of this page is the table. Everything after it is detail.
| Data | Do we hold it | Kept for |
|---|---|---|
| Your name, email address or phone number | Only what you put in an email to us. The site itself has nowhere to enter them | As long as that email is kept in our mailbox |
| A PNR number, or any passenger name | No. We never ask for, accept or store either | — |
| An account, profile or password | No. The site has none | — |
| Cookies set by us | No. We set none of our own | — |
| Cookies set by Google for advertising | Yes, by Google AdSense, which serves the ads on this site | Set and governed by Google; see Advertising below |
| Your IP address and browser string | Yes, in standard web server access logs | Server default; not yet shortened |
| The page you asked for, and the referring page | Yes, in the same logs | Server default; not yet shortened |
| The train, stations and date you type into the checker | Sent to our data provider; the answer is cached with no record of who asked | Cache swept within 48 hours |
| Analytics | No. We run no analytics service | — |
| How fast the page loaded on your device | Yes, as four anonymous numbers. See "How we measure page speed" below | Kept as a line in a log file with no identifier in it |
We do not have accounts
There is no sign-up, no login, no profile, no newsletter and no password. We do not ask for your name, email address, phone number or date of birth, and there is nowhere on the site to give them to us.
We do not store PNR numbers or passenger names
The site has no PNR lookup. We do not ask for a PNR. We do not accept one. We write no PNR number and no passenger name to any database, cache, log file or URL. If you want PNR status, use the official channels: the RailOne app, the enquiry number 139, or a station enquiry counter.
Server logs
Our web server keeps standard access logs, as almost every web server does. A log line records your IP address, the time, the page requested, the referring page if your browser sends one, and your browser's user-agent string. We use these to keep the site running, to find errors, and to spot abuse such as scraping. We do not build a profile of you with them, and we do not sell or share them.
We have not yet set a shorter retention period than our server's default. When we do, this page will state the exact number of days.
When you use the seat availability checker
The checker asks an outside data company what seats are free. When you run a check we send that company the train number, the two station codes, the journey date, and the class and quota you chose. We do not send your IP address, any identifier, or anything about you. From that company's point of view the request comes from our server, not from you.
We keep the answer on our own server for a short time. The next person asking the same thing then costs no new call. That store holds train and seat data, and every row is swept within 48 hours. It holds nothing about who asked. How this site works sets out the cache periods in full.
Cookies, analytics and third-party scripts
We set no cookies of our own, and we do not run Google Analytics or any other analytics service.
One script on every page comes from someone else's servers: the Google AdSense script, loaded from `pagead2.googlesyndication.com`, which chooses and shows the ads. Google and its partners set and read cookies through it. Everything else on each page comes from this domain.
How we measure page speed
One small script of our own, served from this site and named `rum.js`, measures how quickly the page you are reading actually loaded and responded. Without it we would only know how fast the site is on our own server, on a wired connection, which tells us nothing about a phone on a slow network. It runs only after the page has finished loading, and it sends one message when you leave the page.
That message goes to our own server and nowhere else. It contains exactly seven things:
| Sent | What it is |
|---|---|
| The page path | For example `/train/12002/`. Without the part after the `?`, so a checker query — your train, your stations, your travel date — is removed in your browser and never reaches us |
| Time to first byte | How long our server took to start answering, in milliseconds |
| Largest paint | How long the biggest thing on the page took to appear, and a short description of which element it was, such as `h1` |
| Layout shift | How much the page moved about while loading, and which element moved |
| Interaction delay | The slowest response to a tap or key press, split into three parts, and which control it was |
| Navigation type | Whether you arrived, reloaded, or came back |
| Screen width | Rounded to the nearest ten pixels |
It sends no identifier of any kind, so two visits cannot be joined together. It sets and reads no cookie and writes nothing to your browser's storage. It sends no text from the page, nothing you typed, and no referrer. Our server records the line without your IP address and without your browser string, and stamps it with the minute, not the second.
This is not an analytics service and it is not a third party: the file is served from this domain, the collector is a script on this domain, and nobody else receives any part of it.
Advertising
This site shows ads served by Google AdSense. The ads are how the site pays for itself and for the live availability data.
- Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites.
- Google's use of advertising cookies enables it and its partners to serve ads to users based on their visit to this site and/or other sites on the Internet.
- Users may opt out of personalised advertising by visiting Google's Ads Settings.
- Users who prefer not to use Google's Ads Settings may opt out of a third-party vendor's use of cookies for personalised advertising by visiting www.aboutads.info/choices or the Network Advertising Initiative opt-out page.
How Google uses the information it collects from sites that show its ads is set out in Google's own terms: How Google uses information from sites or apps that use our services and Advertising.
We receive no personal information from Google about who saw or clicked an ad. Ads never change the train data, the chart times or the availability figures on a page, and no advertiser can pay to change them.
Children
This site is general travel information. It is not aimed at children. We do not knowingly collect anything from children.
Your rights
We hold no account data, and nothing that names you beyond server logs and any email you send us. So there is usually nothing for us to look up, correct or delete.
For any question about your data on this site, write to contact@trainchartvacancy.com. The site is run by Vijesh Rathore, as the about page sets out.
Changes
We will update this page whenever the answer changes, and change the "Page last updated" date at its foot. Anything that matters also goes in the corrections log. The terms of use cover the rest of the relationship, and the disclaimer covers what this site is not.
Sources
Every factual claim above was checked against these documents on .