No cookies
Aggregate mode works without browser cookies.
The runtime reports route behavior without setting tracking cookies or requiring cross-site identifiers.
No Set-CookieHTTPS POSTPublic project key
Privacy
Default observation does not need identity.
TrueClara is built for aggregate route behavior first. Default consent uses no browser cookies, no cross-site identity, and no PII requirement to detect route and edge changes.
01
No cookies
The runtime reports route behavior without setting tracking cookies or requiring cross-site identifiers.
02
Rotating hashes
A daily rotating salt limits reconstruction while still allowing aggregate route evidence to be counted.
03
Retention
Path and referrer fields have short retention. Aggregate counters retain by tier rather than indefinitely.
Rotating hashes
Session hashes are short-lived and server-side.
A daily rotating salt limits reconstruction while still allowing aggregate route evidence to be counted.
Daily saltServer-sideNo raw IP
Retention
Raw fields expire quickly; aggregates follow plan limits.
Path and referrer fields have short retention. Aggregate counters retain by tier rather than indefinitely.
7-day raw pathPlan retentionDSAR support
Consent upgrade
Richer evidence appears only after analytics opt-in.
Session evidence behind observations and value-route evidence are available when the customer enables the consented mode.
Opt-inEvidenceSession evidence
Before / after
Dashboard archaeology becomes one attributed answer.
Keep deploy context, route movement, and evidence together long enough for the team to decide.
Default
TrueClara starts from aggregate route evidence.
Behavioral tools often need identity first.
Storage
Raw fields expire and aggregates follow tier retention.
Raw logs become permanent audit risk.
Review
Product, legal, and docs describe the same model.
Privacy posture is explained separately.
Privacy is part of the architecture.
Use the default aggregate mode for route behavior, then opt into richer evidence only when the workflow needs it.