Cookie policy
This site does not use cookies, so there is no cookie banner.
Why there is nothing to consent to
Under the ePrivacy rules as implemented in Bulgaria — Article 4a of the Electronic Communications Act — consent is needed before storing information on, or reading information from, a visitor’s device, unless it is strictly necessary for something the visitor asked for.
Consent is required because something is being stored or read in the first place. This site stores nothing on your device: no session cookie, no tracking cookie, no local storage, no third-party pixel. With no storage to consent to, a banner would be theatre rather than compliance.
How spam is filtered without cookies
Three checks, all of which live inside the single page you are looking at. Nothing is written to your browser and nothing is read back from an earlier visit.
- A hidden field
- An input hidden from people and from assistive technology. Automated submissions that fill in every field trip it; you never see it.
- A minimum time on the form
- A submission arriving implausibly soon after the page loaded is treated as automated.
- A signed timestamp
- When the form loads, the server stamps the time and signs it with a key only the server knows. That value travels with the form in one request and is checked on submission, which proves the form was served by us and establishes when. It is not a cookie: it is not stored on your device, and it is never sent back on a later visit.
No analytics, no third-party scripts
There is no Google Analytics, no advertising pixel, no embedded map, video player or chat widget. Fonts are served from this domain rather than a third party, so no request leaves the site at all.
What would change this
If analytics, a booking calendar, a retargeting pixel, live chat or any third-party script that sets a cookie is ever added, this page stops being accurate the moment that code ships — and a proper consent banner, with refusal as easy as acceptance and nothing non-essential loading before a choice is made, becomes a requirement before that feature goes live rather than after.
The claim on this page is not only a promise. The build fails if cookie or session calls appear anywhere in the site’s server code, so adding one without updating this page stops the deploy.