Skip to main content
Privacy & Compliance

Attribution quality without compromising compliance

Use first-party, opt-out, aggregate-only, access, and retention controls without sacrificing attribution quality.

How Kleerr handles data

First-party architecture. Data stays on your domain.

Kleerr's first-party pixel runs on your domain, keeping tracking data in your first-party infrastructure instead of a third-party pixel.

First-party pixel on your domain

Your pixel, your domain, your cookies. No third-party scripts that can be blocked or stripped.

First-party event capture

Conversion events captured via first-party infrastructure. No third-party dependencies.

First-party cookies only

No third-party cookies. No cross-site tracking. Fully compliant with browser privacy restrictions.

Tracking Modes

Choose the right privacy posture for your business

Opt-out (default)

Visitors can opt out of tracking. Standard for US and California compliance. Enabled by default on every plan.

Opt-in PII

When a user authenticates or consents, Kleerr enriches their profile with identifiable data. Full journey visibility for known users.

Aggregate-only

All journey stitching on hashed values. No individual PII stored or accessible. Maximum compliance posture for teams that need it.

Aggregate-Only Mode

Maximum compliance. Same signal quality.

For teams that need the strictest compliance posture, Kleerr can operate in aggregate mode. All journey stitching runs on hashed values. No individual PII stored or exposed.

Hashed identity stitching

Journey connections built on hashed values. Individual PII never stored or accessible in the platform.

No individual PII exposure

Aggregate mode ensures no team member can access or export individual-level personally identifiable information.

Same attribution quality

Data recovery and multi-touch attribution work identically in aggregate mode. Compliance doesn't mean losing data quality.

What we collect

Transparent about every data point

What we collect

  • Page views, clicks, and conversion events on your site
  • UTM parameters and click IDs from ad platforms
  • Order data from Shopify (revenue, products, customer email)
  • CRM deal data (pipeline stage, revenue, contact attribution)
  • First-party cookies for session and identity stitching

What we never collect

  • Personal browsing history outside your site
  • Data from sites you don't own
  • Third-party identity data or cross-site profiles
  • Personally identifiable information from anonymous visitors
  • Third-party cookie data or cross-site tracking
Compliance Controls

The controls your legal team needs

CCPA & CPRA (California)

Opt-out tracking by default. Supports opt-in PII mode for consented users, or aggregate-only mode for maximum compliance. Built for California privacy law — North America-first.

Role-based PII access

Control exactly which team members can view or export individual-level data. Granular permissions so compliance teams can limit PII exposure by role.

Data retention controls

Set your own data retention window. Your data, your rules. Delete on your schedule.

No deanonymization

Kleerr attributes known users. We don't identify anonymous visitors.

When a visitor provides their information (filling a form, logging in, completing a purchase), Kleerr connects that identity to their previous sessions. We never use probabilistic matching or third-party data to unmask anonymous visitors.

Known user attribution

When users identify themselves (purchase, form fill, login), we connect their journey.

Anonymous visitors stay anonymous

No probabilistic matching. No buying third-party identity data. Anonymous stays anonymous.

Kleerr vs. third-party pixels

What data leaves your domain

Cookie type

Third-Party Pixels

Third-party

Kleerr

First-party only

Data collection

Third-Party Pixels

Client-side (blockable)

Kleerr

First-party

Cross-site tracking

Third-Party Pixels

Yes

Kleerr

No

Blocked by ad blockers

Third-Party Pixels

Yes

Kleerr

No

Affected by iOS/Safari restrictions

Third-Party Pixels

Yes

Kleerr

No

Third-party identity data

Third-Party Pixels

Often

Kleerr

Never

Data leaves your domain

Third-Party Pixels

Yes

Kleerr

Only conversion events to ad platforms

Privacy FAQs

Straight answers for privacy and compliance teams

Does Kleerr use third-party cookies or cross-site tracking?
No. Kleerr uses first-party infrastructure and first-party cookies on your domain. It does not use third-party cookies, third-party identity data, or cross-site tracking.
Can we measure attribution without exposing individual PII?
Yes. Aggregate-only mode performs journey stitching on hashed values so individual PII is not stored or exposed in the platform while teams retain attribution and data-recovery capabilities.
What data does Kleerr not collect?
Kleerr does not collect browsing history outside your site, data from sites you do not own, third-party identity data, or PII from anonymous visitors.

Add the script. See it working in minutes.

One lightweight script on your domain. First-party data from day one. Choose your privacy mode and go.

  • Install in under 5 minutes
  • No third-party cookies or cross-site tracking
  • Opt-out, opt-in, or aggregate-only — your call
Quick 2 min estimate