Cookie policy

Last updated 21 September 2026

1. What we would have to tell you, if there were anything to tell

Under Article 5(3) of Directive 2002/58/EC (the ePrivacy Directive), as implemented in Czech law by § 89(3) of Act No. 127/2005 Coll. on electronic communications, storing information on a user’s device or gaining access to information already stored there requires that user’s prior informed consent, unless it is strictly necessary to provide a service the user has explicitly requested.

That obligation does not arise here, because we neither store nor access anything on your device. There is no category of cookie to list, no purpose to describe, no retention period to state and no third-party recipient to name, because none of those things exist.

2. Why there is no consent banner

A consent banner is a mechanism for obtaining permission to do something. We are not doing anything that needs permission, so asking for it would be theatre — and worse than theatre, because consent banners are themselves an interruption and are frequently used to obscure rather than to inform.

We took the other route available under the law: instead of asking you to accept tracking, we removed the tracking. The site was rebuilt to that standard deliberately. Concretely, that meant deleting the analytics, deleting the consent-management script itself (which used localStorage to remember your choice, and so was ironically the main thing storing data on your device), removing the Google Fonts stylesheet and self-hosting a system font stack instead, and removing every remote image.

The result is that on this site there is nothing to consent to, and so nothing to ask you about. We think that is the honest reading of what “privacy by design” in Article 25 GDPR actually requires.

3. What the site does load

Three files, all from brativa.online itself, plus the diagrams on the article page:

Typefaces are not downloaded at all. The site asks your operating system for a font it already has (the “system font stack”), which is why this page may look slightly different on a Mac, a Windows PC and an Android phone. That is intentional: requesting a font from Google Fonts would disclose your IP address to Google on every page load.

4. How to verify all of this yourself

This takes about a minute and needs nothing but the browser you are already using.

Check that no cookie is set

1. Press F12 to open developer tools (on a Mac, Cmd + Option + I).
2. Open the Application tab in Chrome or Edge, or Storage in Firefox or Safari.
3. In the left-hand panel, expand Cookies and select https://brativa.online.
4. The list is empty. Reload the page and browse to other pages on the site — it stays empty.

Check that nothing is written to browser storage

1. In the same panel, look at Local storage, Session storage, IndexedDB and Cache storage for this origin.
2. All four are empty.
3. If you prefer, open the Console tab and run localStorage.length and sessionStorage.length. Both return 0.

Check that no third party is contacted

1. Open the Network tab and reload the page with the tab open.
2. Look at the Domain column — you may need to enable it by right-clicking the column headers.
3. Every single row says brativa.online. There is no request to Google, to a CDN, to a font service or to anyone else.

Check the response headers

1. Still in the Network tab, click the first row (the document itself) and open Headers.
2. Under Response headers, there is no Set-Cookie line.

Or check without the developer tools at all

Install any tracker-blocking extension you trust and watch its counter while you browse this site. It will report nothing blocked, because there is nothing for it to block.

If you ever run these checks and find something we have not declared here, that is a defect and we want to know. Write to info@brativa.online and we will fix it and say so publicly, under our corrections procedure.

5. What the one script actually does

/js/cta.js is short, and you can read the whole of it by opening /js/cta.js directly. It does exactly two things, both of them in your browser and neither of them involving storage or a network request:

1. If you arrived at this site from an advertisement, it copies a short allow-list of campaign parameters that were already in your address bar (such as utm_source, gclid or msclkid) onto the outgoing partner link, so the vendor can attribute the visit to us. These values are read from the URL and written to a link; they are never stored and never sent to us.
2. It re-applies rel="sponsored nofollow noopener" and the strict-origin-when-cross-origin referrer policy to every partner link, so those attributes are correct even if something on the page has altered them.

It sets no cookie, reads no cookie, touches no storage API and makes no fetch or XMLHttpRequest call. If you disable JavaScript entirely, the site works normally; the partner links simply carry no campaign tag.

6. What happens after you leave

This policy covers brativa.online only. When you follow a link to a vendor’s site, you are on their site under their rules, and they will very probably set cookies and ask you about them. That is their decision and their disclosure to make, not ours. Read their cookie notice when you get there.

7. Server logs

The one record that does exist is the web server’s access log, which is not a cookie and is not stored on your device. It is described fully in the privacy policy, section 3: it holds your IP address, the time, the page requested and your user-agent string, it is used only for security and troubleshooting, and it is deleted automatically after 14 days.

8. Changes

If this ever changes — if we ever introduce something that stores data on your device — we will publish it here first, and we will implement whatever consent mechanism the law then requires before doing it. We have no plan to.

9. Contact

BRANAGROUP s.r.o., Za Poříčskou bránou 315/10, Karlín, 186 00 Praha 8, Czech Republic. Email info@brativa.online.