Local controls, one saved banner choice

1. What this build installs

The supplied application sets no cookies and uses no sessionStorage, IndexedDB or service worker. It installs no analytics or advertising trackers. It uses one localStorage entry, bopliostorycrats.consent, solely to remember whether you selected Accept or Decline in the site-wide banner.

Both choices keep tracking off. Neither loads an optional service, and neither stores archive filters, correction drafts or mini-game history. The saved banner choice has no application-set expiry and remains until you change it or clear this site’s browser storage. It applies across pages on the same website origin in the same browser profile, not across devices or different browsers.

Use Cookie settings in any page’s footer to review or change your choice. Before a choice is made, the banner appears on every page. Afterwards, it stays hidden unless you open settings or clear the stored choice. If browser storage is blocked, the choice applies to the current page but cannot be remembered on other pages. Without JavaScript, the banner and its storage mechanism do not run.

2. Temporary page state

Archive filters and correction-draft fields are held in page memory while you use the page. Reset filters restores the full record selection. Reset draft clears the local draft tool. The Lucky Number Reveal activity also keeps its revealed numbers and visit counter in page memory only. Apart from the banner choice described above, this website does not save your choices as a profile or carry them into a later visit using persistent application storage.

3. Downloads, clipboard and browser history

If you request a CSV or text download, your browser can save that file to your device. Copy text uses the clipboard when permitted. Those copies are outside the website’s memory and are not removed by resetting the page.

The homepage date search puts its query into the archive URL. Your browser can retain that URL in its history. Browser caching, autofill and session restoration are controlled separately by your browser, not by a website preference database.

4. Hosting-related mechanisms

A deployed host or security layer may use technical mechanisms or logs to deliver and protect pages. Their exact operation depends on the actual hosting setup; this static build does not configure or certify them. See Privacy: technical delivery for the distinction between local tools and serving a website.

5. If the implementation changes

Any later non-essential integration needs an accurate inventory and appropriate consent controls before loading, with equally accessible reject and manage choices. The current banner choice must not be treated as permission for future trackers. A banner by itself does not make every deployment compliant. This page describes the present zero-tracker build, not hypothetical analytics vendors.