Cookie policy
This website stores nothing on your device. No cookies, no localStorage, no sessionStorage, no IndexedDB, no cache-based identifiers, no fingerprinting, and no requests to anybody else’s server. That is the whole policy. Everything below explains it and shows you how to check it for yourself.
1. What we store: nothing
| Mechanism | Used here? | Notes |
|---|---|---|
| HTTP cookies (first-party) | No | The server sends no Set-Cookie header on any page. |
| HTTP cookies (third-party) | No | There are no third-party resources on the page that could set one. |
| localStorage / sessionStorage | No | The single script on this site contains no storage call at all. |
| IndexedDB / Web SQL | No | Not used. |
| Service worker / cache identifiers | No | No service worker is registered. |
| Analytics (any provider) | No | No Google Analytics, no Matomo, no self-hosted counter. |
| Advertising or conversion pixels | No | No Meta pixel, no Microsoft UET tag, no Google tag, no tag manager. |
| Web fonts from a CDN | No | The page uses your device’s own system fonts, so nothing is fetched and no IP address is disclosed to a font host. |
| Embedded video, maps, social widgets | No | None on any page. |
| Device fingerprinting | No | No canvas, audio, font or WebGL probing. |
2. Why there is no cookie banner
Article 5(3) of the ePrivacy Directive — the rule that consent banners exist to satisfy — requires your consent before a site stores information on your device or gains access to information already stored there. It is a rule about storage and access. Where a site stores nothing and accesses nothing, the rule is not engaged, and there is nothing to ask you to consent to.
We could have added a banner anyway, for appearances. We think a consent dialogue that asks permission for something that is not happening is worse than no dialogue: it trains people to click through prompts without reading them. So we removed the tracking instead of adding the banner. A banner you never see is the honest form of a cookie notice.
Note on what changed. An earlier version of this site did show a consent banner, and earlier versions of this page and the privacy policy described analytics and advertising cookies. Those descriptions did not match what the site actually did, and the machinery has now been removed altogether. This page describes the site as it is today.
3. How to verify this yourself
Please do not take our word for it. Any modern desktop browser can prove or disprove this page in under a minute. Open the developer tools with F12, or Ctrl+Shift+I (Cmd+Option+I on a Mac), then:
Check the storage
- Chrome or Edge: the Application tab → Storage. Look at Cookies, Local storage, Session storage and IndexedDB for
miravest.online. All four should be empty. - Firefox: the Storage tab — same four entries, same expected result.
- Safari: enable the Develop menu in Settings → Advanced, then Develop → Show Web Inspector → Storage.
- Click Storage → Clear site data first if you want to be sure you are not looking at something an older version of this site left behind.
Check the network requests
- Open the Network tab and reload the page with Ctrl+F5.
- Sort by Domain. Every single row should be
miravest.online: the page itself,/css/site.css,/js/cta.js, the SVG diagrams and the favicon. There should be no other domain in the list. - Click the document row and read the Response headers. There is no
Set-Cookieheader.
Check from the console
Open the Console tab and run these three lines. On this site they return an empty string and zero, zero.
| Type this | Expected answer here |
|---|---|
document.cookie | ”” (empty) |
localStorage.length | 0 |
sessionStorage.length | 0 |
Read the script
There is exactly one script on this site and you can read it in full: /js/cta.js. It copies advertising campaign parameters from the page address onto the partner links and re-applies their rel attributes. It contains no cookie, no localStorage, no sessionStorage, no indexedDB, no fetch and no XMLHttpRequest. Use your browser’s find function on the file if you want to confirm that.
4. What still reaches our server
Not storing anything on your device is not the same as knowing nothing. Any request to any website necessarily discloses your IP address to that server, and ours keeps an ordinary access log for fourteen days for security purposes. That is described in full in the privacy policy. If you want to hide your IP address from us, a VPN or Tor is the tool for that, not a cookie setting.
5. When you follow a partner link
This policy covers miravest.online only. A link labelled “partner link” takes you to a different company’s website, which will almost certainly set its own cookies for attribution and advertising. That is their decision on their site, governed by their own cookie notice, and any consent banner you see there is theirs. Nothing on this site obliges you to click one.
6. Managing cookies generally
Although there is nothing here to manage, every browser lets you block or delete cookies and site data for all sites, usually under Settings → Privacy. Doing so will not change anything about your experience of this site, which is a reasonable test of whether we are telling the truth.
7. Changes
If this site ever begins to store anything on your device, this page will be updated before that happens, the zero-storage claim will be withdrawn in plain words, and a lawful consent mechanism will be in place first.
Effective from . This is the current version; we do not keep earlier versions online.