Local processing
Most tools run in browser APIs, Web Workers, Canvas, Web Crypto, or local libraries on your device.
Your file.
Your device.
End of story.
When we say “Runs locally,” we mean the file processing happens inside your browser—not on our servers.
No file storage
When a tool is marked local, its files never reach Easy2Find servers. There is nothing for us to retain.
Automatic cleanup
Temporary object URLs and worker resources are released after processing or when the page closes.
Cloud tools are labeled
If a future feature needs a remote provider, you will see that label before selecting or sending a file.
What happens to a local file?
01 Selected from your device02 Read into browser memory03 Processed by browser code04 Downloaded by you05 Temporary memory released
Honest boundaries.
Site hosting, static assets, consent-aware analytics, and advertisements may use network requests. File contents, passwords, generated passwords, hashes, and pasted tool data are excluded from product analytics. A future cloud tool will have a separate, explicit disclosure before processing.