Cookie Policy

Load a page here for the first time and nothing measures you. Google Analytics and Microsoft Clarity are not in the page at all until you accept them on the banner, and if you reject, they are never loaded. 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.

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.

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.

One category, analytics, two tools. Reject, and nothing in this table is ever created.

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.

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.

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.

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.

• 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 consent record 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.

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 info@company-registration-austria.com or use the contact form.