Abluo, the tiny CMS
Build notes

Why we built cookie consent ourselves

1 min read

A consent banner that appears only when needed, wears the site’s design and remembers the answer. Built into every Abluo site, no extra fees.

Abluo Journal: notes on calm publishing, from the team behind Abluo, the tiny CMS

Most small websites solve cookie consent with a third-party service billed per domain, per month. Abluo already knows exactly which scripts and embeds each site loads. So instead of adding another subscription, consent became part of the platform.

A banner only when it’s needed

Whether the banner appears is not a setting. It is derived from the site itself: if a site uses analytics, marketing or functional cookies, the banner shows. If it uses none, there is no banner at all. There is no switch that hides the banner while tracking stays on.

Fair by design

  • Accept all and Reject all look exactly the same. No button is made more tempting.
  • Closing the banner counts as a refusal. Scrolling is never consent.
  • Customize shows each purpose separately, with nothing pre-ticked.
  • A Cookie settings link in the footer lets visitors change their mind at any time.

Remembered, not repeated

Nobody likes a banner that returns on every visit. A choice is remembered for 12 months on that site. We ask again earlier only if the services behind a purpose change, and never sooner than six months after a refusal.

Embeds and fonts

Google Maps loads only after the visitor allows it, with a simple placeholder until then. Google Fonts are served from the site’s own address, so visitors’ IP addresses never reach Google just to display text.

The banner takes its colours, type and motion from each site’s design system and speaks seven languages. It follows the Italian Garante’s 2021 cookie guidelines and is designed with the EU’s proposed Digital Omnibus rules in mind.

Want a website where compliance is simply handled? Request early access.