CIPA § 631 Risk

Is Crazy Egg legal in California?

Heatmaps & Recordings · Updated 2026

Crazy Egg captures recordings and heatmaps of how visitors interact with your site. Using it is perfectly legal — but running Crazy Egg before a visitor consents is what creates exposure under California's wiretapping law.

Why Crazy Egg can trigger CIPA claims

California's Invasion of Privacy Act (CIPA), Penal Code § 631, prohibits intercepting communications without all-party consent. Since 2022, a wave of plaintiff-firm litigation has applied this decades-old wiretapping statute to website session-replay, chat, and pixel tools — arguing that capturing a visitor's clicks, keystrokes, and form input without consent is an unlawful interception. Crazy Egg captures recordings and heatmaps of visitor behavior — gate behind consent.

Statutory damages run up to $5,000 per violation, and plaintiffs argue each affected visitor session is a separate count — which is why even small sites receive demand letters.

Real-world enforcement

In a landmark action, the California Attorney General reached a $1.2M settlement with Sephora over its use of tracking technologies without honoring consumer privacy choices. Private CIPA suits over session-replay and chat tools have named retailers, healthcare providers, and SaaS companies alike. The common thread: trackers firing before the visitor had any chance to opt out.

How to make Crazy Egg compliant

1. Confirm how Crazy Egg is installed. If it loads through Google Tag Manager, set the tag's "Consent" settings to require the relevant consent type so it cannot fire before opt-in.
2. Add GTM Consent Mode with all storage defaulting to "denied" (snippet below), and connect a CMP that flips consent to "granted" only after the visitor accepts.
3. If Crazy Egg is hard-coded as a raw <script> instead of via GTM, move it into GTM (or wrap it) so the consent gate actually applies — a raw snippet ignores Consent Mode.
4. Re-scan with RegSentry's "Verify fix" button to confirm Crazy Egg no longer fires before consent.

Consent-gating snippet

<!-- Place BEFORE the GTM/gtag snippet. Defaults all storage to "denied"
     so no tags fire until your CMP updates consent after the user opts in. -->
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('consent', 'default', {
    ad_storage: 'denied',
    analytics_storage: 'denied',
    functionality_storage: 'denied',
    personalization_storage: 'denied',
    security_storage: 'granted',
    wait_for_update: 500
  });
</script>

Your CMP (Cookiebot, OneTrust, Termly, etc.) calls gtag('consent','update',{...:'granted'}) only after the visitor accepts. Until then, tags stay blocked.

Crazy Egg's official privacy/consent documentation →

Check your own site

RegSentry runs a real browser against your site, watches exactly when Crazy Egg (and every other tracker) first contacts a third-party server, and captures the evidence — including whether it intercepts keystrokes typed into your forms.

← See all tracker compliance guides