Cookie policy
This site stores nothing in your browser. Here is exactly what that means, why there is no consent banner, and how to check it for yourself.
Last updated:
This website uses no cookies at all. Not one. It also writes nothing to any other storage mechanism in your browser. There is no consent banner on this site because there is nothing to consent to, and you should not have to take our word for it — how to verify it yourself is below.
What a cookie is, and why sites use them
A cookie is a small file a website asks your browser to store and send back on subsequent requests. Cookies are how sites remember a login, a language choice or a shopping basket — and also how advertising networks recognise the same browser across different sites in order to build a profile. It is the second use that made consent banners a legal requirement.
What this site stores: nothing
To be exhaustive, because “we only use essential cookies” is a phrase that usually hides something:
| Mechanism | Used here? | Notes |
|---|---|---|
| First-party cookies | No | The server sends no Set-Cookie header. |
| Third-party cookies | No | Nothing is loaded from any other domain, so no other domain can set one. |
| Analytics cookies | No | There is no analytics software of any kind on this site. |
| Advertising cookies and pixels | No | No Meta pixel, no Google Ads tag, no Microsoft UET tag, no affiliate script. |
localStorage | No | Nothing is written or read. |
sessionStorage | No | Nothing is written or read. |
| IndexedDB / Web SQL / Cache API | No | No database is opened and no service worker is registered. |
| Fingerprinting | No | No canvas, font, audio or WebGL probing; no device-characteristic collection. |
| Web fonts and CDN resources | No | The site uses the typefaces already on your system. Nothing is fetched from Google Fonts or any content delivery network. |
The only JavaScript on this site is a single small file, /js/site.js, served from this domain. It does two things: it opens and closes the navigation menu on narrow screens, and it makes sure every commercial link keeps its disclosure attributes. It touches no storage API. You can read it in full at /js/site.js — it is deliberately short enough to read.
Why there is no consent banner
Article 5(3) of the ePrivacy Directive (2002/58/EC, as amended, and as implemented in the Czech Republic in Act No. 127/2005 Coll. on electronic communications) requires informed consent before storing information on, or gaining access to information already stored in, a user’s terminal equipment — with a narrow exemption for what is strictly necessary to provide a service the user has requested.
That obligation is triggered by the act of storing or reading. This site does neither. There is therefore no consent to obtain, and presenting you with a banner would be theatre: a dialogue asking permission for something that is not happening. We consider that worse than useless, because it trains people to click through consent requests without reading them.
The same reasoning applies to the GDPR. Consent under Article 6(1)(a) is a legal basis for processing personal data. We process none from visitors, so we need no such basis. The one processing activity that does occur — ordinary server logging — rests on legitimate interests and is described in the privacy policy.
How to verify this yourself
Please do check. It takes about a minute and it works in any modern browser.
Check that no cookie is set
- Open the developer tools:
F12, orCtrl+Shift+I, orCmd+Option+Ion a Mac. - Go to the Application tab in Chrome or Edge, or Storage in Firefox and Safari.
- Expand Cookies and select
https://valteris.online. The list will be empty. - While you are there, look at Local Storage, Session Storage and IndexedDB. All empty as well.
Check that nothing is loaded from another server
- Open the Network tab and reload the page with
Ctrl+F5. - Look at the domain column. Every single request — the page, the stylesheet, the script, the SVG diagrams, the icon — comes from
valteris.online.
Check the response headers
- In the Network tab, click the first request (the document itself).
- Look at Response Headers. There is no
Set-Cookieheader. - From a terminal you can check the same thing with:
curl -sI https://valteris.online/ | grep -i set-cookie— which returns nothing.
If you ever find any of the above to be untrue, that is a bug and we want to know about it: info@valteris.online.
When you leave this site
This promise covers valteris.online and stops at its boundary. When you follow a link marked “partner link” you arrive at an affiliate network and then at a vendor’s website. Those sites will almost certainly set cookies, including cookies used to attribute a commission, and they will apply their own consent mechanism and their own policy. We have no control over that and we do not receive what they collect. The same applies to the reference sites we link to for sources.
Controlling cookies generally
Nothing needs to be done for this site, but if you want to manage cookies across the web, every major browser lets you view, block and delete them under its privacy or security settings, and offers a private browsing mode that discards them when the window closes. Look for “Cookies and site data” in the settings of Chrome, Firefox, Edge or Safari.
If this ever changes
We have no plan to introduce cookies, analytics or any other form of collection. If that ever changed, we would update this page and its date before the change took effect, describe precisely what was being stored and why, and implement a compliant consent mechanism where the law required one. We would not do it quietly.