Consent management
The cookie banner that comes with the platform
Most websites bolt on a consent tool from yet another vendor. BespokeLMS ships a full consent management programme inside the platform — so there is no extra subscription, no plugin and no integration to buy or keep in step.
Bolted on, or built in
| With a bolt-on tool | Built into BespokeLMS |
|---|---|
| Another subscription, another invoice, another vendor to keep in step with your site. | Included with the platform. One supplier, nothing extra to buy, nothing to fall out of date. |
| A banner script you paste in and a cookie policy somebody maintains by hand. | Banner, blocking engine and cookie policy are generated from one configuration, so they can never disagree. |
| Consent lives in the banner tool while your marketing list lives somewhere else. | Consent and marketing permissions are one fact: withdraw on the website and the Sales CRM knows in the same request. |
What the consent engine does
-
A banner in your brand
The banner takes its colours, corners and typeface from your brand kit by default, and the designer gives you full control — layouts, positions, wording, languages.
-
Delivery, your way
Full banner, quiet notice or link-only — you choose how consent is asked for per site. The floor never moves: blocking stays on until a visitor agrees.
-
Blocking that fails closed
Non-essential scripts and embeds are held back server-side and in the browser until consent exists. If anything is uncertain, nothing loads.
-
An evidential ledger
Every decision is recorded append-only with a hash of the exact interface the visitor saw. If a consent is ever questioned, you can prove what was shown.
-
A cookie policy that writes itself
Your policy page renders from the same declared purposes and vendors that drive the banner and the blocking — declare a vendor once and all three update together.
-
Regional rules and GPC
Per-region opt-outs are honoured, and a browser Global Privacy Control signal is treated as the choice it is — without asking again.
Why it lives inside the platform
Because a website, a CRM and a consent tool that come from three vendors will disagree — about who consented, to what, and when. Ours cannot: the site that collects consent, the ledger that records it and the CRM that acts on it are the same system.
Hosted sites get the banner with zero installation. A site hosted elsewhere adds one script tag, restricted to the domains you have verified.
Questions we get about consent
Do we need a separate cookie-banner subscription?
No. The consent management programme is part of the platform — banner, blocking, policy, records and reporting included.
Does it work on a website not hosted on BespokeLMS?
Yes. One script tag, served from your site key and locked to the domains you have verified. A copied key on an unknown site gets nothing.
What happens when a visitor withdraws?
Blocking applies immediately in their browser, the withdrawal is recorded in the ledger, and if they had given marketing consent on a form, the CRM permission is withdrawn in the same request.
Whose name is on the banner?
Yours. It carries your brand by default, and the small attribution line can be switched off — white-label means their visitors think about them, not us.
See your banner in your brand
Bring your domain. We will show you the banner, the blocking and the ledger running under your own name.
Book a consultation