Privacy Policy
Last updated: June 1, 2026
Your privacy matters to us. This policy explains what information RailSeat collects and how it is used.
1. Information We Do Not Collect
RailSeat does not require you to create an account, log in, or provide any personal information. We do not collect your name, email address, phone number, or payment details.
2. Query Data
When you search for seat vacancies, the train number, station codes, journey date, and class you enter are sent directly from your browser to the IRCTC API. RailSeat does not log or store these queries on our servers.
3. Analytics
We use Google Analytics to understand aggregate usage patterns (page views, session counts, device types). This data is anonymised and does not identify individual users. You can opt out of Google Analytics by installing the Google Analytics Opt-out Browser Add-on.
4. Cookies & Local Storage
RailSeat stores your language preference and theme (light/dark) in your browser's local storage so that your settings persist between visits. No tracking cookies are set by RailSeat itself.
5. Service Worker & PWA
If you install RailSeat as a Progressive Web App, a service worker is registered in your browser to enable offline access to the app shell. No personal data is stored in the service worker cache.
6. Third-Party Services
- IRCTC APIs — vacancy data is fetched live; IRCTC's own privacy policy governs those requests.
- Google Analytics — anonymised usage analytics (see Section 3).
- Google Fonts / Vercel — font assets and hosting; standard request logs may be kept per their respective policies.
7. Children's Privacy
RailSeat is not directed at children under the age of 13. We do not knowingly collect any information from children.
8. Changes to This Policy
We may update this Privacy Policy periodically. The "last updated" date at the top of this page will reflect any changes.
9. Contact
Questions about this Privacy Policy? Visit our Support page.