Privacy
Keep the boundary visible.
NullKit is designed so supported file processing happens in your browser. Tool routes do not need an account and do not load Google Analytics.
Selected files
When a tool states that processing is local, the selected content is not sent to NullKit or a third-party processing service. Static page code, fonts, models, and processing engines still load from the NullKit website.
Temporary processing data
Selected files, passwords, form values, temporary page renders, intermediate compression attempts, and generated outputs are held only by the current browser workflow. NullKit does not intentionally place this content in website storage or retain it after the tool is reset, the page is closed, or you navigate away. Your browser, operating system, extensions, downloads, swap memory, and backups remain outside NullKit's control.
Optional website analytics
With your permission, NullKit uses Google Analytics on ordinary website pages to understand general traffic and improve the site. Google Analytics stays disabled on tool routes, and analytics events must never contain selected files, tool inputs, generated results, passwords, QR payloads, or document contents. You can change your choice using Analytics settings in the footer.
Anonymous operation and error counts
After a successful file operation or a tool error, a tool may send NullKit only its tool identifier, a completed-file count, or a normalized error category. The counters do not include filenames, raw error messages, stack traces, file contents, sizes, hashes, generated results, account identifiers, or cookies. NullKit keeps aggregate counts by tool, category, and UTC day for private operational reporting.
Minimal website data
Ordinary server and security logs may include request metadata such as time, route, browser user agent, and network address. They do not include the contents of files that are never uploaded.