Keepdesk security
Keepdesk tools were built never to send your files to a server. Local Shield goes one step further: the moment you add a file, the browser itself locks the tab's main outbound channels. Not a promise — a rule the browser enforces.
Converting, compressing and background removal run on your device with code downloaded alongside the page. Keepdesk has no server that receives files; the site only serves static files.
When you choose, drop or paste a file, the page adds one more security policy (CSP). From then on fetch, XHR, WebSocket, sendBeacon and form posts cannot leave our site. Once applied, no script on the page can lift it; it lasts until you reload.
Every attempt the lock stops is counted on the Local Shield badge on the tool screen, with the address it tried to reach. Nothing is blocked out of sight.
Each of our scripts and styles carries a SHA-384 fingerprint (Subresource Integrity). If a file changes by a single byte in transit or on the server, the browser refuses to run it.
Files live only in that tab's memory — never in cookies or browser storage. Text tools with resume, such as the character counter, keep what you type in this browser only. Wipe and start fresh clears that text and the tab's memory in one click. Most image tools redraw the result, so location and camera data do not follow the file.
No. The tools never needed outside connections. Files from our own site, such as the background-removal model, still load.
Not from inside the page once it is on — that is the browser's rule, and why you can rely on it. Reloading starts over.
Current Chrome, Edge, Safari and Firefox all support the security policy (CSP) and code fingerprints (SRI).