Cookie policy

Effective 22 September 2026 · Publisher: Boyuk Group, s.r.o.

1. What a cookie is, and why sites ask

A cookie is a small piece of text a website asks your browser to keep and hand back on every later request. It is what lets a site recognise a returning browser. Article 5(3) of the ePrivacy Directive (2002/58/EC, as amended by 2009/136/EC) says that storing information on, or gaining access to information already stored on, a user’s terminal equipment requires that user’s informed consent, unless it is strictly necessary to deliver a service the user asked for.

That is the rule the consent banners exist to satisfy. We took the other route: we removed the storage instead of asking permission for it.

2. The complete list of what we store

The table has no second half. That is the entire inventory.

3. Why there is no consent banner

A consent banner is required when a site stores or reads information on your device beyond what is strictly necessary. This site does neither, so there is no legal basis question to resolve and nothing for you to agree to. Showing you a banner anyway would be theatre, and it would make you click something for no reason.

Separately: the small amount of personal data that does arise from an ordinary visit — the web-server access log — is not covered by the cookie rules at all, because it is recorded on our server rather than on your device. It is described in full in section 3.1 of the privacy policy, and it is deleted after fourteen days.

4. How to check this yourself

Do not take our word for it. Verifying the claim takes under a minute in any modern desktop browser.

Check for stored data

1. Press F12 (or Cmd+Option+I on a Mac) to open the developer tools.
2. Open the Application tab in Chrome or Edge, or Storage in Firefox and Safari.
3. Look under Cookies, Local Storage, Session Storage, IndexedDB and Cache Storage for the entry https://miranov.online. Every one of them should be empty.
4. Reload the page with the panel open and watch: nothing appears.

Check for third-party requests

1. Open the Network tab, tick Disable cache, and reload.
2. Sort by Domain. Every request should be to miranov.online and nothing else — no fonts.googleapis.com, no CDN, no analytics endpoint.
3. Check the Response Headers of the document request. There is no Set-Cookie header.

The one-line version

Open the Console tab and type:

document.cookie

It returns an empty string. You can also run localStorage.length and sessionStorage.length; both return 0.

5. JavaScript on this site

One small script runs, at /js/cta.js. You can read the whole of it — it is served unminified. It does exactly two things: it copies campaign parameters such as utm_source from the address you arrived on into the outgoing partner link, and it re-applies the rel="sponsored nofollow noopener" markers to those links. It reads no storage, writes no storage and contacts no server. The site works fine with JavaScript disabled.

6. Where the promise ends

It ends at the edge of this domain. If you follow a partner link, the affiliate network and the advertiser on the other side will almost certainly set cookies, because that is how they know which site to pay. We cannot control that and we do not pretend to. What we can tell you is that nothing is set before you decide to click, and that the links are labelled so the decision is yours. See the affiliate disclosure.

7. Blocking cookies generally

Nothing on this site needs adjusting, but if you want to tighten your browser generally, every major browser lets you block third-party cookies or all cookies in its privacy settings. Doing so will not change anything about how miranov.online behaves.