Cookie policy
Rail Buddy, operated by RailBuddy, uses very few cookies, none of them optional and none for analytics or advertising. This page lists all of them.
Last updated 30 July 2026
The short version
- The cookie that keeps you signed in is strictly necessary. Without it the service cannot work, so it is not optional.
- No analytics runs anywhere — not on the public pages, and not on the driver or planner surfaces, where your position is in play.
- We set no advertising cookies and share nothing with advertising networks.
Strictly necessary cookies
| Name | Purpose | Lasts |
|---|---|---|
RAILBUDDY_SESSION |
Keeps you signed in. A random identifier — it holds no personal information itself. Deliberately long-lived: a driver should not be signed out mid-trip, or asked for a PIN in a section with no coverage. | Up to 30 days |
XSRF-TOKEN |
Protects forms against cross-site request forgery. | Session |
These cookies are marked HttpOnly (not readable by JavaScript),
SameSite=Lax (not sent on cross-site requests) and, in production,
Secure (sent only over HTTPS).
Browser storage that is not a cookie
These are stored in your browser's local storage. They stay on your device and are never sent to us or to anyone else.
| Key | Purpose |
|---|---|
rb-theme | Your light/dark theme preference, applied before first paint so the cab display does not flash |
Your live position is handled in the page and never stored anywhere — not in a cookie, not in local storage, and not on our servers. See the privacy policy.
Blocking cookies
You can block or delete cookies entirely in your browser settings. Blocking the strictly necessary cookies will stop you being able to sign in.
Changes to this policy
If we add or remove a cookie, this page changes with it and the "last updated" date above moves. Questions: [email protected].