Last updated: 22 September 2026.

Why there is no consent banner

Article 5(3) of Directive 2002/58/EC (the ePrivacy Directive), as implemented in Czech law by Act No. 127/2005 Coll., requires informed consent before storing information on, or gaining access to information already stored on, a user's terminal equipment — except where it is strictly necessary to provide a service you have explicitly requested.

A consent banner exists to obtain that consent. We do not store or access anything on your device, so there is nothing to consent to, and a banner would be a pointless obstacle asking you to approve something that is not happening. Removing the collection is a better answer than asking permission for it.

The same reasoning applies to Article 6 GDPR: with no personal data collected through your terminal equipment, no legal basis for such collection is required.

What we do not use

• No analytics. No Google Analytics, no Matomo, no Plausible, no server-side analytics beyond the ordinary access log the web server must keep to operate.
• No advertising pixels. No Meta pixel, no Microsoft UET tag, no Google Ads conversion tag, no remarketing list.
• No tag manager of any kind.
• No social widgets, share buttons that call home, comment systems or embedded video.
• No web fonts. The site uses the fonts already on your device. Loading a font from a third-party server would send your IP address to that server.
• No CDN, no remote images. Every file the page needs — stylesheet, script, icon, every diagram — comes from veldator.online itself.
• No fingerprinting. No canvas, WebGL, audio-context or font-enumeration probes, and no script that reads your screen, timezone or hardware to build an identifier.

The one script on this site, and what it does

The site loads a single JavaScript file, /js/cta.js. You can read the whole of it — it is short and not minified. It does exactly two things:

1. If you arrived with campaign parameters in the address bar (for example utm_source or msclkid), it copies those parameters onto the outbound partner link so the vendor can attribute the referral. Those values were already in your address bar; nothing is read from your device and nothing is written to it.
2. It re-applies the rel="sponsored nofollow noopener" attributes and the referrer policy to partner links, so the disclosure markup cannot be lost.

It sets no cookie, writes to no storage API, and sends no network request.

How to verify all of this yourself

Do not take our word for it. This takes about thirty seconds in any desktop browser.

Check for cookies and storage

1. Press F12 (or Ctrl+Shift+I; on a Mac, Cmd+Option+I) to open the developer tools.
2. Open the Application tab in Chrome or Edge, or Storage in Firefox or Safari.
3. In the left-hand panel, look at Cookies, Local storage, Session storage and IndexedDB for veldator.online.
4. Every one of them should be empty. Reload the page and look again.

Check that nothing is sent to a third party

1. Open the Network tab and reload the page with the tab open.
2. Sort or scan the Domain column. Every request should be to veldator.online.
3. Check the response headers of the first request: there should be no Set-Cookie header.

Check from the console

Open the Console tab and type document.cookie then press Enter. It should return an empty string (""). Then try localStorage.length and sessionStorage.length; both should return 0.

What your browser does on its own

Your browser will cache the stylesheet, the script and the diagrams so that the site loads faster the second time. That is ordinary HTTP caching performed by your browser for your benefit; it is not an identifier, we cannot read it, and it is cleared when you clear your browsing data.

Sites you leave for

If you follow a partner link you go to a third-party vendor's website. That site will almost certainly use cookies and will ask you about them under its own policy. We have no control over it and this policy does not apply there. See section 5 of the privacy policy.