Privacy
NP Tools privacy model
NP Tools is designed around local browser processing. Core utility input is handled on the device whenever the task can be completed with browser APIs, reducing routine exposure of working data to an application server.
Updated: 2026-07-21
Local processing
Text, tables, images, keys, campaign materials, and other working input are processed by the active tool in the browser for core transformations. Do not assume that local processing makes unsafe input harmless; secrets and personal data still require appropriate handling on the device.
Browser storage and offline assets
The interface may use browser storage for preferences, recent or favorite tools, saved local profiles, and in-progress work supported by a specific tool. The PWA service worker may cache application assets and previously visited routes for offline use. Clearing site data removes browser-managed state.
Network boundaries
Public pages, application code, updates, and static assets are delivered over the network. External links leave NP Tools. If a utility requires a live endpoint or another external request, that boundary must be visible in the tool interface; local-first is not a claim that the entire website works without network delivery.