Privacy
PaceBoss is local-first. Your race data stays on the device you load it on. The architecture isn't a privacy policy — it's how the tool is built: there is no server that could receive your data, because nothing is sent.
What lives on your device
All state is written to your browser's storage. Nothing travels to a server we operate.
| What | Where | Purpose |
|---|---|---|
| Theme settings (accent colour, dark/light mode, pace-band toggle) | localStorage |
Remembers your visual preferences between visits |
| The most recent imported CSV (raw text + parsed workspace) | IndexedDB |
Powers the "Resume last session" shortcut so you don't have to re-import after a refresh |
One IndexedDB key (last) and one localStorage key (acc-explorer-settings). Both can be cleared at any time via Clear all local data on the import screen.
The one external service
The site includes Vercel Analytics. It records anonymous page views and basic performance metrics — response times, error rates, browser type. It does not see your imported race data. It does not use cookies. It does not fingerprint visitors. It has no access to driver names, lap times, sector splits, or anything else in your CSV.
Bug reports
If you submit feedback through the in-app form, that goes to a third-party form host (Tally) and contains only what you type. Your imported CSV is never attached automatically.
Why local-first
Race telemetry contains server names, league names, driver identities, and finishing positions you may not want broadcast. A local-first design is the simplest guarantee that none of that leaks: if your data never leaves your device, it can't end up anywhere you didn't put it.
If you want to share a result, the Export PNG button on the results and driver pages produces a screenshot you control entirely.