Privacy
The short version: local tools never send your image anywhere, and we tell you before anything ever would.
Local tools: your image never leaves your device
Resize, crop, rotate, flip, compress, convert, metadata removal, text overlay and the editor all run entirely inside your browser tab. Your file is read with the File API, decoded by the browser, manipulated on a canvas and re-encoded locally. There is no request that carries the image anywhere. You can verify this yourself: open your browser’s network panel and edit an image — you will see no upload.
This is a structural property, not a promise
The distinction matters. We are not saying we delete your uploads quickly; we are saying there is no upload, so there is nothing on any server to delete, leak or subpoena.
Cloud AI tools
Some planned features — generative fill, object removal, face and style tools, image to video — cannot run in a browser. Those are labelled "Cloud AI" wherever they appear. They are all currently disabled, and none of them process or upload anything in this build. If and when they are enabled, the page will state clearly that your image is sent for processing before you begin, and no cloud tool will ever be presented as local.
Metadata
KaiConvert never reads your photos’ EXIF data for any purpose of its own. The metadata removal tool works by re-encoding the image, which discards metadata as a side effect of writing a fresh file — it does not parse, store or transmit what was there.
Analytics
Analytics are disabled by default and off entirely in local development. When enabled, events record which tool was used and whether an operation succeeded — never image contents, never file names, never dimensions that could identify a specific file. No image data of any kind is included in any event.
Storage
Your images are held in memory for the duration of your session and released when you close the tab or start over. Object URLs are revoked and image bitmaps disposed as soon as they are no longer needed. Nothing is written to persistent storage.
Advertising
No advertising is served in this build. The architecture reserves ad slots that render only when explicitly enabled by configuration, and no ad may obstruct an editing workflow.