Skip to main content
NeatUtility
Local Security Architecture

Privacy by Default

NeatUtility is engineered so that pasted input and generated output are processed locally in your browser and are not uploaded by the utilities. The browser still requests site assets from the host; clipboard, downloads, and extensions are separate boundaries you control.

Zero Backend Processing

NeatUtility is hosted as static HTML, CSS, and JavaScript. Every utility runs locally inside your browser using isolated Web Workers. There is no backend server receiving your requests.

No Telemetry on Data

We never inspect, record, or track your pasted inputs, formatted outputs, search queries, or filenames. Application telemetry is currently disabled entirely; your code and credentials stay in your browser session.

Memory-First Handoffs

When using “Send To” to pipe data between utilities, payloads default to in-memory handling and never enter URLs or permanent storage. Sensitive payloads (such as JWT tokens or .env files) stay strictly in memory and are discarded when you close or refresh the tab.

Isolated Storage & URL Scope

Only non-sensitive UI preferences (such as light/dark theme preference and starred favorite tool IDs) and local Color Picker saved palettes (namespaced and validated) are persisted in local storage. User text is never saved or placed into URLs. The Color Picker offers an explicit share link limited strictly to normalized 6- or 8-digit hexadecimal color values; it never accepts or includes images, text, or arbitrary parameters.