Technical Transparency
"Runs in your browser, nothing is sent to a server" is an easy claim to make and a hard one to trust blindly. This page explains exactly what that means mechanically, so you don't have to take it on faith — you can check every claim below yourself in under a minute.
Zero network requests for tool data
Every tool (JSON, JWT, YAML, CSV, OpenAPI, Base64, UUID, timestamp, regex, JWKS/PEM, JSON Schema) is implemented with plain browser-native APIs — JSON.parse, the Web Crypto API for JWT signatures and JWKS/PEM conversion, atob/btoa for Base64, regular string/array processing for everything else. None of it calls fetch or XMLHttpRequest to send what you typed anywhere.
Verify it yourself: open your browser's DevTools, go to the Network tab, use any tool with real (or fake) sensitive data, and watch the request list. You'll see the initial page load and nothing else — no request fires when you click Validate, Decode, Convert, or any other tool button.
What's actually stored, and where
localStorage['cryonel-theme']— your light/dark mode preference. One string, set only when you click the theme toggle, never read by anything except the page itself.- sessionStorage (a short-lived handoff key) — when you click a "Send to X" button to move a result from one tool into another, the value is written to sessionStorage, the browser navigates to the next tool's page, and that page reads and immediately clears the key. It never leaves your browser and doesn't survive a tab close.
- Nothing else. No cookies are set by Cryonel's own code, and there's no analytics script (no Google Analytics, no Plausible, no tracking pixel) on the site today.
The service worker only caches files, not your data
Cryonel registers a service worker (/sw.js) so the site loads fast and works offline after your first visit. It caches static files — HTML, CSS, JS, icons — using a network-falling-back-to-cache strategy. A service worker can only see requests that actually go out over the network; since tool data never triggers a network request in the first place, the service worker never sees it either.
Advertising
The interface has ad placeholder slots reserved in the layout for when monetization is enabled, but as of this writing no ad network script is loaded on the site — the slots are hidden via CSS. If and when an ad network like Google AdSense is turned on, it will be declared here and in the Privacy Policy, and — like every other part of this site — it has no access to what you type into a tool, since that data never leaves the tool's own JavaScript.
Open source
Don't take any of the above on faith either — the entire frontend is public. Read the actual code for any tool at github.com/semihbugrasezer/wp-cryonel.