GDPR and the consent banner

The banner is a deploy stage you opt into per project. It is off by default: Weblooks never injects anything into your site automatically. Once enabled, the next deploy ships the banner, with the Reject option the same size and prominence as Accept, by design. Ask your agent to turn it on with the set_consent_banner tool. There is no settings screen for it yet, and nothing changes on your live site until you publish again.

Nothing non-essential runs before the visitor makes a choice. Consent-gated tags (analytics, marketing pixels) stay inert until the matching purpose is accepted, and only then does the banner activate them. A banner that appears after the trackers have already loaded is decoration, not consent, so the ordering is the whole point. This is why each tag has to be added as a consent-gated one in the first place: switching the banner on does not hold back a tag that was added the ordinary way, because that tag has already run by the time anyone is asked. The banner itself speaks English, Swedish, German, French and Spanish, following each page's own language. If the built-in design does not suit your site, you can supply your own banner markup and keep the same engine behind it; ask your agent about custom consent banner markup. Whichever you use, make sure refusing is as easy as accepting.

GDPR requires you to be able to demonstrate that consent was given, not just assert it. Every grant and withdrawal is recorded with the purposes chosen, the privacy policy version in force, and a timestamp. Records are pseudonymous: no IP addresses, emails, or account ids are stored, and records expire automatically (roughly thirteen months by default).

Find it under Checks → Consent log in the project. It is read-only, because an editable log is not evidence. Sites that run their own banner can post decisions to the same log through a small public API.