Skip to content
FmtTools

Site policy

Cookie Policy

Short version: this site does not set cookies. Not first-party, not third-party, not analytics, not advertising. The one thing it writes to your browser is a single local-storage key that records your answer to the consent prompt. Everything below is the full inventory, plus what the web server still sees when it serves you a page.

Last updated November 18, 2026

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.

Complete storage inventory for fmttools.com as of November 18, 2026
MechanismNamePurposeLifetime
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 storagefmttools-cookie-consentRemembers 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 cachePage, script, CSS and image filesYour 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:

CategoryWhat it would cover hereStatus
Strictly necessaryStorage 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 / functionalityChoices that personalise the interface: language, theme, panel layout.One local-storage key for your consent choice, written only after you click. Nothing else.
AnalyticsMeasuring page views and conversion, e.g. Google Analytics, Plausible, Fathom.Not used. No measurement ID, tag or script is loaded.
Advertising / marketingAd targeting, frequency capping, attribution; typically third-party.Not used. No ad network, no affiliate redirects, no social pixel.
Cross-site trackingAny identifier readable by more than one domain.Not used, and not possible while the site ships no third-party requests.

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.com remove 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.