What happens to an image you open
When you open, drop or paste an image, your browser reads it from your device into memory, decodes it, and draws it on a canvas. Editing, filtering, resizing, compressing, converting, watermarking and exporting all run in your browser — on the main thread or in Web Workers. The result is created in memory and saved by your browser when you press download.
There is no server component that receives images. The site has no accounts, no database, no cloud storage and no image-processing API.
What is stored on your device
- Preferences in your browser's localStorage: your light/dark theme choice and your last-used export settings (format, quality, scale). They never include image data.
- App files cached by a service worker so the site works offline: pages, scripts, styles and icons from this site. Images you edit are never cached.
- Projects only if you choose Save project. That downloads an .editor-project file to a place you choose; nothing is kept by the site.
Closing the tab discards your working images from memory. When you jump from a tool page to the editor, the file is handed over in memory only.
What is never collected
- No account, name, email or login.
- No cookies set by the site.
- No analytics, advertising or third-party scripts.
- No image content, filenames or metadata sent anywhere.
How this is enforced, not just promised
The site is served with a Content-Security-Policy that limits network connections (connect-src) and image sources to its own origin. Even if a bug tried to send data to another domain, the browser would block it. Workers are same-origin only.
Metadata in exported files
Exports are rendered from pixels and re-encoded by your browser, so EXIF, GPS location, camera details and embedded thumbnails from the original are not carried over. The metadata tool lets you see what an image contains first.
Things that depend on your browser
Your browser and operating system are responsible for decoding formats and for clipboard access. If you enable an extension that reads page content, or use a shared or managed device, those tools may see what is on screen; the site cannot control that.
Optional AI features
The editor is structured so that local AI models (background removal, object removal, upscaling) can be added later behind a provider interface. No such features are enabled today, and none would send images to an external service without saying so clearly.
Reporting a security issue
If you believe you have found a vulnerability, please use the details on the contact page.