Consent that knows who it is.
ConsentBridge records every cookie consent against the WHMCS client and order it belongs to. It blocks non-essential tags, feeds Consent Mode v2, and keeps a tamper-evident proof trail in your own database.
First 30 licenses. Refundable until the first release.
hash 9f2c…a41d hmac-sha256
chain verified · anchor 2026-10-31
The gap
Your CMP knows the browser. Your billing knows the customer. Nobody connects them.
A page consent tool answers "did this browser accept cookies". It cannot answer the question a regulator, a lawyer or an angry client actually asks: which client consented, to what text, and can you prove it?
Consent lives in the wrong place
Page CMPs store decisions in their cloud, keyed by a cookie. When the visitor logs in, the consent and the account are two unrelated facts.
WHMCS cannot prove consent
The built-in tools export and delete client data. None of them record what the visitor was shown, when, and what he chose.
Support cannot answer the ticket
"Show me everything you hold about me, and when I agreed to it" turns into a manual hunt across tables, logs and a third-party dashboard.
How it works
Four moves, all inside your installation.
Capture before any tag runs
The module injects a 630-byte snippet with default: denied and a 1.4 KB loader. No theme file is edited:
it attaches through ClientAreaHeadOutput, so Six, Twenty-One, Nexus and custom themes all get it.
Block by purpose, not by banner
Four purposes (necessary, preferences, analytics, marketing). Non-essential scripts are held by
data-block, by GTM consent settings and by a runtime guard. Unmanaged tags are reported, not hidden.
Bind the decision to the account
When the visitor is logged in, the record carries client_id. When not, it is linked on
ClientAdd through an HMAC of the email, and checkout adds the order_id.
Prove it, or withdraw it
Every record is appended to an HMAC-SHA256 chain with a daily anchor. A withdrawal is a new record, never an edit. The proof dossier exports as JSON and PDF with a public verification page.
Proof
Thirteen fields. One chain. Zero trust in the dashboard.
A consent record is only evidence if it can be recomputed. ConsentBridge stores the exact text
version shown, the decision, the source and the identity link, then chains each row to the previous one with
an HMAC key that lives in configuration.php, outside the database dump.
Any edit to a stored row breaks the chain at that point, and the daily anchor tells you when it happened. That is what "tamper-evident" means, and it is the only claim worth making.
records 10.482 · anchor 2026-10-31 · chain intact
What the dossier answers
Compare
Same banner. Different question answered.
| Page CMP e.g. CookieYes, Cookiebot | ConsentBridge | |
|---|---|---|
| Knows which WHMCS client consented | No, keyed by browser cookie | Yes, client_id and user_id |
| Links consent to order and invoice | No | Yes, order_id on checkout |
| Blocks checkout server-side for terms | No | Yes, required for contract only |
| Where the proof lives | Vendor cloud | Your MySQL, chain anchored daily |
| Pricing unit | Per domain and pageviews | Per installation, no pageview meter |
| Data subject clock | No | 15/30 days, 3/6 business days, evidence of execution |
| Reads consent from an existing CMP | n/a | v1.1 coexistence mode |
| Consent Mode v2 and GPC | Yes | Yes |
Competitor behaviour taken from vendors' published feature pages, October 2026. Page CMPs are good at what they do; this table only shows the questions they were not built to answer.
Pricing
Per installation. No pageview meter.
All prices in US dollars. One WHMCS installation plus the marketing site of the same controller.
Founder · first 30
one-time · refundable until first release
- Full license, all MVP features
- 12 months of updates and email support
- Founder price locked on renewal
- Direct line to the maintainer
License · after launch
one-time · 12 months of updates included
- 1 WHMCS installation
- Up to 3 properties or brands
- Consent Mode v2, GPC, blocking
- JSON/PDF dossier with verification
Updates & support
per year, from year 2
- New WHMCS major compatibility
- Email support, 2 business days
- Keeps the chain verifier current
- Optional: no renewal, module keeps working read-only
Not included on purpose: legal advice, a compliance guarantee, or coverage of third-party sites you do not control. The controller decides the legal basis; the module records and proves what happened.
FAQ
The questions buyers actually ask
Does it guarantee LGPD or GDPR compliance?
No, and nothing can. ConsentBridge records consent, proves what was shown, blocks tags and tracks the data subject clock. Legal basis, retention, security of the server and the answer to the data subject remain with the controller.
We already use CookieYes. Why add this?
Because your CMP does not know which WHMCS client consented, cannot block checkout on terms acceptance, and
cannot produce a dossier that ties a decision to client_id and order_id. In v1.1 the
module reads the state from your existing CMP and mirrors it into that record, so you do not need to replace anything.
Will it break my custom theme?
The module never writes to templates/ or orderforms/. Everything is injected through hooks,
including the checkout checkbox, which lands inside the cart form. If a theme misses the injection point, the admin
reports it instead of rendering a broken banner.
What does it add to page weight?
A 630-byte inline snippet plus a 1.4 KB gzip loader: 2.0 KB total, one request, no render blocking. For comparison, Cookiebot's script measures 28 KB gzip and gtag alone is 153 KB gzip.
Does it work with WHMCS 8.x?
Yes, 8.13.x on PHP 8.2 and 8.3, and 9.0/9.1 on PHP 8.2 to 8.4. WHMCS 9 removed PHP 8.1 support, so the matrix follows the platform, not our preference.
Where does the data live?
In your MySQL. The license check never sends client data, email addresses or IPs to us; it only validates the key. There is no external CMP, no tag manager of ours and no SaaS dashboard holding your consent records.
When does the first release ship?
Founder licenses are being reserved now and are refundable until the first release. Building starts when the first cohort is reserved, and the release candidate goes to founders before the Marketplace listing.
Reserve
Founder license · $59
Tell us the installation and we send the reservation and the invoice with the founder terms. No payment page, no card data on this site.
Refundable until the first release. The founder price stays locked on future renewals for the first 30 licenses.