Cookies and storage
1. Current setup
The website code sets no cookies and installs no behavioural analytics, advertising trackers or third-party embeds. It does not use local storage, session storage, IndexedDB or a service worker to preserve visitor preferences.
There is no “accept all” banner because this baseline has no non-essential tracking tools to enable. A decorative consent banner would not improve this implementation’s accuracy.
2. Selections and drafts
Archive selections and correction-draft fields are handled in page memory. The application does not save them as a persistent profile. Clearing selections restores the archive; resetting the draft clears its fields and text preview.
A browser may restore a page or form through its own history features. That behaviour is separate from a website-managed draft store.
3. Downloads and the clipboard
A CSV or text download is a file you choose to save on your device, not a tracking cookie. A copied draft is placed on your clipboard when that operation is available. Files and clipboard contents may remain after you leave the page.
Manage those copies using your device’s own controls. The website does not remotely retrieve or delete them.
4. Hosting-related mechanisms
A chosen host or delivery service may use technical caching, security mechanisms or request logs. Such infrastructure is not configured by the page’s filtering script, and its exact behaviour depends on deployment.
The absence of application cookies does not prove the absence of every technical mechanism at hosting level. See the privacy explanation of technical requests.
5. If the setup changes
Adding non-essential measurement or advertising tools would require an accurate inventory and an appropriate choice mechanism before those tools load. Rejecting and managing choices should be as accessible as accepting them.
A banner alone cannot make every deployment compliant. This page describes the no-tracker baseline, not permission for undisclosed future additions.