Cookie policy
This website stores nothing on your device. No cookies, no localStorage, no sessionStorage, no IndexedDB, no service worker. That is not a preference setting — the collection is simply not there, and you can check that yourself in about thirty seconds.
The whole policy, in one line
Celusagruna s.r.o. does not set, read or permit any cookie or comparable technology on miravain.online.
Why there is no consent banner
Under Article 5(3) of the ePrivacy Directive (2002/58/EC), as implemented in the Czech Republic by Act No. 127/2005 Coll. on electronic communications, a website needs your prior consent before it stores information on your device or gains access to information already stored there — unless that storage is strictly necessary to deliver the service you asked for.
Consent is required for storing or accessing. We do neither. There is nothing to consent to, so asking you to consent would be theatre: a banner that exists to look compliant rather than to give you a choice that matters.
We also think the honest version is better for you. A consent banner asks you to trust a promise about what happens after you click. This page asks you to trust nothing — it tells you how to check.
How to verify it yourself
Do this on this very page. It takes about half a minute and needs no software beyond the browser you are already using.
Chrome, Edge, Brave and other Chromium browsers
- Press F12 (or Ctrl+Shift+I; Cmd+Option+I on a Mac) to open developer tools.
- Open the Application tab.
- In the left sidebar under Storage, click through
Cookies, Local storage, Session storage,
IndexedDB and Cache storage. Every one of them should be
empty for
https://miravain.online. - Now open the Network tab and reload the page with
Ctrl+R. Look at the Domain column — you can add
it by right-clicking the column headers. Every single request should be to
miravain.online. There should be no request to Google, no font service, no CDN, no analytics endpoint. - Still in the Network tab, click the document request and look at the
Response Headers. There should be no
Set-Cookieheader.
Firefox
- Press F12 and open the Storage tab. Check Cookies, Local Storage, Session Storage, IndexedDB and Cache Storage. All empty.
- Open the Network tab, reload, and confirm every request goes to miravain.online.
Safari
- Enable the Develop menu: Safari → Settings → Advanced → Show features for web developers.
- Open Develop → Show Web Inspector, then the Storage and Network tabs, and check the same things.
Without developer tools
Use curl -I https://miravain.online/ from a terminal and look at the response
headers. There is no Set-Cookie line.
If you ever find a cookie here, that is a bug and we want to know. Send what you found to info@miravain.online and we will fix it and say so publicly.
What the one script on this site does
This site loads a single small JavaScript file, /js/cta.js, served from our
own server. You can read the whole thing: it is about thirty lines.
It does exactly two things. First, when you arrive from an advertisement, it copies the
campaign parameters from the address bar onto the outbound partner link, so the advertiser can
attribute the visit to the right campaign. Those parameters describe the campaign, not you.
Second, it re-applies the rel="sponsored nofollow noopener" attributes to every
partner link, so the sponsored-link disclosure cannot be lost.
It reads no storage, writes no storage, sets no cookie and makes no network request. The site works without JavaScript: turn it off and every page still renders and every link still works.
Third parties
There are none on this site. Nothing is embedded, nothing is loaded remotely, no font is fetched from Google, no library is pulled from a CDN, no image is hotlinked.
What we cannot do is control the other side of a link. If you follow a partner link, you leave miravain.online, and the site you land on will have its own cookie practices and its own banner. Read theirs there. Ours ends at our boundary.
Changes
If this ever changes — if we were ever to introduce anything that stores data on your device — we would update this page first, and we would implement a genuine consent mechanism before the storage began, not after.
Last updated: 23 September 2026. See also the privacy policy.