LOCAL PROCESSING
Local processing, cache, and metadata: how data is actually handled
ImgConvert is a desktop app. Conversion, compression, thumbnails, and queue management happen on the device. Understand local cache, metadata, and access scope to evaluate the privacy boundary correctly.
Key points
- Image conversion, compression, thumbnails, and queue management happen on your device.
- The app accesses only inputs, output locations, and clipboard images you actively choose when needed.
- Source metadata is not preserved by default; local cache and preferences can be cleared.
Image processing stays on the device
ImgConvert does not upload, collect, or send image contents, paths, clipboard contents, or conversion results to us or a third party. Format conversion, compression, thumbnail creation, and queue management run locally.
That does not mean the app never uses the network. Downloading the app or viewing releases needs a network service, but processing an image does not require handing it to a web service.
Access scope follows your actions
The app accesses only input files, output directories, and clipboard images you actively choose when needed. It does not scan photo libraries, disks, or network locations in the background.
You choose the output directory. For important material, using a dedicated output location makes it easier to keep sources and results separate.
Metadata and local cache
Source metadata is not preserved automatically. Only when you explicitly enable preservation does ImgConvert write supported ICC, EXIF, XMP, and related metadata to output files.
Conversion preferences, temporary files, thumbnail cache, and result-cache records may be local. Result-cache records contain hashes and file sizes for verification or reuse, not image bytes or file paths. You can disable reuse and clear local app data or cache records.
Common questions
Are images uploaded to a server?
No. Image conversion, compression, thumbnails, and queue management happen on your device.
Is EXIF preserved by default?
No. Supported metadata is written to output only when you explicitly enable metadata preservation.
Does result cache contain images or paths?
No. Result-cache records contain only hashes and file sizes for verification or reuse, not image bytes or file paths.