1. What our websites set
- Our public pages (this site and clearlineprotocol.com) set no cookies and use no analytics, advertising or tracking tools.
- The RailOps applications keep your sign-in session and working copies of records on your device so crews can work without signal. That is storage you control, not tracking.
- Nothing on your device is used to profile you or shared with advertisers.
When you read a public page, our host (Netlify) logs your IP address, browser description, the page and the time to deliver the page and protect the site from abuse, and keeps those logs for a short period (see the Privacy Policy, section 4). No cookie is set. Forms are protected against automated submissions with a hidden field rather than with a tracking service.
The demonstration pages behind sign-in keep your sign-in session, and the time your visit was last recorded, in your browser's local storage for as long as you stay signed in.
2. What the RailOps applications store on your device
The RailOps portal, the crew application and the customer application are installable web applications. They store, in your browser's local storage and in its database (IndexedDB), and only for the site itself:
| What | Why | How long |
|---|---|---|
| Your sign-in session (a token issued by our authentication provider, Supabase) | So you stay signed in between screens and visits | Until you sign out, the session expires, or an idle office account is signed out automatically |
| Copies of recently viewed records (tracks, cars, jobs, lists) and the changes waiting to be sent | So crews can keep working where there is no signal; changes are sent when signal returns | Refreshed as you work; cleared on sign-out |
| Server answers cached for up to 24 hours | So the application opens quickly | Up to 24 hours |
| Which database this copy of the application belongs to (app-config.json) | So an installed application can start without signal | Until replaced |
| Markers that you have accepted the current Terms of Use, the evaluation notice (on the demonstration) and the AI notice | So you are not asked on every screen; the acceptance itself is recorded in the database | For the browser session |
| Small preferences: the last screen, a collapsed panel, the chosen yard | Convenience | Until cleared |
None of this is read by anyone but the application on your device. Signing out clears the working copies and the session. On a shared or lost device, also clear the browser's data for the site or remove the installed application.
3. Content from other providers
Some screens inside RailOps load content from other companies' servers, which receive your IP address and browser description when that happens and may set their own cookies under their own policies: map images from OpenStreetMap (the jobs and rail map screens), Google Fonts (the rail map page), and the pdf.js library from Cloudflare's cdnjs (the Demurrage Calculator). We set no cookies for them and pass them nothing about you. Our public pages load nothing from other companies.
4. Clearing it
Sign out of RailOps to clear the session and the working copies. To remove everything, clear your browser's site data for the application's address, or uninstall the installed application. On a work device your railroad's own policy applies.
5. Why there is no cookie banner
A banner asks consent for cookies that track or advertise. We set none, so there is nothing to consent to. Storage inside the applications is necessary for them to work and is described above instead of asked about. If that ever changes, this page and the Privacy Policy will say so first, and a banner will appear where the law requires one.
6. Changes
We will post changes here with a new version and effective date. The version is cookies-2026-10-29.
7. Contact
Questions: sales@clearlineprotocol.com with "Privacy" in the subject line.