Who it's for
Four kinds of people use this. Here's what each of them gets.
The product is the same for everyone: hold the trackers, watch what happens, keep the record. What differs is what you need out of it. Pick the one that sounds like you.
Agencies
One account, 25 client sites on the Agency plan, and a published rate for anything beyond that — never a wall, never a surprise bill. Reports with your name on them instead of ours. Every site re-checked weekly, so you find a new tracker before your client does. You bill compliance as a retainer; we produce the paperwork underneath it.
A demand letter lands on your client and reaches you by lunchtime. You need to show what your blocking actually did — quickly, across every site you manage, branded as yours. A screenshot of a cookie panel isn't a record.
Founding customers — closes December 31, 2026. Join before then and keep your price for as long as you stay — Agency at $99/month, or Scale at $299/month (5 places). Prices go up in January for anyone who joins after.
At a glance
Free to start. We will set up your first 5–10 client sites with you.
What you get
Every client in one account
All your clients' sites, scans and reports in one dashboard. 25 included on Agency; extra sites at a published monthly rate, with no plan change and nothing switching off.
Reports with your name on them
Your logo and your company on the Privacy Defense Report. Your clients don't have to see ours.
Checked every week, automatically
Every verified site, every week. A new tracker becomes a notification instead of a discovery.
One invoice
One subscription for the whole portfolio, and an extra-site rate you can quote to a client before you agree to it.
Small business
You're not a European enterprise with a privacy department. You run a US business with a website, and you've started hearing that a California law might apply to you — probably because it happened to someone you know. You get the same protection the big platforms get: one line of code, a cookie banner that actually holds things back, and a proper check of your own site. Free.
You can't put a compliance retainer on the books, and you don't need software built for a European privacy team. But one demand letter still costs you real money — and “I thought my cookie banner handled it” is exactly what the businesses getting those letters thought.
At a glance
One site, unlimited visitors, no credit card.
What you get
Free forever, one site
Unlimited visitors, no credit card. Prove the site is yours by adding a short line of text to your domain settings, and we'll check up to 100 pages of it.
The protection isn't the paid part
Holding trackers until consent, honoring “don’t sell my data” browser settings, Google's consent setting and your own per-tracker rules are all full strength on Free. What you pay for is more sites, deeper checks, longer history and the report.
One line of code
Paste it once, at the top of your page. You don't need a developer.
Results in plain English
We check up to 100 pages and show your overall result in full, plus your 3 most serious findings. The complete list — every request, every page, every tracker — is on Pro and up.
Compliance & legal teams
You already have a consent tool. We're not asking you to replace it. What you probably don't have is an independent account of what your website actually did — taken by something that isn't the tool being asked about, in a real browser, and written down so it can't be edited afterwards. That's the whole job here. Your consent tool reports on itself. We report on your website.
Your consent tool's dashboard says “blocked.” Someone — outside counsel, an auditor, the other side — asks what that was based on. A vendor reporting on its own behavior isn't an independent record of what loaded.
At a glance
100 sites, deeper checks, set up with you rather than self-serve.
What you get
Something you can hand to a lawyer
One document per scan: the banner as visitors saw it, everything sent before anyone agreed, what was held, which tracker caused which cookie, and your full settings history. In date order.
Independent of your consent tool
Our check doesn't read your settings before judging them. A site configured to let Google's tags run early still comes back “exposed” on its own scan, because the check is deliberately blind to that setting. We don't grade a configured exposure on a curve.
A record nobody can quietly change
Every observation is fingerprinted into a code that can be re-checked at any time, over a history nothing rewrites. The report itself states plainly what that fingerprint does and doesn't prove: there's no official timestamp and no digital signature.
If a block fails, the report says so
A check that runs after you've blocked something and still sees it running is reported as a failure. We don't quietly re-mark it green.
Legal hold on every plan
Stops our normal deletion schedule and keeps everything, whatever your plan's retention window says. Not an upsell. Self-serve on paid plans, by request on Free.
What this does not cover
Tracking that happens server-to-server is invisible to any tool of this kind, ours included. Fonts loaded by style files can't be held by anyone. And on a locked website builder like Wix, the platform's own tags can't be stopped by any consent tool. All three are in the report, named.
WordPress developers
You build or maintain WordPress sites. Our plugin runs server-side and reaches the tags other plugins enqueue — before the page is sent, which no client-only tool can do. That lets you answer a client's compliance question with a mechanism instead of a shrug. It's free, it's GPLv2+, and the account is where the crawl and the record live.
A client asks “are we CIPA-compliant?” and every client-side tool answers “probably.” You want to point at what the server actually sent, not at a dashboard status.
At a glance
Free · server-side blocking · in the WordPress plugin directory.
What you get
Server-side gating, scoped honestly
Tags another plugin enqueues (wp_enqueue_script) are rewritten before delivery, on by default. Tags a plugin prints directly into wp_head need output-buffer gating switched on — it's off on a fresh install. Tags injected at the CDN edge land after PHP finishes and no plugin reaches them.
A measured result you can repeat
On a live site with output-buffer gating on, zero pre-consent requests to googletagmanager, google-analytics, connect.facebook.net, cdn.pagesense.io and pagesense-collect.zoho.com. Measured 2026-07-30 at plugin 0.2.63, and confirmed independently on a second site the same day.
Documented ceilings
Hooks, filters, and a written list of what the plugin can't patch: CDN edge injection, @import-delivered font CDNs, and page caches that captured HTML before the gate ran.
Free, GPLv2+, on WordPress.org
Install it from your WordPress admin like any other plugin — search for Consentinel Cookie Consent. Listed in the plugin directory since September 2026.
Consentinel is compliance software, not legal advice. Nothing on this page creates an attorney-client relationship or guarantees compliance.