Cookie Policy

01Cookies and similar technologies

Cookies are small files stored by your browser. Technologies such as local storage can retain information without using a traditional HTTP cookie. They may support technical functions, security, preferences or, where enabled, measurement and other purposes.

02Reported technology inventory

The following entries record the technologies described in the published policy dated 13 September 2026; this is not a new live cookie scan. Actual use and retention depend on the active configuration. The current consent panel should identify enabled optional services and purposes.

CookieConsent: stores the consent preference for the domain. Reported duration: approximately one year; artefaktum.net.

elementor: technical storage associated with WordPress / Elementor. Reported duration: persistent; artefaktum.net.

Google Tag Manager: manages tags configured in container GTM-WZVRDSK. Other services depend on the active tags. Provider: Google. This is not itself a cookie name.

rc::a: Google reCAPTCHA bot protection. Reported duration: persistent; Google / gstatic.

rc::c: session-related Google reCAPTCHA bot protection. Reported duration: session; Google / gstatic.

__cf_bm: Cloudflare anti-bot technology that may appear when a protected external resource is requested. Reported duration: temporary on the relevant external domain; the existing policy does not specify a precise duration.

This inventory does not prove that all listed technologies are active in every visit. A first-party page cannot inspect all third-party or HttpOnly cookies.

Current header component: the approved header additionally uses the session-storage key afLogoShown to remember that its logo animation has already played in the browser session. It contains a display-state flag, not assessment answers. This documented interface preference must also be reflected in the site's storage inventory and consent assessment.

03Google Tag Manager

Artefaktum integrates Google Tag Manager with container identifier GTM-WZVRDSK. Tag Manager manages scripts and tags. Its presence alone does not establish that all Google technologies or behavioural advertising are used.

Non-essential tags must be subject to the appropriate consent mechanism before activation. If analytics, marketing or other non-essential categories are added, this policy and the preference panel must be updated accordingly.

04Google reCAPTCHA

Some forms may use Google reCAPTCHA to reduce automated submissions, spam and abuse. This may involve technical information such as IP address, browser, device and interactions needed to distinguish human traffic from automated requests.

The rc::a and rc::c technologies may be stored through Google / gstatic resources. Their use must be limited to the relevant form-protection functions and handled under applicable law.

05External services and Supabase

Certain technical functions may request external services. Cloudflare may set __cf_bm when the browser requests an external resource protected by Cloudflare. Its appearance does not mean that Cloudflare provides the entire Artefaktum website.

Functions using supabase.co infrastructure may generate requests to that domain. Only integrations actually necessary for the relevant function should be maintained.

06Consent and preferences

Strictly necessary technologies may be used without consent where they are indispensable to provide a requested service or an essential technical function. Non-essential technologies require prior consent where the law requires it.

You must be able to accept, reject or configure non-essential categories clearly. Withdrawing or changing consent must be as easy as giving it.

The settings button on this page opens the consent manager already installed on the website. It does not accept optional cookies or alter your choices by itself.

07Analytics, advertising and profiling

The published policy does not establish verified behavioural-advertising or commercial-profiling purposes. This policy therefore does not attribute unverified advertising or profiling activities to the site.

Any analytics, advertising, non-essential measurement or profiling tag added to Tag Manager must be classified appropriately and blocked until consent is obtained where required.

08International transfers

Some global services, particularly Google technologies, may involve processing or access outside the European Economic Area, depending on the service and configuration. Any transfer must rely on a valid GDPR mechanism, such as an adequacy decision or appropriate safeguards.

Email processing by dotplex is addressed in the Privacy Policy; email provision does not itself establish a cookie-related transfer outside the EEA.

09Managing and deleting storage

Use the website's consent mechanism to manage your choices. Your browser also allows you to delete cookies and local storage or block particular technologies. Removing strictly necessary storage may affect some functions.

Deleting browser storage is not the same as recording a new preference in the consent manager. Use the settings panel to change or withdraw optional consent.

10Updates

This policy must be updated when technologies, providers or technical configuration change. New non-essential categories must be included in the consent mechanism before activation where required by law.

Storage visible in this browser

This optional local check displays storage names accessible to this page, not values. It cannot inspect HttpOnly cookies or other domains, and does not determine legal necessity or consent.