ntug-privacy(7)
Privacy
ntug has no backend, no account system and no analytics. The short version fits in one sentence: the site is a handful of static files, and everything you type stays inside your browser tab.
What runs where
The page loads three kinds of file, all from the same folder: HTML, one stylesheet and one script. After that, every tool is computed by your browser. The regex tester uses the browser’s regular expression engine. The hasher calls the Web Crypto API your browser ships with. The JSON, encoding, epoch, UUID and contrast tools are plain JavaScript with no libraries.
There is no code in ntug that sends data anywhere. It does not use fetch, XMLHttpRequest, WebSockets, beacons, iframes, web fonts, CDNs or tracking pixels. You can save the folder and run it from a disk with the network off, and every tool still works.
What is stored
Almost nothing. Your inputs are never written to storage; they live in the page and disappear when you reload. The one thing ntug remembers is the short list of tools you opened most recently, so the palette can show them first.
| Where | Key | Holds |
|---|---|---|
| localStorage | ntug:recent | Up to three tool names, such as json or epoch |
| Cookies | none | ntug sets no cookies |
| IndexedDB, cache | none | Not used |
If your browser blocks storage, ntug keeps that list in memory for the length of the visit and carries on. The self-check below shows what is stored right now and lets you clear it.
Files and the clipboard
The SHA-256 tool can hash a file you choose. The file is read into memory by the page, hashed, and forgotten. It is not uploaded, copied or listed anywhere. Copy buttons write to the clipboard only when you press them, and ntug never reads the clipboard.
The contact page builds a mailto: link and hands it to your mail app. ntug does not see or send the message; whatever you write travels through your own mail provider and lands in the inbox behind hello@ntug.dev. Do not put secrets in a bug report. A trimmed version of the input that misbehaved is nearly always enough.
Check it yourself
You should not have to take this page’s word for it. Three ways to test the claim:
- Open your browser’s developer tools, switch to the Network panel, reload, and use a few tools. You should see this page’s own files and nothing else.
- Switch off Wi-Fi or enable airplane mode after the page has loaded. Every tool keeps working.
- Read the source. There are five HTML files, one
style.cssand onescript.js, with no minification and no bundler.
Self-check
This panel asks your browser a few questions and shows the answers. It reports what your browser says; it cannot prove anything about the rest of your machine.