Small print
Cookie policy
The short version is that this site sets no cookies whatsoever. Not one, not even a strictly necessary one. What we do use is two named items of local storage, which stay inside your browser and are never transmitted anywhere, and this page lists both of them in full.
Last reviewed: 4 August 2026. For everything else concerning personal data, see the privacy policy.
Cookies proper: none
A cookie is a small file that a site asks your browser to store and then send back with every subsequent request, which is what makes cookies useful for logging in and useful for tracking. Joremalix has no accounts to log into and nothing to track, so we set none. You can confirm this yourself: open your browser’s developer tools on any page of this site, look under storage, and the cookie list for this domain will be empty.
Because we set no cookies and use no third-party services that might set them, there is no cookie consent decision for you to make here. The small panel you may have seen on your first visit is not a cookie banner; it is a notice about the two local-storage items described below, and it exists because we would rather over-explain than quietly write things into your browser.
The two items we do use
Local storage differs from a cookie in one respect that matters a great deal: it is never automatically attached to a network request. Data written into local storage sits in your browser profile and can only be read by scripts running on this same site. Nothing here leaves your machine.
| Item name | Contents | Purpose | Necessary? | Lifetime |
|---|---|---|---|---|
jm.notice.state |
One of two words: accepted or essential |
Remembers which button you pressed on the storage notice, so that it does not reappear on every page you read | Strictly necessary. Without it the notice cannot know it has already been answered | Until you clear site data, or roughly twelve months of inactivity if your browser prunes storage |
jm.reading.count |
A single whole number, incremented once per page view. Nothing else — no page names, no dates, no identifier | Lets us show a small “pages read” figure on the front page and gives the desk a rough sense of whether the log is being used at all | Optional. Only written if you chose “That’s fine” on the notice | Until you clear site data |
That is the complete list. There is no third item, no session storage, no IndexedDB database, no service worker cache and no fingerprinting of any kind. If you choose “Keep only the essentials” on the notice, the second item is never created, and if it already existed from a previous visit it is deleted at that moment.
What the reading count cannot do
It is worth being precise about this, because a counter sounds more invasive than it is. The number stored is a total, held only on your device, and it does not record which entries you read or in what order. Nothing about it is sent to us — we genuinely do not receive it — so the figure shown on the front page is your own count read back to you, not a site-wide statistic.
The desk therefore has no audience analytics at all. We know how many entries we have published and we know how many emails arrive; beyond that we work partly in the dark, which is a trade we have accepted deliberately.
No third parties, and why that is unusual
Every file this site needs is served from this domain. The stylesheets, the icon font, the two typefaces and the collage images are all stored alongside the pages, which is why there is not a single request to an outside host when you load a page. We use no content delivery network, no font service, no embedded video, no social media widget, no comment platform, no advertising network, no tag manager and no analytics product, whether privacy-friendly or otherwise.
- No Google Analytics, Plausible, Fathom, Matomo or any equivalent
- No advertising or retargeting pixels, and no affiliate tracking in any link
- No social sharing buttons, which are among the most common quiet trackers
- No externally hosted fonts, icons or scripts
- No consent management platform, since there is nothing here to obtain consent for beyond one optional counter
Removing the two items
You can delete both at any time without affecting your ability to read anything. The site works identically with empty storage; you will simply see the notice again on your next visit.
Open settings, then privacy and security, then choose the option for site settings and find this domain in the list of stored data. Selecting it and clearing the data removes both items. Alternatively, with this page open, press the key combination that opens developer tools, choose the application or storage tab, expand local storage, and delete the two entries by name.
Open settings, then the privacy and security panel, then manage data under cookies and site data. Search for this domain, select it, and remove it. Firefox groups local storage with cookie data in this dialogue even though we set no cookies, so removing the entry clears both of our items.
On macOS, open Safari settings, choose the privacy panel, then manage website data, find this domain and remove it. On iOS or iPadOS, open the Settings app, scroll to Safari, choose advanced and then website data, then swipe to delete the entry for this site. Using private browsing also prevents either item from persisting beyond the session.
All major browsers allow you to block site data for a specific domain, and most privacy extensions can disable local storage entirely. If you do this, the storage notice will appear on every page because it cannot remember your answer, and the reading counter will stay at zero. Nothing else on the site is affected: the genre filter, the folding sections and the inbox form all work with storage completely blocked, because none of them depends on it.
The inbox form and storage
Filling in the form on the inbox page writes nothing to your browser. The fields are checked in the page itself so that you get an immediate answer about anything missing, and the contents are not saved as a draft, cached, or retained if you navigate away. Once submitted, what happens to the message is covered by section 2 of the privacy policy.
If this page becomes inaccurate
A cookie policy that has drifted away from what the site actually does is worse than none, so we treat an error here the same way we treat a factual error in a write-up. If you inspect this site and find storage we have not declared, or a request going out to a host we have not mentioned, tell us and it will be either removed or documented, and the change will appear in the public correction log.
Found something we missed?
We would genuinely like to know
Undeclared storage would be a serious slip. The correction log on the inbox page is where any fix would be recorded, with a date.