Storage and privacy
Everything the widgets store on a visitor's device, and what we do with the requests they make.
No cookies and no identifiers: only the settings a visitor saves, in localStorage on your domain, never sent to us.
Every key the bundle can write
Keys are namespaced per embed, so two widgets on the same page never collide. A widget that is not on the page writes nothing: a calculator-only embed stores nothing at all.
| Key | Purpose | Lifetime | Lawful basis |
|---|---|---|---|
| oddsrelay:om:filters:<embed>Oddsmatcher, when the visitor saves a filter set | Remembers named filter sets so the visitor does not rebuild them on every visit. | Until cleared. No expiry is set. | Strictly necessary: it is functionality the visitor explicitly asked for by saving. |
| oddsrelay:om:commissions:<embed>Oddsmatcher, when the visitor sets a per-exchange commission | Their exchange commission rate, so the money column is right without asking twice. | Until cleared. No expiry is set. | Strictly necessary: a preference the visitor entered, used only to compute what they see. |
If localStorage isn't available (private browsing, blocked storage, a sandboxed iframe), the widgets still work; they just don't remember settings.
How a visitor clears it
Each widget clears its own data in its own interface: saved oddsmatcher filter sets have a delete control, and a saved commission is overwritten in place. Everything is also removed by the browser's standard "clear site data" for your domain. If you want a button of your own:
// Clear everything an OddsRelay widget has stored on this origin.
Object.keys(localStorage)
.filter(function (k) { return k.indexOf("oddsrelay:") === 0; })
.forEach(function (k) { localStorage.removeItem(k); });Request data
The live odds widget calls our API from the visitor's browser, so our API logs receive the request: your origin, the key it was made with, and standard request metadata. We use it for two things:
- Operating and improving the product: error rates, latency, which features get used.
- Reporting your own usage back to you: how often your embeds rendered, and where.
We don't use it for advertising, personalisation, cross-site profiling or lead generation, and we don't sell or share it.
The calculators make no network requests, so we can't see them.
For this site and the API, see our privacy policy.