Built with Chinaski

Cookie Notice

Chinaski ships a lightweight cookie-consent banner: a one-line notice with Accept and Decline buttons, displayed on public pages until the visitor makes a choice. No external scripts, no consent platforms — the whole mechanism is server-rendered HTML with a small inline script injected at build time. This page covers the setting, what it does, and how it interacts with the analytics loaders.

Enabling the notice

Off by default. Turn it on under Settings → Integrations (“Display cookie notice on the public site”). The banner renders on pages, posts, and the blog index — the templates a visitor browses content through. Backup and utility pages (404s, offline fallback) don’t carry it.

Once enabled, the banner appears on every such page until the visitor responds. A repeat visit (same browser) won’t re-show the banner: making a choice stores a first-party cookie_consent cookie for one year.

What the banner offers the visitor

  • The text — your notice text, or the shipped default (“This site uses cookies to improve your experience.”).
  • Learn more — a link to your cookie policy URL, shown when one is set.
  • Accept / Decline — the two buttons set the consent cookie to granted or denied respectively. Both choices have the same duration (one year) and are evenly first-party.
  • Escape hides the banner for the current view only — an escape hatch without recording a decision, so the banner reappears next page.

Nothing leaves the visitor’s browser: the banner stores one local cookie and hides itself — no beacon, no platform, no network callback.

Configuring the banner

Settings → Integrations is where the banner is configured:

  • Notice text — free text; blank falls back to the default sentence.
  • Cookie policy URL — renders the “Learn more” link when set.
  • Button labels — customize “Accept” and “Decline” wording.

Each configured language can override the notice text and both button labels via its own per-language field, so a multilingual site shows the notice in each language.

Consent isn’t just a banner — the builder’s GA4/GTM loaders are wired to it. When the cookie notice is active:

  • The analytics loader waits for a “consent = granted” cookie before ever loading.
  • A visitor who has declined never loads analytics (their cookie_consent stays at decline for the full year, suppressing the loader everywhere).
  • A visitor who has yet to choose… does not get analytics until first interaction (the loader also waits for the first click/scroll/keydown/touch) and consent — so “no answer yet” means “no tracking”.

With the notice disabled, the loader instead respects an explicit decline cookie — but no consent gate is otherwise active.

Simple by design

The banner is a static site component with a first-party cookie — no tracker, no consent platform, no challenge other than the two buttons. If your site has no analytics or other cookie-adjacent JavaScript, the notice is just a compliance convenience; if you run GA4/GTM, the consent state gates those scripts as described above.