How our tools actually work
Understanding what happens when you use a ConvertAtlas tool is part of trusting it, so here is the honest technical picture.
Everything runs client-side
When you open a tool page, your browser downloads a small amount of JavaScript. From then on, every action — formatting, encoding, hashing, generating — happens on your device. There is no API call carrying your input to a backend, because the logic lives in the page itself. You can confirm this in your browser’s network tab: typing into a tool produces no network requests.
Secure primitives where it counts
Cryptographic operations use the browser’s built-in Web Crypto API where possible — for example SHA-256, SHA-512 and HMAC use the same vetted implementation your browser ships with. Random values for UUIDs, tokens and passwords come from crypto.getRandomValues, a cryptographically secure source, never from predictable pseudo-randomness.
Verified against references
Before a tool ships, its output is checked against authoritative references and known test vectors — for instance, hash functions are validated against published expected values. Where we re-implement an algorithm from an open-source project, we credit the original and re-verify the result rather than trusting it blindly.
What we do and don’t collect
We do not store, log or transmit the content you put into any tool. Like most websites we use privacy-respecting analytics to understand which tools are useful and optional advertising to keep ConvertAtlas free; both are governed by your cookie choices and our Privacy Policy. The data inside the tools themselves never enters that picture.