Cookie Policy
Updated:
This site sets no cookies. Not first-party, not third-party, not analytics, not advertising. That is why you were never shown a consent banner: under Article 5(3) of the ePrivacy Directive (2002/58/EC, as amended by 2009/136/EC), consent is required for storing or accessing information on your device — and where nothing is stored beyond what you asked for, there is nothing to consent to.
The one thing stored on your device
The site remembers whether you chose the light or dark theme. That preference is written to your browser’s localStorage under a single key:
jvm-scope-theme → "light" | "dark" | "system"| Property | Value |
|---|---|
| Storage type | localStorage, not a cookie |
| Sent to the server | Never — localStorage is not attached to HTTP requests |
| Contains | One word describing a display preference |
| Personal data | None; it identifies a setting, not a person |
| Lifetime | Until you clear it |
| Purpose | Rendering the page in the theme you picked, without a flash of the wrong one |
This falls squarely inside the “strictly necessary to provide a service explicitly requested by the subscriber or user” exemption in Article 5(3): you asked for the dark theme by clicking the toggle, and honouring that across pages is the service. It is created only when you use the toggle. If you never touch it, nothing is written at all.
To remove it: clear site data for jvmscope.com in your browser settings, or use a private window. The site will fall back to your operating system’s colour scheme preference, which it reads without storing anything.
Audience measurement without cookies
Where audience measurement is enabled, this site uses Cloudflare Web Analytics. It counts page views without setting a cookie, without a device fingerprint, and without any cross-site identifier. There is no way to follow a single reader from one article to the next, which is a deliberate limitation, not an oversight. Because it stores nothing on your device and reads nothing from it, the Article 5(3) consent requirement does not apply.
Details of what it reports are in the privacy policy.
No embedded third parties
Articles here contain no embedded video players, no social media widgets, no comment platform, no like buttons and no externally hosted fonts or scripts. Every asset a page needs comes from jvmscope.com. This matters for a cookie policy because embeds are the usual route by which a site that “sets no cookies” ends up setting several — and it is why this page can make an unqualified claim rather than a hedged one.
Links to other sites are ordinary links. Once you follow one, that site’s own cookie and privacy practices apply, and this policy stops being relevant.
Local storage is not a cookie, and the difference matters
The two are often treated as interchangeable in privacy notices, which obscures a real distinction. A cookie is attached to every HTTP request to the domain that set it, so its contents travel to the server automatically, on every page load, whether or not the server wants them. localStorage is read only by script running on the page and is never transmitted anywhere by the browser.
That difference is why the theme preference described above is a genuinely local setting rather than a server-visible identifier. The value never leaves your device. There is no server-side session it corresponds to, no log line it appears in, and no way for this site’s operator to read it.
Both mechanisms are covered by the same Article 5(3) rule, which is written in terms of “storing information, or gaining access to information stored, in the terminal equipment of a subscriber or user” rather than in terms of cookies specifically. That is why this page exists at all: the exemption has to be justified, not assumed.
What the server sees regardless
Serving a page requires processing your IP address and the details of the request. That happens at the network level, has nothing to do with cookies or local storage, and cannot be switched off without also switching off the ability to send you the page. It is covered in section 2 of the privacy policy, along with the retention period and the legal basis.
The distinction worth holding onto is that this processing is transient and technical, while a cookie would be persistent and device-resident. This site does the first and not the second.
Controlling it from your side
Because nothing here tracks you, there is little to configure. For completeness:
- Clearing the theme preference: clear site data for jvmscope.com, or browse in a private window.
- Blocking scripts entirely: the site renders and reads correctly with JavaScript disabled. You lose the theme toggle, the search dialog and the copy-to-clipboard buttons on code blocks; the articles themselves are plain HTML and are unaffected.
- Blocking the analytics beacon: any content blocker will do so, and nothing on the site depends on it. Page counts will simply be slightly lower than reality, which is a cost borne by the operator and not by you.
Do Not Track and Global Privacy Control
Neither signal changes anything here, because there is no tracking to switch off.
Changes
If a cookie is ever introduced — for example by adding a feature that genuinely requires one — this page will be updated before that happens, and a consent mechanism will be in place first for anything outside the strictly-necessary exemption.