ToolNest · Published 2026-09-24 · Updated 2026-09-24
What “runs in your browser” means on ToolNest
Privacy pages fail when they over-claim. This guide matches the current software: most tools are local; a few extras are not.
Local processing
PDF merge, image compression, hashing, QR generation, and similar tools read your input in JavaScript and produce a download or an on-page result. ToolNest does not host a file-processing API for those actions.
Libraries from CDNs
Some tools load open-source libraries (and, for background removal, an optional model) from public CDNs. That is a download into your browser, not an upload of your document to ToolNest. If a CDN is blocked, the tool may fall back or fail — the UI says so.
Things that do leave the device
The contact form posts name, email, subject, and message to Formspree so we can reply. If advertising is enabled later, Google AdSense may use cookies as described in the privacy policy. Optional analytics, if configured, is for aggregate usage — not the contents of your PDFs.
localStorage
Theme preference, recent tools, and the notepad use localStorage. Clearing site data clears them. They are not an account.
Questions
Is ToolNest “100% private” or “guaranteed secure”?+
Those phrases are too broad. The accurate claim is: tool inputs are processed in the browser, with the exceptions documented in the privacy policy.