Legal
Cookies
Last updated July 12, 2026. What cookies and similar local storage this site actually uses.
This page is kept separate from the Privacy Policy so it can be updated on its own as the specifics of ad-vendor cookies change, without touching the broader privacy commitments. It lists exactly what's stored in your browser, split into what's strictly necessary for the Site to function and what's set by third parties.
Current status
This Site's ad-consent flow uses Google AdSense for advertising and Google's Funding Choices as its consent-management platform (CMP). On every page load, Funding Choices loads first and determines whether consent is legally required for you and, if so, resolves it — no ad script requests an ad or sets an advertising cookie before that resolution happens, for any visitor, in any region. Until an AdSense publisher ID and ad units are actually configured for this deployment, however, this consent flow and every ad slot on the Site stay inert: no Funding Choices script, no AdSense script, and no advertising cookie of any kind loads. This page will be updated with the specific cookie names Google sets once ads actually go live.
What is stored today
None of the following are traditional HTTP cookies — they're local, first-party browser storage (localStorage and IndexedDB) that never leaves your device:
micro-tool-yard:theme(localStorage) — remembers whether you last chose light or dark mode.- Sidebar collapse state (localStorage) — remembers whether you last collapsed the tool sidebar to an icon rail.
- Tool history (IndexedDB, via the
localforagelibrary) — an optional local log of recent activity in tools that offer a history panel. Filenames and timestamps only, never file contents. Clearable at any time from within each tool.
None of this is a tracking mechanism in the advertising sense — it isn't shared with us, isn't used to identify you across sites, and exists purely so the Site remembers your own local preferences between visits, the same way a browser remembers a bookmark.
What is added once ads are live
Once an AdSense publisher ID and ad units are configured, the following becomes active — not before:
- Visitors in regions where consent is legally required (e.g. the EEA/UK) see a Funding Choices consent message before any advertising cookie is set, and no ad request fires until that consent choice is resolved. Visitors outside those regions have consent resolved immediately, with no visible banner, per Funding Choices' own geography-aware behavior.
- Google's advertising cookies are used for ad delivery, frequency capping, and — where you consent — ad personalization and measurement. These are set and controlled by Google, not by us directly; Google's own cookie documentation applies to them.
- A minimal, privacy-respecting analytics beacon (Cloudflare Web Analytics) may also be added, which does not use cookies or any persistent client-side identifier at all — it reports aggregate page-view and performance metrics only.
Managing or clearing local storage
You can clear everything this Site has stored in your browser at any time via your browser's own "Clear site data" or "Clear cookies and site data" setting for this domain, or by using the "Clear all local data" action available inside any tool that has a history panel.