Most sites open with a banner because most sites load things that need one. This one does not, so the rest of this page is mainly an explanation of what we use instead, and what would have to change for that banner to appear.
What a cookie actually is
A cookie is a small file a site asks your browser to keep and hand back on every later request. Useful ones remember that you are logged in. The ones regulators care about are the third-party kind, which follow you between sites to build an advertising profile. Under Albanian law no. 124/2024 and the EU's ePrivacy rules, anything beyond what is strictly necessary needs your consent before it is set.
This site has no logins, no shopping cart, and no advertising, so there is nothing here that needs remembering between requests.
What we use instead
We do want to know which pages people read, so we know what to write next. That runs on Vercel Web Analytics, which was chosen precisely because it does the job without identifying anyone.
- It sets no cookies and stores nothing in your browser.
- It assigns no persistent identifier, so it cannot recognise you tomorrow or on another device.
- It cannot follow you off this site. There is no cross-site network behind it.
- It reports aggregate numbers only — page views, referrers, countries. Nothing at the level of a person.
Because the measurement is anonymous and nothing is stored on your device, it does not require consent. That is the whole reason there is no banner: we did not find a legal loophole, we picked a tool that does not need one.
Server logs
Separately from analytics, our host keeps ordinary request logs — IP address, page requested, browser user-agent, timestamp. Every web server on the internet does this, it is not a cookie, and it is not something a banner would cover. It is described in more detail in the privacy policy.
No embedded third parties
There are no embedded videos, no map widgets, no chat bubbles, no social feeds, and no web fonts loaded from someone else's server. Fonts are self-hosted at build time. Every one of those is a common way for a third party's cookie to end up on a site whose owner never intended it, and the simplest defence is not to have any.
What would change this
If we ever add something that sets a cookie or stores an identifier — a chat widget, an embedded player, a conversion pixel — this page gets updated and a consent banner ships with it, before the thing is switched on. We are not going to quietly start tracking and leave a stale page saying we do not.
If you want to check, or block it anyway
Do not take our word for it. Open your browser's developer tools, go to the storage or application tab, and look at the cookie list for this domain. It is empty.
If you would still rather block scripts, every major browser lets you, and any content blocker will stop the analytics request. Nothing on this site breaks without it — the pages are static HTML and read perfectly with JavaScript switched off entirely.
Contact
Questions about this page go to contact@byoas.com. The related pages are the privacy policy and the terms.
This page is written to be clear and accurate, not to serve as legal advice. If your situation turns on a clause here, take advice on it.