Cookie policy
This site sets no cookies at all. That is the whole policy — here is how to verify it yourself, and why there is no consent banner.
Effective 1 August 2026. Last updated .
This site sets no cookies
Not one, of any kind. That is the whole policy: there are no cookies to accept, reject, or configure, which is why you have never seen a consent banner here.
We publish this page anyway, because "we use cookies to improve your experience" is the default text on almost every site, and a plain statement that we do not is worth making explicitly — and easy to verify.
How to check
Do not take our word for it. In any browser, open developer tools, go to the Application or Storage panel, and look at the cookie list for this domain. It is empty. The same panel will show that Local Storage, Session Storage, and IndexedDB are empty too.
What we do not use
- No analytics. No Google Analytics, no Plausible, no Fathom, no server-side page-view counting beyond ordinary access logs.
- No advertising or tracking cookies. No ad network, no retargeting pixel, no conversion tracking, no fingerprinting.
- No social embeds. No share buttons, no comment widgets, no embedded video — each of which would otherwise set third-party cookies.
- No consent management platform. These are themselves a common source of tracking, and with nothing to consent to we do not need one.
- No preference cookies. We do not remember your indentation setting or anything else between visits. The trade-off is that you set your options each time; we think that is the right trade for a tool you use occasionally.
Browser storage
The converters keep the document you are working on in the memory of the page,
which is discarded when you close or reload the tab. Nothing is written to
localStorage, sessionStorage, or IndexedDB.
Your browser will cache our pages, stylesheet, and scripts so repeat visits are fast. That is ordinary browser caching, not a cookie, and you control it through your browser settings. Clearing your cache removes it.
Why no banner
Consent requirements — the EU ePrivacy Directive, the UK's PECR, and similar rules elsewhere — apply to storing or accessing information on your device where that is not strictly necessary for a service you asked for. We do neither, so there is no consent to obtain and a banner would be theatre.
The limited data we do receive, essentially short-lived server logs, is covered by the privacy policy.
If this ever changes
If we introduce anything that stores or reads information on your device beyond what is strictly necessary, we will update this page before it goes live, ask for your consent where the law requires it, and make refusing as easy as accepting.
Questions: contact@json-yaml.com.