skabro.eu sets no cookies of its own, ever, on any page. Eight of its nine pages store nothing on your device at all and load nothing from anyone else’s servers. The contact page is the exception: it uses Google reCAPTCHA to keep automated abuse away from the enquiry form and from our telephone number, and doing so both lets Google set a cookie in its own domain and writes one reCAPTCHA entry into your browser’s local storage. This page explains exactly where that line falls.
1. The short version
Browsing this site sets no cookies - not analytics, not advertising, not necessary ones. On eight of the nine pages nothing whatsoever is written to your device, and the fonts, styles, scripts and images all come from skabro.eu itself.
One page differs. On /contact we load Google reCAPTCHA, so that neither the enquiry form nor our telephone number can be used by bots. That fetches code from Google, lets Google set a cookie of its own - in its domain, not ours - and, when you actually send the form or ask for the number, writes one reCAPTCHA entry into local storage. It happens only on that page, only because those two things are there, and it is described in full in section 4.
There is no cookie banner. reCAPTCHA is used strictly to protect a service you are asking us for, which is the one category that does not require prior consent - see section 6 for why that position is not entirely free of doubt.
2. What cookies are
Cookies are small text files a website stores on your device, usually to remember something between page loads. They can be strictly necessary for a service you asked for, or optional - analytics, personalisation, advertising. Under Slovak Act No. 452/2021 Coll. on electronic communications, which implements the EU ePrivacy Directive, optional cookies may only be stored with your prior consent.
The same rules apply to any other technology that stores or reads information on your device, including local storage, session storage and tracking pixels.
3. What is stored on your device
skabro.eu sets no cookies at all, on any page, including the contact form. Nothing here is ours, and nothing here is used to recognise or follow you. What the reCAPTCHA on /contact does store, in full, is this:
_GRECAPTCHA(cookie) - set by Google, not by us, and stored againstgoogle.comrather thanskabro.eu. reCAPTCHA loads inside a frame served by Google, and the cookie belongs to that frame. It helps reCAPTCHA tell a returning browser from a fresh one, which is part of how it scores a submission. Typically persists around six months. We can neither read it nor delete it._grecaptcha(local storage) - written by Google’s reCAPTCHA code, but stored underskabro.eu, because that is the page the code runs on. It appears when a check actually runs - that is, when you send the enquiry form or press Show phone number - and not merely from opening the page. It holds a reCAPTCHA token value, it is not an identifier we set, read or use, and it persists until you clear your browser storage. We do not put anything of our own beside it.
Nothing is written to session storage, on any page. Nor does anything of ours survive a page load: even the telephone number, once you have asked for it, is held in memory for that visit only and is gone when you close the tab.
Because it is a third-party cookie, many browsers block it outright - Safari and Firefox by default, Chrome depending on your settings. reCAPTCHA still works when they do.
Google may also read cookies it has already set in your browser from other sites. That is outside our control and is a consequence of using their service, which is why section 4 exists.
You can confirm all of this rather than taking our word for it. Open your browser’s developer tools, look under Application or Storage, and browse the site: under skabro.eu the cookie list stays empty on every page, and on eight of the nine pages local storage and session storage are empty too. Then open /contact and send the form or press Show phone number: a single _grecaptcha entry appears in local storage, and a google.com cookie entry alongside it. Both are the ones described above, and they are the only things you will find. The network panel shows requests to skabro.eu only, except on /contact, where google.com and gstatic.com also appear.
4. Google reCAPTCHA on the contact page
The contact form is a public endpoint, and a public endpoint attracts automated abuse. We defend it in several ways that involve nobody else - a hidden field bots fill in and humans cannot see, submission rate limits, and a daily ceiling. The same check also guards the button that shows our telephone number, which is kept off the page precisely so it cannot be harvested in bulk. reCAPTCHA v3 is the one layer in any of this that requires a third party. When you open the contact page and when you use either of those two things:
- Your browser loads
recaptcha/api.jsfromgoogle.comandgstatic.com, which in turn opens a hidden frame served by Google. Those two hosts are the only third-party requests this site makes anywhere. - reCAPTCHA collects information about your browser, device and interaction with the page, and sends it to Google, which returns a score for how likely the request is to be automated.
- At that point Google’s code writes its
_grecaptchaentry into local storage underskabro.eu, and sets its_GRECAPTCHAcookie ingoogle.com. Both are listed in section 3. Neither is ours, and we use neither. - Our server checks that score before accepting your message, or before sending you the phone number. For an enquiry it is stored alongside the message so we can tell a false rejection from a real one; for the phone number it is kept for 24 hours with a hashed form of your IP address, purely to limit how often the number can be requested, and then deleted. Our Privacy Policy sets both out in full.
- Google is the recipient of that data, acting for its own purposes as well as ours, and may process it outside the EEA. Google’s handling is governed by its own Privacy Policy and Terms of Service, not by ours.
We rely on our legitimate interest in preventing abuse of the form, and in keeping our telephone number out of bulk-harvested lists, as the legal basis - and we have limited the exposure as far as the service allows: it loads on one route out of nine, never on a page you are only reading, and it is not used for analytics, advertising or measurement of any kind.
If you would rather not involve Google, write to hello@skabro.eu instead. It reaches the same inbox as the form and no captcha is involved. We would rather you contacted us than submitted to a tracker you object to.
5. What we deliberately do not use
Some of this is a design decision rather than an obligation, so it is worth being specific. This site has no:
- Analytics. No Google Analytics, no Plausible, no Matomo, no self-hosted analytics of any kind. We do not count you.
- Advertising or remarketing. No ad networks, no conversion pixels, no retargeting tags.
- Social media embeds. No share widgets, no embedded feeds, no comment systems - all of which load third-party code and set third-party cookies.
- Externally hosted assets. Fonts are served from this domain rather than from a font CDN, which is a common and often overlooked way of disclosing visitor IP addresses to a third party.
- Fingerprinting of our own. We make no attempt to identify your device or browser. reCAPTCHA does profile your browser in order to score it, which is the trade-off described in section 4, and it is confined to the contact form.
Our hosting provider records standard server log data in order to serve and secure the site. That is not a cookie and it is not stored on your device; it is covered in our Privacy Policy.
6. If this ever changes
Should we add anything else that stores data on your device, this page will be updated with a new date before the change goes live, so what you read here is never behind what the site does.
Anything optional, analytics included, would run only after you had actively given consent, and a consent control would appear on the site at that point.
In fairness, the position in section 1 deserves a caveat. Treating an anti-abuse captcha as strictly necessary, and so exempt from prior consent, is the common reading and the one we rely on - but it is not settled, and some European data protection authorities take a narrower view of reCAPTCHA specifically because Google also benefits from the data. If that reading prevails we will either put the captcha behind a consent step or replace it with one that sets no cookies. We would rather write that down than leave you to discover the argument exists.
7. Managing cookies and storage in your browser
Every major browser lets you view, block and delete cookies and site storage from its privacy settings. Deleting the two entries in section 3 is safe: reCAPTCHA simply writes a fresh one the next time a check runs, and nothing on the site depends on either.
Blocking third-party cookies - the default in Safari and Firefox - changes nothing here: reCAPTCHA still works, as section 3 says. Blocking scripts or storage for skabro.eu itself, or blocking google.com outright, is different: the captcha then cannot produce a result, and the form and the phone reveal will refuse rather than let an unchecked request through. If you browse that way, email us at hello@skabro.eu - it reaches the same inbox and no captcha is involved.
Questions about this policy can be sent to hello@skabro.eu.