Cookieless Analytics & Privacy Architecture

Core Privacy & Compliance Standards

Hikr is engineered from the ground up to operate completely without invasive client-side cookies or continuous surveillance trackers. By aligning with ePrivacy Art 5(3) requirements, our architecture ensures that no non-essential information is stored on or retrieved from user terminal equipment without prior informed consent. Furthermore, Hikr leverages Safari WebKit 7-day immunity characteristics by relying entirely on first-party server-side request routing and transient session handling that bypasses aggressive Intelligent Tracking Prevention (ITP) restrictions.

For deeper technical research and foundational engineering papers regarding cookieless measurement, consult our primary provenance documentation hosted at bouletteproof.com.

Operating Modes: Mode B, Mode D, Mode E, and Mode C Boundaries

Mode B (Daily Rotating Hash): To prevent long-term visitor tracking while enabling single-session attribution, Mode B computes a transient cryptographic hash using the exact formula hash(daily_salt + websiteId + ip + ua). Crucially, raw IP addresses and User-Agent strings are never stored in our databases. The salt rotates automatically every 24 hours, ensuring complete cryptographic amnesia.

Mode D (hkclid Redirect Token): Mode D utilizes server-to-server 302 redirects to inject the immutable hkclid token. This links ad clicks to subsequent server actions without relying on cross-site tracking pixels or third-party cookies.

Mode E (Consent at Form Bind): Mode E ensures that identity binding and event forwarding occur exclusively at the moment of form submission where explicit user intent is established.

Mode C (WebKit Purge Boundary & Agency Upgrades): When operating in Mode C, deployments require a visible consent banner. State storage is strictly bounded by an immutable 30-day WebKit purge ceiling. Additionally, any ad-platform forwarding (such as Meta CAPI) mandates explicit, auditable user consent prior to dispatch.

Explicit Architectural Boundaries & Refusals

• No Long-Run Profiles: Hikr explicitly refuses to build or maintain historical cross-session user profiles.
• Strict 30-Day Purge Floor: All optional extended storage tiers enforce automated 30-day maximum retention limits in accordance with WebKit constraints.
• Mandatory Consent for Ad Platforms: Forwarding conversion payloads to third-party ad networks (e.g., Meta CAPI) requires verified visitor consent.