Updated 18 Nov 2026 · Version 2026-11-18-ts1
Cookies
1. What this version uses
This version uses no analytics, behavioral advertising or pixels. Images, fonts, styles and portal code are local. On the contact page the external Cloudflare Turnstile component verifies access to prevent abuse. This integration does not request cookie pre-clearance. The provider may use technical mechanisms necessary for verification. Analytics or marketing consent is not required to browse or submit an inquiry.
2. Preference record
Saving a choice stores angariar_privacy_v1 in browser localStorage, containing version, choice and date, without name, email or business content. Validity is up to 180 days and is checked when the portal opens. Reopen settings from the footer or clear site data in your browser. This local record is not an inquiry database or consent to future services.
3. Categories and infrastructure
Analytics and Marketing are marked not used and cannot be enabled in this version. WordPress authentication cookies may exist for administrators using restricted areas; public intake needs no login. Infrastructure may use necessary technical mechanisms. Server logs are not cookies. Basic abuse prevention stores an IP-derived server key for about 15 minutes without adding the raw IP to the commercial record.
4. Changes and choices
Before optional services are introduced, their providers, purposes and periods must be identified and appropriate choices implemented. A current preference does not authorize future tracking. The manager reports storage failure without enabling trackers. We do not claim an audit of every cookie in the wider WordPress installation without checking the deployed environment.
5. Anti-bot verification
We use Cloudflare Turnstile to protect this form against abuse. Your browser loads the Cloudflare component, which processes technical connection and browser data to verify access. Our server sends the verification token to Cloudflare without your name, email, company or message. A random request identifier binds verification to submission. We do not store the token in the commercial record or send it to HubSpot. The service may involve international processing; see Cloudflare privacy information. Its purpose is security, not audience analytics or advertising.

