DevPrivacy Policy
Last updated: October 23, 2026.
The short version
The tools on DevClamp run locally in your browser. Whatever you type or paste into a tool is processed on your device and is never sent to us or to anyone else. We have no accounts, no sign-ups and no databases of user content — there is nothing for us to collect.
What your input does
No tool on this site transmits your input over the network. Most tools keep input only in your browser tab's memory — closing or reloading the page discards it.
Nine tools (the JSON formatter, the JSON ↔ YAML and JSON ↔ CSV converters, the Base64 and URL encoder/decoders, the timestamp converter, the regex tester, the JSON to TypeScript converter and the text diff checker) additionally auto-save your work in your own browser's local storage, on your device, so an accidental refresh does not lose it. Drafts expire automatically after 7 days. This draft never leaves your device, is not a cookie, and is not accessible to us or to any third party. Each of those tools has a Clear saved draft button that deletes the draft immediately, and you can also delete it at any time through your browser's site-data settings. Some tools are deliberately excluded: the JWT decoder, because tokens are credentials and are never written to storage; the hash generator, because what you hash may be a password; and the IP lookup described below.
The homepage can also pin the tools you use most: for that, your browser locally keeps a simple count of how often you open each tool page. That count is stored only in your browser's local storage on your device — there is no account and no server-side collection, and we cannot see it. Entries fade out after 90 days, and the Clear button on the frequent-tools strip erases the record immediately. The same local storage also remembers which of the site's usage tips you have already seen, so each tip is shown at most once; that read-state likewise never leaves your device.
One stated exception: the IP lookup
The What's My IP page answers a question that cannot be answered locally — what public IP address the internet sees for your connection — so, when you open that page, your browser sends one request to a third-party lookup service (ipwho.is, with ipapi.co as fallback). That service necessarily receives the IP address it reports, your browser's user-agent string and standard connection data, and its own privacy policy governs that request. The request goes from your browser directly to the provider: we do not receive, store or log your IP address, and every other detail on that page is read locally on your device.
Analytics
We use privacy-friendly, cookie-free analytics (Umami) to understand which tools and guides are useful, in aggregate: pages viewed, rough country, browser type. Analytics data does not include tool input, is not used to build personal profiles, and is not sold or shared. If analytics are not yet enabled on a page, no analytics script is loaded at all.
Advertising
This site is supported by advertising provided by Google AdSense. When ads are enabled, Google and its partners may use cookies to serve ads based on your prior visits to this and other websites. You can opt out of personalised advertising at Google Ads Settings, and learn more in Google's partner-sites policy. Ad slots never appear inside tools and never collect tool input.
If you email us, we receive your address and message and use them only to reply. We do not run a mailing list.
Changes
If this policy changes, the updated version will be posted on this page with a new date. Questions about this policy: contact us.