Images stay on the device
Resize, compression, and conversion run in the browser. Files are not uploaded to a remote processing queue.
Privacy policy
The privacy model starts with one constraint: image files stay local.
PixelProof is designed around browser-only image processing. This page explains what that means in practice, what limited product data may still exist, and where direct communication sits outside the editor flow.
No uploadBrowser-onlyLocal stateLimited analytics
DATA
What this page is really saying
Analytics do not include image content
Basic aggregated usage data may be collected to understand product usage, but it does not include the files you edit.
Manual contact is separate
If you email feedback directly, that email is handled like a normal message. It is separate from the editor workflow.
Scope
How privacy works across the product surface.
Last updated July 27, 2026.
Processing
No-upload image work
When you resize, compress, or convert images, the work is performed inside the browser using Web APIs such as Canvas, File, Blob, and Web Workers. The product does not receive your files or keep copies of them on a server.
Analytics
Limited product usage signals
The site may collect high-level usage data such as pageviews or route usage to understand which tools and presets are useful. That data is intended to improve the product surface, not to inspect the content of edited files.
Advertising
No advertising code is currently loaded
PixelProof does not currently load advertising code. The site publishes an ads.txt seller authorization file, but it does not load Google AdSense ad code or personalized advertising cookies. If advertising is enabled later, this policy will be updated before activation.
Storage
Browser preferences and temporary file handoff
Preferences and saved setups can remain in local browser storage. When you continue with a file in another tool, its contents are temporarily saved in this browser’s IndexedDB. The receiving tool clears that copy after loading it. A handoff older than ten minutes is rejected and deleted the next time it is accessed; closing the tab does not schedule deletion. You can remove remaining local data by clearing this site’s browser storage. These files are not sent to a server.
Third parties
Infrastructure still serves the app shell
The site still needs to deliver its code, fonts, and static assets over the network so the interface can load. That network activity is for the application itself, not for transmitting the image pixels you process locally.
FAQ
In practice
A few practical boundaries matter more than the legal language.
The product is intentionally simple. The main distinction is between local editing, which stays in the browser, and direct communication, which behaves like normal web or email communication.
01
If you are working with sensitive files, you can complete the edit flow without sending the image to a server because the editor is built for local execution.
02
If you share feedback by email, the email itself may contain whatever details you send voluntarily. That communication is outside the local editor flow.
03
This policy describes the product's current behavior and may be updated if the app architecture changes in the future.
NEXT
Related pages
Privacy, security, and terms are meant to read together.
Privacy explains what data the product handles. Security explains the local-first architecture. Terms explain the responsibilities around using the tool.