Cookie and Local Storage Policy for This Reference

01 Purpose of this page

This page explains how the documentation site at orderflow-metrics.org treats cookies and other forms of local storage. It is written for readers who want a plain account of what a browser may keep after a visit, and it distinguishes clearly between items the site creates and items the browser creates on its own initiative.

A cookie is a small labelled note that a web server asks a browser to keep and to send back on later visits. Local storage is a similar holding area that a page can use to keep a value. Both live inside the browser profile, not on the host.

02 What this site sets

The site sets no cookies of its own, and no page writes to local storage, session storage or an index database. Every document is static HTML and CSS served from one host, so there is no code on the pages that could place a note in the browser.

Plain statement There is no consent banner on this site, because there is nothing to request consent for. No first-party cookie, no third-party cookie and no storage key is created by any page.

Because the site is stateless, a reader who returns tomorrow arrives as a stranger to the host. Nothing about the previous visit is remembered by the site itself, and no preference is carried from one page to the next by the site.

03 What a browser may keep regardless

Browsers keep their own copies of files in order to render pages faster. This is ordinary client-side behaviour and happens for every site, with or without cookies. Four common categories are worth naming.

Network cache

Copies of the style sheet, images and pages, so a repeat visit loads quickly.

Back-forward cache

A short-lived snapshot of a page held while a reader moves through history.

Form memory

Optional browser-side recall of typed values, controlled by the reader.

History record

The list of visited addresses kept by the browser itself.

None of these is placed by the site. Each is a feature of the reader's own software and is governed by that software's settings rather than by anything on these pages.

04 Clearing storage in common browsers

A reader who wants a clean slate can do so from the browser's own settings panel. The steps are broadly alike across the major families of software, though the wording differs.

1. Open the settings or preferences area of the browser.
2. Find the section on privacy, or on browsing data.
3. Choose the items to remove, such as cached files and site data.
4. Select the time range, for example the last hour or all time.
5. Confirm the removal and reload this page to rebuild what is needed.

A private or incognito window discards its storage when it closes, which is another simple way to leave no trace on a shared machine. Removing cached files only slows the next visit; it changes nothing about the page content, and it does not affect any record on the host.

05 No advertising or analytics cookies

No advertising network, measurement service or tag manager is attached to this site. No page asks a remote host to load a picture, a font or a counting pixel. There is therefore no cross-site profile to build and no identifier to sell, rent or pass along.

The desk keeps its own availability notes at the hosting layer, as described on the privacy policy page, and those notes are technical lines rather than browser storage. They are not linked to a reader and are discarded on a rolling schedule.

06 Inventory of storage items

The table below lists the items a reader might encounter, states who creates each one, and gives its usual lifetime. The first row is the only one that concerns the site, and it is empty by design.

Readers with questions about this inventory may write to [email protected] or use the postal address on the contact page. This page was last reviewed on 12 October 2026 and will be revised if the site's technology ever changes.