Cookie policy
This website stores nothing on your device. No cookies. No
localStorage, no sessionStorage, no IndexedDB, no cache-based
identifiers. Nothing is loaded from any other domain, so no third party can set anything either.
There is no consent banner on this site because there is nothing to consent to.
1. What cookies and similar technologies are
A cookie is a small piece of text a website asks your browser to keep and send back on later
requests. Browsers also offer other places to keep data — localStorage,
sessionStorage, IndexedDB, the cache — and all of them can be used to recognise a
returning browser. European law treats them together: storing information on a user's device, or
reading information already stored there, requires prior consent unless it is strictly necessary to
provide the service the user asked for.
2. Which of them this site uses
None. There is no cookie table below because there are no cookies to list. That is not a drafting shortcut; it is the design of the site.
| Mechanism | Used on this site |
|---|---|
| First-party cookies | None |
| Third-party cookies | None — no third-party content is loaded at all |
| localStorage / sessionStorage | None |
| IndexedDB / Web SQL | None |
| Analytics or tag manager | None |
| Advertising or conversion pixels | None |
| Web fonts or CDN assets | None — system fonts only, everything self-hosted |
| Device or browser fingerprinting | None |
3. Why there is therefore no consent banner
Article 5(3) of the ePrivacy Directive (2002/58/EC, as amended by 2009/136/EC, implemented in the Czech Republic in Act No. 127/2005 Coll.) requires consent before storing information on, or gaining access to information stored in, a user's terminal equipment. The obligation is triggered by the act of storing or reading. If a site stores nothing and reads nothing, the obligation does not arise and there is nothing for a banner to ask about.
We think a consent banner on a site like this would be worse than useless: it would train you to click "accept" on a question that was never asked, and it would itself have to store your answer — meaning the banner would be the only thing on the site writing to your device. So we removed the collection instead of adding the banner.
4. How to verify this yourself
Do not take our word for it. Any modern desktop browser will show you, in well under a minute.
Chrome, Edge, Brave and other Chromium browsers
- Open this page, then press
F12(orCtrl+Shift+I; on macOSCmd+Option+I) to open DevTools. - Choose the Application tab. In the left-hand panel under Storage,
click Cookies →
https://krasovin.online. The list is empty. - Still under Storage, check Local storage, Session storage and IndexedDB. All empty.
- Switch to the Network tab and reload the page with
Ctrl+R. Every row in the list is onkrasovin.online— the HTML document, the stylesheet, one script and the SVG diagrams. Nothing else. - Click any row and look at the Response Headers. There is no
Set-Cookieheader.
Firefox
- Press
F12, then open the Storage tab. Inspect Cookies, Local Storage, Session Storage and Indexed DB: all empty for this origin. - The Network tab, after a reload, shows only requests to this domain.
Safari
- Enable the Develop menu: Safari → Settings → Advanced → "Show features for web developers".
- Develop → Show Web Inspector, then the Storage and Network tabs, as above.
Without developer tools
Click the padlock or the "site information" icon next to the address bar. Every major browser shows a cookie and site-data count there. For this site it reads zero.
5. The one piece of JavaScript on this site
There is exactly one script, /js/cta.js, served from our own domain. You can read
all of it — it is under sixty lines. It does one thing: if the address you arrived on already
contains advertising campaign parameters, it copies those same parameters onto the outgoing partner
link, and it makes sure that link keeps its rel="sponsored nofollow noopener"
attributes. It performs no network request, reads no device information and writes to no storage
area. The site works perfectly well with JavaScript disabled.
6. What happens after you leave
When you follow a partner link you arrive on a vendor's website. That vendor and its affiliate network will generally set their own cookies in order to attribute a sale, and their own cookie notice and consent mechanism apply there. We have no control over and no visibility into that; it happens on their domain, under their policy, after you have left ours. The privacy policy describes the outbound journey in more detail.
7. Server logs are not cookies
For completeness: the web server that delivers these pages writes a standard, short-lived access log, as every web server does. That is a record on our side, not storage on your device, and it is not a cookie. It is described in section 3 of the privacy policy.
8. If this ever changes
If we ever introduced anything that stored or read data on your device, we would update this page first, state exactly what it is and why, and — for anything not strictly necessary — ask for your consent before setting it. As of the effective date above, we have no plan to do so.