Processing happens entirely on your own device. Nothing is uploaded.
“Your content never leaves this device.”
Security and privacy, explained in plain language.
“For this tool, your file is processed within your browser and is not transmitted to our server.” The kind of sentence you'll find on every tool page here, not just in a policy you never read.
How every tool is classified
Local processing is used whenever possible. Some workloads may optionally use secure external processing.
“You will be asked before anything is uploaded.”
The function requires temporary server-side processing, encrypted and automatically deleted.
“Review the Data Handling information before continuing.”
AI is used only where it materially improves the task, and always disclosed upfront.
“You'll always know which provider processes your data.”
Data retention
If we don't need to store something, we don't. Device Only tools store nothing on our servers, ever. When a Secure Processing tool must upload a file, it is automatically deleted shortly after your task completes, and you can delete it yourself at any time with Clear Session.
Third parties
Most tools involve no third party at all. Where a tool is AI Assisted, the exact provider, what is sent to them, and whether it's used for model training are stated on that tool's page, never buried in a policy.
Security approach
Any file that must reach our servers is encrypted in transit and at rest, isolated per job, and accessible to nothing except the process handling your task. Device Only pages are served with a Content Security Policy that stops the browser from sending data to any other site.
Compliance roadmap
These tools are designed with ISO/IEC 27001 security-management principles and OWASP application-security practices in mind from the ground up. We do not claim certification until it has actually been completed.