Cookie policy

Effective 22 September 2026 · version 2.0

Why there is no consent banner

Article 5(3) of the ePrivacy Directive (2002/58/EC, as amended) requires consent before storing information on, or gaining access to information already stored on, a user’s terminal equipment — subject to 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. We do neither. There is therefore nothing to consent to, and a banner asking you to accept cookies that do not exist would be misleading rather than compliant. We chose to remove the tracking instead of asking you to tolerate it.

This is a deliberate design decision with a cost: we have no idea how many people read this page, which sections they read, or which links they follow. We consider that an acceptable price.

How to verify this yourself

Do not take our word for it. Every modern browser will show you, in under a minute:

1. Open this page, then press F12 (or ⌘⌥I on a Mac) to open developer tools.
2. Cookies. In Chrome or Edge go to the Application tab, then Storage → Cookies. In Firefox go to the Storage tab, then Cookies. Select this site. The list will be empty.
3. Browser storage. In the same panel check Local Storage, Session Storage, IndexedDB, Cache Storage and Service Workers. All empty, none registered.
4. Third-party requests. Open the Network tab and reload the page with Ctrl+Shift+R. Look at the Domain column — you may need to enable it by right-clicking the column headers. Every single request will be to pravator.online. There are no requests to font providers, content delivery networks, analytics endpoints or advertising servers.
5. Response headers. Click the document request in the Network tab and read the response headers. There is no Set-Cookie header.
6. The code itself. The site loads exactly one script, /js/cta.js. It is about sixty lines, it is not minified, and you can read all of it. Search it for cookie, localStorage, fetch or XMLHttpRequest — there are no matches.

What that one script does

It does two things, both at the moment the page loads and neither involving storage:

• It re-applies rel="sponsored nofollow noopener" to every partner link, so the disclosure of the commercial relationship cannot be lost to a markup mistake.
• If the URL you arrived on carries an advertising click identifier such as msclkid, gclid or a utm_ parameter, it copies that parameter onto the outgoing partner link so the advertiser can attribute the visit. This is a URL parameter passed through at click time, visible to you in the address bar. It is not a cookie, it is not stored, and nothing happens unless you click.

What happens after you leave

Once you follow a partner link you are on the advertiser’s website, and their cookie practice applies. Most advertisers do set cookies, and most will show you their own consent interface. We cannot control that and we do not pretend to. What we can control is this site, and on this site the answer is none.

Server logs are not cookies

For completeness: the web server records each request in a log file, as every web server does. That is not storage on your device and is outside the scope of Article 5(3); it is ordinary processing of personal data, covered in section 3 of the privacy policy, retained for 14 days and used only for operating and securing the site.

If this ever changes

If we ever add anything that stores or reads information on your device, we will publish a compliant consent mechanism before it goes live, update this page, and change the effective date above. Until that happens, the statement at the top of this page is the whole truth.