Do I need this if Koo's analytics are cookie-free?

Koo's own analytics don't need consent. But if you add Google Analytics, Meta Pixel or any other third-party tag, a consent banner is required in most regions. Koo blocks those scripts until the visitor consents.

Does it handle IAB TCF?

IAB TCF support is on the roadmap. Today, Koo supports simple accept/decline and category-level consent.

Are consent records stored?

Yes. Koo stores a timestamped, hashed record of each consent event in a first-party cookie.

Can I customise which scripts are blocked?

Yes. Tag each third-party script with a consent category and Koo blocks or allows it based on the visitor's choice.

Cookie consent

A configurable GDPR and CCPA consent banner, built right in

Koo drops a branded consent banner on your site in one toggle. Configure GDPR, CCPA or both, customise the button labels and categories, and let Koo store consent records so you stay compliant.

GDPR and CCPA out of the box

Toggle between frameworks or run both. Koo serves the right banner based on the visitor's region.

Per-site configuration

Each site gets its own banner text, button labels and consent categories. Nothing shared across sites.

Respects user choice

Consent preferences are stored in a first-party cookie. Koo respects opt-outs on every subsequent visit.

Matches your brand

The banner inherits your site's colours and typography. It won't look like a bolt-on.

In one sentence

Enable the banner in your Convert tab, pick GDPR or CCPA mode, customise the copy and Koo handles storing consent preferences. No external scripts or cookie managers to pay for.

How it works