Preview — how the banner will look on your website
💻
Generated Code
▾
Add the HTML in your page's <body>, the CSS in your stylesheet or a <style> tag, and the JavaScript before </body>.
HTML
CSS
JavaScript
Case workspace
Build, save and export this legal workflow
This workspace turns the consent design and code check result into a reusable matter note, dashboard item and gated PDF checklist. Use the app first, then save the evidence trail.
Benchmarked against Termly, OneTrust and enterprise consent platforms. The goal is not to copy them; it is to bring the useful workflow pattern into an Africa-first tool with official-source caution and local evidence capture.
Observed feature pattern
Mature privacy tools scan or map real processing activity, then connect policies, cookie choices, DSARs, consent logs and regulator evidence.
They preserve an audit trail instead of leaving users with a static policy that drifts away from the product.
They route high-risk processing into DPIA, breach and processor-contract workflows before launch or vendor onboarding.
Implemented on this app
This page now asks for matter, country or regime, date, status, evidence and risk flags before the user exports a note.
The app-specific checklist is not generic: it starts with "Audit actual cookies in the browser before publishing the banner".
Saved workflows can be resumed from the dashboard and handed off to Privacy Policy Generator when the matter naturally continues.
The PDF/export moment is a value-after-result gate, so users can still use the tool first and only share email when saving the report.
Best next move
Which cookies are strictly necessary, analytics, advertising, preferences or security
Audit actual cookies in the browser before publishing the banner
A banner that says “accept” but loads tracking before any choice
Reviewed 28 April 2026 · Banner generator
Consent design and code check
A banner is compliant only when the site behaviour matches the choice. Non-essential analytics, advertising and tracking cookies should wait for consent where consent is required.
Decisions this clarifies
Which cookies are strictly necessary, analytics, advertising, preferences or security
Whether opt-in, opt-out or notice-only is appropriate for the target jurisdictions
How users can withdraw or change consent later
Before you rely on it
Audit actual cookies in the browser before publishing the banner
Block non-essential tags until the saved preference allows them
Keep a visible preference link in the footer or account area
Red flags
A banner that says “accept” but loads tracking before any choice
No reject button where opt-in consent is required
Using dark patterns that make refusal harder than acceptance
Before filing, signing, publishing, or sending anything, keep a short record that links the app result to evidence and official-source checks.
Capture
Save the country or regime, parties, dates, amounts, selected options, and final output. Add why this matters: Which cookies are strictly necessary, analytics, advertising, preferences or security.
Attach
Audit actual cookies in the browser before publishing the banner. Also keep the strongest supporting document, receipt, portal reference, ID, contract, policy, or court file beside the generated result.
Escalate
If you see this risk, pause and get qualified help: A banner that says “accept” but loads tracking before any choice.
Paste this into your matter file, compliance folder, board pack, or lawyer handoff.
Cookie Consent Requirements Under African and EU Law
Cookie consent banners are required by data protection laws that mandate user consent before setting non-essential cookies. The EU GDPR, Nigeria's NDPA 2023, South Africa's POPIA, and Kenya's DPA 2019 all require prior consent for analytics, marketing, and tracking cookies.
A legally compliant cookie consent banner must: (1) appear before any non-essential cookies are set; (2) clearly explain what cookies are used; (3) offer a genuine option to decline; (4) not use dark patterns to manipulate consent; (5) record and store the user's consent choice.
Under the NDPA 2023, Nigerian websites must obtain consent before setting non-essential cookies.
POPIA requires consent for processing of personal information through cookies used for tracking individuals.
Essential/necessary cookies (site functionality, security) generally do not require consent.
Consent must be freely given — pre-ticked boxes, cookie walls, and bundled consent are not compliant.
Disclaimer
This tool provides general information and educational resources only. Not legal advice. Generated code is a template — review with a qualified lawyer before deploying on your website.