Know where your files are processed, how downloads are protected, and what to check before sharing.
Privacy by design
Remove hidden details with browser-first tools where supported. When a file needs server processing, understand the upload, download and expiry steps before you continue.
Local cleaning where supported
Temporary server results
Protected account access
Supported image, PDF and document tools clean locally selected files inside your browser. The file contents do not need to be uploaded for that local cleaning step. Processing libraries load only when needed, and browser workers handle supported cleaning tasks so the page stays responsive.
Some image formats require server conversion. Video, audio and RAW processing also use server tools. Check the processing information beside the tool before choosing a sensitive file.
Server tools receive the file you choose, check supported file types and apply upload and processing limits. Heavy jobs run through a bounded queue rather than allowing unlimited simultaneous processing.
For a successful server job, the original input is removed after processing. Completed results are scheduled to expire after 15 minutes; periodic cleanup removes expired job files. Download your result before it expires. Cleanup timing depends on the processing service being operational.
Account job lookups are tied to the requesting user. A secret download link is a separate way to access a completed result until it expires. Anyone with that link may be able to download the file, so share it only with the intended recipient.
Choosing an upload-based API or a sharing feature can send a file to the server even if the file was originally cleaned in the browser. Local cleaning and server sharing are separate actions.
Passwords are stored as salted password hashes rather than readable passwords. Session cookies are HttpOnly and use SameSite protection; production session cookies also use the Secure attribute. Sensitive actions apply server-side authorization checks.
Two-step verification is available for back-office accounts. Keep your own password unique and avoid signing in on devices you do not trust. Account and usage records are separate from the temporary files used for processing.
API and MCP requests use server-side authentication, permissions and usage limits. Keep API keys in a trusted application or server, and treat them like passwords. Never place a private API key in publicly accessible browser code.
Use the API documentation to understand authentication, supported formats and request limits before connecting an integration. Revoke credentials you no longer use from your account.
Metadata removal reduces hidden file details; it does not hide information visible in the file itself. Faces, signatures, addresses, document text and visible watermarks can still identify a person or place.
Review the cleaned file and any remaining-field report. Keep a backup of your original, check the result in a metadata viewer, and inspect the visible content before publishing. Before sending sensitive files to a server tool, check that your connection uses HTTPS.
No. Supported browser cleaning can keep a locally selected file on your device. Video, audio, RAW, formats needing server conversion, and upload-based API or sharing workflows send files to the server. Read the tool's processing information before continuing.
Completed server jobs are scheduled to expire after 15 minutes. A periodic cleanup task removes expired job files. Save your cleaned file before expiry; service interruptions can affect cleanup timing.
No. The visible contents may still contain identifying information, and a format may retain fields that cannot be removed safely. Review the result and remaining-field report before sharing.
Use the contact page with a short description and the affected page or feature. Do not include passwords, API keys, live secret download links or confidential files in your initial message.
Need more information?
Read our privacy policy or report a security concern.
Updated