This page describes what happens to your data when you use gnext.dev. It is written to be precise rather than reassuring.
What the tools do with your input
All 17 tools run entirely in your browser. Text you type or paste, and files you open, are processed by JavaScript on your device. They are not uploaded, not logged and not stored on any server. When you leave or reload a page, the input is gone. The one exception to “nothing leaves the page” is the Copy button, which writes to your own clipboard at your request.
The JWT decoder’s optional signature check and the hash generator use your browser’s Web Crypto API; secrets and keys you enter stay in the page and are not transmitted.
What the web server sees
Like any website, the server that delivers gnext.dev receives the standard HTTP request for each page and asset: your IP address, the URL requested, the time, your browser’s user-agent string and the referring page if your browser sends one. These may be kept in ordinary server access logs for operational purposes. Tool input is never part of a request, because tools do not make requests.
Analytics and tracking
There are no analytics scripts, advertising trackers, social media embeds, or third-party scripts of any kind on this site. There are no fonts or scripts loaded from other domains. If lightweight, privacy-respecting analytics are ever added, this page will describe exactly what is collected.
Cookies and local storage
The site sets no cookies. It does not currently use browser local storage. If a future feature stores preferences (for example, a favourite tools list), it will do so in your browser only, and this page will say so.
Accounts
There are none. Nothing on the site requires or offers sign-in.
External links
Reference pages link to standards documents and official documentation on other sites. Those sites have their own policies.
Changes
This page is updated whenever the site’s behaviour changes. Last updated 16 September 2026.