Austria
Cookie Policy
Everything this site stores on your device or reads back from it, named item by item, with what it is for, who sets it and how long it lasts. Nothing that is not strictly necessary is stored until you say yes.
Last updated: 17 September 2026.
The short version
Load a page here for the first time and nothing is stored on your device and nothing is read from it, which is the thing the law is about. Google Analytics does load, and it is worth being exact about what that means: it runs with storage switched off, so it sets no cookie, carries no identifier that could follow you, and records a page view and nothing more. Accept on the banner and it starts measuring properly, with the cookie described in the table below. Reject, or ignore the banner, and it stays in the state it started in. Microsoft Clarity is different and is treated differently: it has no such mode, it writes its identifier the moment it loads, so it is not in the page at all until you accept it, and if you reject it is never fetched. What is stored without asking is the record of your answer, and whatever Cloudflare's security layer needs to tell a person from a bot. There is no advertising on this site, so there is no advertising cookie, no retargeting pixel and no conversion tag for any ad network.
"Cookie" in this page also covers localStorage and anything else kept on your device, because the law that matters here is about storage and access generally, not about the word cookie.
How consent works here
First paint, nothing granted.
The page loads with Google Consent Mode v2 set to denied, before anything else runs. Google Analytics is fetched in that state: with analytics_storage denied it may send a page view, and it may not write to your device or read from it. Microsoft Clarity is not fetched. /js/consent.js and /js/analytics.js load, and neither stores anything on its own.
The banner asks.
It offers three things: accept, reject, and a settings view that explains the one category there is. It is reachable by keyboard and it does not cover the page content.
Your answer is written down, on your device.
/js/consent.js stores it in localStorage under the key consent, as {analytics: true or false, ts}, where ts is when you answered. It is not a cookie, it is not sent to any server, and it is what stops the banner asking again on the next page.
What your answer changes.
If you accepted, the consent signal is updated to granted, Google Analytics begins storing the cookie in the table below, and Microsoft Clarity is fetched for the first time. If you rejected, or closed the banner without answering, Clarity is never fetched and Google Analytics stays exactly as it was on first paint: no cookie, no identifier, no storage.
You can change your mind.
A settings link in the footer of every page reopens the banner. Switching analytics off puts Google Analytics back to storage denied at once, so the cookie stops being used from that moment; Microsoft Clarity was loaded on the page you are on and cannot be unloaded from it, so it stops from the next page. Neither reaches back to delete what was already collected, though you can ask us to, under the rights section of the privacy policy.
Your answer is stored per browser and per device. A different browser, a private window, or clearing site data means you will be asked again.
Stored without asking you
These are strictly necessary: they exist to deliver the site, to remember your own answer about the rest, or to keep the forms from being flooded. Austrian law requires consent for storage on your device unless the storage is needed to transmit the message or is strictly necessary to provide the service you asked for (§ 165 Abs. 3 TKG 2021, BGBl. I Nr. 190/2021, in force since 1 November 2021), which is the exception each row below relies on.
| Name | Type | Set by | What it does | Lifetime |
|---|---|---|---|---|
consent | localStorage, first party | This site, /js/consent.js | Records whether you accepted or rejected analytics, and when | Until you clear your browser storage |
__cf_bm | Cookie, first party | Cloudflare | Tells automated traffic from human traffic. Set where Cloudflare's bot management is active on this zone | 30 minutes |
_cfuvid | Cookie, first party | Cloudflare | Used by Cloudflare's rate limiting to tell requests apart. Set where that feature is active | Session, deleted when the browser closes |
Two things people expect to find in this table and which are not there. Cloudflare Turnstile, the captcha on the forms, sets no cookie in the configuration this site uses; the pre clearance mode that would issue a cf_clearance cookie is not switched on. The form rate limit counts submissions per IP address, and that counter lives in a store on Cloudflare's side, not on your device, for 10 minutes. It is described in the privacy policy because it is processing, but there is nothing here for it to be.
The three items that can be stored before you answer the banner. None of them measures a visit, identifies you across sites, or is used for advertising.
Loaded only after you accept
One category, analytics, two tools. Reject, and nothing in this table is ever created.
| Name | Type | Set by | What it does | Lifetime |
|---|---|---|---|---|
_ga | Cookie, first party | Google Analytics 4 | Holds the randomly generated identifier that keeps one visit together | 2 years |
_ga_<container-id> | Cookie, first party | Google Analytics 4 | Holds the session state for this property | 2 years |
_clck | Cookie, first party | Microsoft Clarity | Holds the Clarity identifier and links the session to a recording | 1 year |
_clsk | Cookie, first party | Microsoft Clarity | Holds the current session so its page views stay together | 1 day |
Microsoft identifiers on clarity.ms | Cookies, third party | Microsoft | Microsoft may set its own identifiers on its own domains when the Clarity script loads. They are Microsoft's, set under Microsoft's terms, and they exist only after you accept | Set by Microsoft |
Clarity records a replay of the session: pages, clicks, scrolling, where a page was abandoned. It is configured to mask text input, so what you type into a form field is not recorded. The purpose is finding the field nobody can fill in, not watching who was filling it.
Everything the analytics category creates, on this domain and on Microsoft's. Google Analytics event data is kept for 14 months at property level; Microsoft sets the retention for Clarity data.
Measured without a cookie
Ahrefs Web Analytics runs on this site and is genuinely cookieless. It writes no cookie, stores nothing in localStorage, reads nothing back from your device and sets no identifier that could follow you to another site. Because there is no storage and no access to storage, § 165 Abs. 3 TKG 2021 has nothing to attach to and it loads whatever you answered on the banner.
That is not the same as saying it processes nothing. It receives the request data for the page view, which is processing under the GDPR and rests on legitimate interest, and you can object to it. The privacy policy says how.
What this site does not use
Stated plainly, because a cookie policy that only lists what exists leaves the reader guessing about the rest.
- No advertising or retargeting. No Google Ads remarketing tag, no Meta pixel, no LinkedIn insight tag, no conversion tracking for any ad network, and no cookie of that kind at all.
- No third party fonts, maps, videos or icon sets. Everything the page needs is served from this domain, so no request goes to another company merely by opening a page here.
- No social media embeds and no share buttons that load code from a social network.
- No chat widget, no session recording beyond Clarity, no A/B testing tool, no heatmap tool beyond Clarity.
- No cross site tracking, no data broker, no audience list. Nothing from this site is sold or shared for advertising.
- No cookie wall. Rejecting analytics changes nothing about what you can read or send. The forms, the payment page and every guide work identically either way.
Stripe and NOWPayments pages
Paying an invoice moves you off this site. Card payment opens Stripe Checkout on Stripe's own domain, and cryptocurrency payment opens a NOWPayments page on theirs. Whatever those pages store is theirs, under their own policies, and this page cannot speak for it.
What is worth saying is what happens on our side: Stripe's own script is not loaded on this domain. This site does not run a card field of its own, so the __stripe_mid and __stripe_sid cookies that Stripe sets where its script is embedded do not appear here. /pay/ collects an invoice number, a name, an email address, an amount and a currency, and hands you over.
Changing or withdrawing your choice
- From the footer. The settings link on every page reopens the banner. Switch analytics off and nothing further is collected.
- By clearing site data. Your browser's site data control deletes the
consentrecord and every cookie in the tables above, on that browser. The banner then asks again. - From your browser. Every browser can block or delete cookies for a site, or for all sites. Blocking the strictly necessary items may break the forms, which is the only thing on this site that depends on them.
- Withdrawal is not retroactive. Collection stops; what was already collected is dealt with under the rights section of the privacy policy, including erasure.
Keeping this page true
A cookie policy is only worth anything if it matches the site on the day you read it. This one is checked against the deployed site before release and whenever a script, a tool or a hosting setting changes, and the date at the top is rewritten each time. If a tool is added, it appears in the right table here before it is switched on, not after.
If you find something in your browser that is set by this site and is not in a table above, that is a defect and we want to know: write to [email protected] or use the contact form.