The boundary is simple: your input stays here.
LocalKit's pages arrive over the internet. Once a tool has loaded, the files and text you give it are processed in your browser—not uploaded to an application server.
No processing server
V1 has no backend that receives files or text for tool operations.
No product storage
Inputs and outputs are not written to an account, database, localStorage, or IndexedDB.
No content analytics
Analytics must not include filenames, contents, metadata, hashes, pasted text, or generated output.
No silent fallback
If your browser cannot perform an operation, the tool stops clearly instead of uploading the input.
What may use the network
The website, fonts, scripts, and static pages must load. Privacy-safe analytics may record a page view, tool start, successful completion, or sanitized error. That telemetry cannot contain your input or result.
Temporary browser memory
During processing, your browser holds the selected file, decoded pixels or text, settings, preview, and generated result. Resetting the tool, replacing the result, navigating away, or closing the tab releases that working state. Download and clipboard actions happen only when you request them.
Browser and device limits
Large image work depends on available memory and browser canvas limits. LocalKit communicates practical limits per tool. It does not claim one universal file-size ceiling, and V1 does not promise offline availability.