Last updated: 9 September 2026 · operator details pending
01
Cookies and similar technologies
A cookie is a small file a website can save or read in a browser. Local storage, pixels, SDKs, identifiers, and other mechanisms may similarly access information on a device. This policy sometimes uses “cookies” as a readable umbrella term.
Strictly necessary storage may be used without consent only within the legal exemption. Optional analytics or marketing remains off until consent is valid, freely given, specific, informed, and as easy to withdraw as it is to give.
02
Verified application inventory
age-one-analytics-consent- A first-party
localStoragerecord managed by AGE ONE. It contains only thegrantedordeniedchoice, its ISO save time, and the format version. It persists on that device until site data is cleared or the version is invalidated. - Project form
- The application does not set a form cookie. Its random deduplication identifier and form start time remain in page memory and are sent with the enquiry. Abuse limiting occurs on the server.
- Google Tag Manager
- This build has no GTM ID configured, so its loader and tags do not run regardless of the preference stored in the browser.
03
What this inventory can and cannot establish
The inventory describes the application code and the build configuration available here. A network, security, or hosting provider may add technology through account settings, and a GTM container can change independently of this repository.
Before final legal publication, the production domain must be audited in a clean browser before and after every choice, together with Cloudflare, Hetzner, and container settings. Every observed technology must be listed with name, provider, purpose, category, duration, recipients, and transfers. A generic list would be inaccurate.
04
Categories and activation rules
Strictly necessary
Supports delivery, security, and the privacy choice requested by the user. It is not used for advertising. Refusing optional storage does not block content or the form.
Optional analytics
May measure website use only after “Accept analytics”. The application restricts events to controlled names and parameters and rejects names, email addresses, telephone numbers, company names, and the project description.
Marketing, preferences, and external media
No such category is declared active in the audited application. It will not be introduced without assessment, updated policies, and the consent or objection mechanism required by law.
05
Consent, refusal, and withdrawal
When analytics is configured, the panel separately offers necessary-only use and analytics acceptance. Nothing optional is selected by default. The permanent “Cookie settings” control reopens the panel; the choice applies to the same browser and device.
Changing from accepted to denied stores the new choice and reloads the page so the GTM loader no longer starts. Clearing this site’s browser data also removes the local preference. If the browser blocks storage, the interface reports the error and analytics remains disabled.
The application cannot generically delete cookies created by unknown container tags. A real container must therefore remain disabled until every tag is inventoried, withdrawal is tested, and deletion of controllable provider cookies is implemented.
06
Do Not Track and Global Privacy Control
The website does not interpret these as separate choices. Analytics is off until explicit consent, so an unrecognised signal never activates optional technology. If data sale/sharing or behavioural advertising subject to US law is introduced, Global Privacy Control must be implemented before that use begins.
07
Updates, sources, and contact
This policy and inventory will be updated before a new provider is activated and whenever technical configuration changes. Questions may be sent to [email protected].
Official sources used for the consent rules: