dev101.io

Privacy

The short answer: nothing you type into a dev101.io tool is recorded, logged, sold, or shared. Every transform runs 100% in your browser tab.

The one-paragraph version

dev101.io is a static site. Each tool is a React component that runs in your browser and processes whatever you paste locally. Your inputs — JSON payloads, JWT tokens, regex patterns, text you're diffing, anything — never touch our server, never hit a database, never cross a network boundary we control. There is no account system, no analytics on tool inputs, no third-party script that can see what you type.

What stays in your browser

The following data is processed entirely client-side and is never transmitted anywhere:

  • Tool inputs and outputs. Anything you paste into a text area, upload via a file picker, or generate with a tool lives only in the memory of the current browser tab. Close the tab and it's gone.
  • URL-hash shareable state. Some tools encode their inputs into the URL fragment (the #… portion). By HTTP design, URL fragments are never transmitted to servers — they're handled purely by the browser. That means a share link stays between you and the person you send it to, with no intermediate server logging what you shared.
  • Local preferences. Settings like theme or panel layout may be saved to localStorage. They live in your browser only and are never uploaded.

What we log, and why

To keep the site online we operate a standard web server with a reverse proxy. Its access logs record the minimum needed to diagnose outages and defend against abuse: request paths (e.g. /tools/jwt-decoder), response codes, user-agent strings, and IP addresses. These logs are rotated and purged on a short schedule. They do not contain request bodies, query strings carrying user input, or URL fragments — tool data simply never reaches them.

Analytics

We do not run analytics on the content you enter into any tool. To understand which tools people actually use, we run Google Analytics 4 in Consent Mode v2 with cookieless pings by default. The signal is aggregate page views only — the path you visited (e.g. /tools/jwt-decoder) plus anonymized geo and device class. No tool inputs, no URL hashes, no query strings with user data, and no cookies unless you explicitly allow them via the consent bar.

  • Do Not Track / Global Privacy Control honored. If your browser sends either signal, the analytics script is never loaded — zero requests go to Google.
  • Cookieless by default.The first time you visit we use GA4's cookieless mode, which means no _ga or _ga_*cookie is set. You'll see a small bar at the bottom giving you three choices: keep cookieless, allow cookies for richer analytics, or opt out entirely.
  • Opt-out is permanent. Choosing "Opt out" writes a localStorage flag that prevents GA4 from loading on any future visit — no scripts, no pings, nothing.
  • No PII, no ad signals.IP anonymization is on, Google Signals is off, ad personalization is off. We don't feed the data into an ad network.

Third parties

No third-party service has access to your tool inputs. The site does not embed tracking pixels, customer-support widgets, advertising SDKs, or session-replay tools. Fonts and icons are bundled locally; there are no calls to Google Fonts, Gravatar, or similar remote asset hosts on tool pages. The single exception is the Google Analytics script described above, loaded only when you haven't opted out — and never on tool data itself.

Cookies

By default the site sets no cookies. If you choose "Allow cookies" in the consent bar, GA4 sets its standard first-party _ga and _ga_* cookies (used for session de-duplication across pages). No advertising cookies are ever set. Functional preferences such as theme choice are stored in localStorage, not cookies, and are never transmitted anywhere.

Children's privacy

dev101.io is a developer utility site with no account system. We do not knowingly collect any personal information from anyone, including minors.

Changes to this policy

If this policy changes in a material way — for example, if we ever add an optional sign-in feature — the change will be announced on this page with an updated effective date. Routine edits for clarity will not be called out.

Contact

Questions, corrections, or concerns about this policy can be directed to Max Dutkin. Include the URL of the tool or page you're writing about so the response can be specific.

Want the backstory behind this stance? See the about page.