Opt-Out Signal Lint for US State Privacy Laws

It reads your source files and flags the exact lines that ignore an opt-out preference signal: ad pixels that initialise unconditionally, consent defaults set to granted, and signal checks written against the wrong value. Each finding names the line, the reason it is a sale or share, and the corrected code.

Front-end and full-stack developers at US-facing e-commerce and SaaS companies who own the analytics and advertising tag code, and the agencies who inherit those repositories. If someone on your team wired a Meta pixel or a Google Ads tag into a checkout flow, this is the file it reads.

A page scanner loads a rendered page and reports the tags that fired for that one region, consent state and code path. It cannot see the isEU branch that never runs for a US visitor, or a pixel behind a feature flag. It also runs after deployment, when the share has already happened.

The file you have open is fully audited for free — all 20 rules, every line, no key and no cap. A licence key adds a different job: sweeping the whole workspace, exporting the finding list as CSV, JSON or HTML, and a CI exit code so a fixed leak cannot come back in a later merge.

Osano, the nearest hosted consent platform, starts at $199/month, and a privacy engineer reading the same repository by hand bills far more than that for a single pass. This is $29 once, one licence key per person or team seat, with a 7-day full refund.