The inventory
Everything this site stores
These are the only storage mechanisms fmttools.com uses. There is no service worker, no offline application cache, no IndexedDB database and no Web SQL store, so nothing else is written on your device beyond the ordinary HTTP cache your browser maintains for every site you visit.
| Mechanism | Name | Purpose | Lifetime |
|---|---|---|---|
| First-party cookies | — | Not used. Nothing on this site reads or writes document.cookie. | — |
| Third-party cookies | — | Not used. No embedded frames, tags or pixels exist to set them. | — |
| Local storage | fmttools-cookie-consent | Remembers whether you chose allow optional or necessary only in the consent prompt, so the prompt does not reopen on every page. | Until you clear site data or reset it from the footer |
| Session storage | — | Not used. | — |
| IndexedDB / Web SQL | — | Not used. | — |
| HTTP cache | Page, script, CSS and image files | Your browser re-fetches nothing it already holds. This is a performance mechanism controlled by your browser, not a tracking identifier: it holds no user-specific value. | Governed by the cache headers your browser receives |
Classification
Cookie categories, and which apply
Consent frameworks group storage into categories. Here is what each one would cover on a site like this, and the honest status of each:
| Category | What it would cover here | Status |
|---|---|---|
| Strictly necessary | Storage without which the page cannot function: a session on a login site, a load-balancer affinity cookie. | None needed. There is no login, no cart and no server-side session. |
| Preferences / functionality | Choices that personalise the interface: language, theme, panel layout. | One local-storage key for your consent choice, written only after you click. Nothing else. |
| Analytics | Measuring page views and conversion, e.g. Google Analytics, Plausible, Fathom. | Not used. No measurement ID, tag or script is loaded. |
| Advertising / marketing | Ad targeting, frequency capping, attribution; typically third-party. | Not used. No ad network, no affiliate redirects, no social pixel. |
| Cross-site tracking | Any identifier readable by more than one domain. | Not used, and not possible while the site ships no third-party requests. |
The apparent contradiction
Why there is a banner at all
A cookie banner on a site that sets no cookies looks like boilerplate copied from a competitor. It is here for two specific reasons:
- Your choice is recorded before anything could change. Regulations such as the EU ePrivacy Directive and the GDPR require consent to be captured before non-essential storage is written. Storing that preference now means that if an analytics or advertising service is ever added, the switch is gated by a decision you already made rather than retrofitted after the fact.
- The two options behave identically today, and we say so. Choosing Allow optional enables nothing, because there is no optional service to enable. Clicking it writes one local-storage key and closes the prompt.
The legal basis for that single key is consent (GDPR Article 6(1)(a)); the basis for serving you the page itself is performance of a request you made (Article 6(1)(b)). Under Article 7(3) you can withdraw consent at any time using the controls below, and withdrawal does not affect what was already lawful.
Data flow
What leaves your machine, and when
Every converter on this site — JSON formatter, validator, minifier, CSV to JSON, JSON to CSV, JSON to YAML, YAML to JSON, Base64, URL encoder — parses and rewrites text inside your browser tab using JavaScript that was downloaded once. Your input never becomes a request body. There is no upload endpoint to send it to, no account system to attach it to, and the result is handed back to you as a Blob download generated locally.
The requests your browser does make
Loading a page sends an ordinary HTTP request for that document plus its CSS, JavaScript and images. That request carries a destination URL, and the server learns what any web server learns: see the next section. Navigating between pages produces one such request each. Typing in a tool, formatting, converting, downloading a result and copying to the clipboard produce zero requests.
What the server sees
Hosting, logs and retention
Pages and assets are served as static files from shared hosting with a reverse proxy in front. That infrastructure writes the conventional web-server access log for each request: timestamp, request line (method, path, protocol), HTTP status, response size, Referer and User-Agent headers, and the client IP address. Aggregate traffic reporting is derived from those files.
We do not add our own logging layer, and the application has no database, queue or request handler that could receive submitted content. Log retention follows the hosting control panel's rotation settings; the practical consequence is that a log line outlives a page view but not indefinitely. If you want even that, reach us at the address below and we will confirm the current rotation window.
None embedded
Third-party services
No fonts, scripts, stylesheets, images or iframes are fetched from another domain. The interface uses your operating system's own font stack, all artwork is served from this origin, and the only external URLs on the site are plain links you choose to click — the specification documents in the footer (IETF, W3C, yaml.org) and the reference links inside the guides.
Once you click one of those links you are on that organisation's site under its own policy, and your browser sends it the usual headers and Referer. That transfer is started by your click, not by anything embedded here.
Your side of it
Changing or clearing your choices
- Change your mind. Use Cookie settings in the footer of any page. The prompt reopens with your current choice shown, and saving replaces it.
- Delete it outright. Your browser's site-data controls for
fmttools.comremove the key, or send us a request and there is nothing on our side to delete, because the choice never leaves your device. - Block it in advance. Private-browsing modes and storage-blocking extensions will prevent the key from being written. The consequence is only that the prompt reappears on each page load; no feature depends on it.
Keeping this accurate
Changes and contact
If this site ever starts setting a cookie or loading a third-party service, this page is rewritten first: the inventory table gains the real name, purpose and lifetime of each entry, and the effective date at the top changes. The version above describes the code as deployed on November 18, 2026.
Questions about any of this, or a request to confirm the log-retention window, go to [email protected], or use the form on the contact page.