Quick answer
Questions to ask before using any online tool with photos, PDFs, checksums, links, or other private files.
Use the related browser-only tool after reading the safety notes, then verify the output before sharing.
Check the privacy model
Look for clear wording that explains whether files are processed locally or uploaded to a server. Vague promises such as “secure” or “private” are less useful than specific workflow details.
If the tool uses cloud processing, look for retention rules, deletion timing, access controls, logging practices, and contact information.
Check the task risk
A public product image is lower risk than a passport scan, legal document, medical record, school file, or private family photo. The more sensitive the file, the more careful your workflow should be.
Some tasks are safe for simple local tools, while others require specialist software, legal review, or organization-approved systems.
Check output accuracy
Always open the output file before sharing it. Check page order, image quality, dimensions, metadata status, or checksum value depending on the task.
Do not assume a success message is enough. A useful tool should explain what happened and what still needs your review.
Check what not to send
Do not send private originals, filenames, metadata values, hashes, GPS coordinates, personal URLs, access tokens, or screenshots with sensitive information to support unless there is a verified and appropriate process.
For bug reports, describe the problem using non-private details: browser, device, approximate file type, approximate size, and the error message.
FAQ
Is local processing always better?
It is often better for simple privacy tasks, but some workflows require specialist tools.
What is the biggest mistake?
Uploading sensitive originals to a tool without understanding where the file goes or how long it is retained.
Should I keep originals?
Yes. Keep originals private until you have verified the cleaned or converted output.