Measure the funnel, not the person

Search text stays in your browser

Autocomplete and directory filtering operate on creator names shipped with the page. The funnel endpoint accepts a result count and success state, but its validation schema has no field for the query text.

Accepted product events are deliberately narrow

The endpoint allowlist covers search success, result opens, compare starts, comparison opens, methodology/source/correction actions, embed copies, and data downloads. Properties are restricted to coarse surface, creator slug, canonical comparison slug, category, source type, asset, result count, position, or success.

Unsupported fields and oversized payloads are rejected. The application does not add IP addresses, user-agent strings, referrers, or cross-event identifiers to analytics records.

Browser privacy signals are honored

Client-side event delivery is skipped when Do Not Track is set to 1 or Global Privacy Control is enabled. Requests omit credentials, disable caching, and use a no-referrer policy.

Hosting and optional storage

Pages and the validation endpoint run on the hosting provider, which may process connection data needed to deliver and secure requests under its own infrastructure policies. Validated funnel events are stored only when the deployment owner configures the optional analytics binding; otherwise they are accepted and discarded.

Embeds and external sources

Creator cards use local monograms rather than third-party avatar aggregators. Embed cards do not include analytics scripts. External source and correction links open the destination site, which then applies its own privacy policy.