Cookie policy
Freighthub is a static site with no login, no forms and no analytics. It sets no cookie for measurement, advertising or personalisation. The only cookie involved in serving a page comes from the hosting provider, and it exists to keep automated traffic from taking the site down.
Cookie categories
| Category | Used here | What it would do |
|---|---|---|
| Strictly necessary | Yes — one host-set security cookie | Keep the site reachable and tell a browser apart from automated traffic |
| Preferences | None | Remember a setting such as language or theme; the site has no such settings |
| Statistics | None | Count visits and see which pages are read; no analytics script is loaded |
| Marketing | None | Follow a reader across sites or target ads; there is no advertising tag or pixel |
The one cookie
| Cookie | Set by | Purpose | Lifetime |
|---|---|---|---|
__cf_bm and similar | The CDN and hosting provider, not Freighthub's code | Distinguish a real browser from automated traffic and keep the service available during abuse or a spike | Short-lived; it expires on its own and is not a persistent identifier |
It is written by the infrastructure that serves the site, is not read by Freighthub, and cannot build a profile of what you read. If the provider changes its cookie set, this table is updated.
Why there is no consent banner
European and UK law requires consent before a non-essential cookie is set. The exception is a cookie strictly necessary to deliver the service the reader asked for, and that is the only kind present. Without the host's security cookie, the provider cannot tell a reader from a bot flood and may not serve the page at all.
A banner would ask permission for something the site does not do, and would have to store the answer — adding a cookie to manage the absence of cookies. If a non-essential cookie is ever introduced, a working consent mechanism will exist before it is set, and this page will name it first.
Local and session storage
None is used: no localStorage, no sessionStorage, no IndexedDB, no service worker, no fingerprinting script. The article pages carry no client-side code at all.
The three calculators on the tools pages run entirely in the browser tab. What you type stays in the page's memory, is not transmitted and is not saved; reloading or closing the tab discards it. There is no saved calculation to clear. Your browser's HTTP cache may keep static files, but that is a cache rather than a cookie or storage record.
Third-party requests
There are none beyond the hosting provider: no Google Fonts or Adobe Fonts, no analytics, no embedded video, no map, no social widget, no advertising pixel. Type uses fonts already on your device, falling back to the system font. The Content-Security-Policy allows its own origin only (default-src 'self'), so a third-party script or font could not load even by mistake. Links to regulators and ports are ordinary links; nothing is requested from them unless you click.
Controlling cookies
| Browser | Where the setting lives |
|---|---|
| Chrome | Settings → Privacy and security → Third-party cookies; on Android, Settings → Site settings |
| Firefox | Settings → Privacy & Security → Cookies and Site Data |
| Safari | macOS: Settings → Privacy → Manage Website Data. iOS: Settings → Apps → Safari → Advanced → Website Data |
| Edge | Settings → Cookies and site permissions → Manage and delete cookies and site data |
Labels move between versions; the settings search box finds the page in any of them. Private windows discard cookies when they close. Blocking third-party cookies is the broadest setting most browsers offer and has no effect here, because the only cookie is first-party. Global Privacy Control and Do Not Track have nothing to act on: there is no tracking to switch off.
If you block cookies
- Reading is unaffected. Every page is static HTML and CSS.
- The bot check may repeat. Each request may be re-checked; a challenge loop is worth reporting.
- No feature is lost. There are no preferences or saved state to degrade.
- Calculators still work. They need JavaScript, not cookies.
Related
Privacy policy — what is processed and why ·Terms of use — the basis on which the site is published ·Accessibility ·Contact