Cookie policy

There is no consent wall on this site and no “we use cookies” banner that means nothing. This page lists what is actually stored, by whom, and how to get rid of it.

What this site stores itself

One entry, in your browser’s localStorage, under the key 56jqb/consent/ad-v1. It records whether you accepted ads, so the banner does not ask you again on every page. It never leaves your browser.

If you decline, no AdSense script is loaded and no request is made to googlesyndication.com — the consent flag is the only thing written, and it says “no”.

After you accept ads

Google’s AdSense loader sets and reads its own cookies for ad personalisation and reporting. Those are Google’s cookies on Google’s domains, managed by their loader, and their policy governs them. This site cannot read them and does not try.

Sign-in

If you create an account, your session is a signed cookie your browser holds and sends back. There is no server-side session table. Clearing site data signs you out; nothing else is affected.

How to clear it

• Consent flag: DevTools → Application → Local Storage → delete 56jqb/consent/ad-v1, then reload. The banner comes back and you can answer differently.
• Google’s cookies: your browser’s “clear site data” for this host, or Google’s own ad settings page.
• Nothing here is needed for the library to work: every component, prompt and guide is readable and copyable with storage cleared.