Privacy

The short version

Your images never leave your computer. All the enhancement happens on your own graphics card or processor, using AI models installed with the application.

This is not a policy we intend to follow. It is how the software is built: there is no code in the enhancement path that can open a network connection.

What we checked, and how

We watched it. The installed application was driven through a complete workflow — opening a JPEG, enhancing it 4×, exporting it — while every network socket the program held was sampled four times a second.

Stage	Samples	Connections
Starting up	32	0
Opening an image	24	0
Enhancing	100	0
Exporting	40	0

We check the source on every build. An automated audit fails the build if anyone adds an analytics library, a crash reporter, a telemetry client, a cloud AI service, or any network call in the enhancement path. Adding one on purpose requires writing down a reason.

What does use the internet

Signing in. The Litesum Launcher activates your computer and collects a licence roughly weekly. Litesum Enhance itself reads that licence from a local file and makes no requests of its own. No image data is involved.

Repairing a damaged model. If a model file is corrupted, a Repair button appears in About that downloads a fresh copy. It is the only code in the product that fetches a model, it only appears when something is already broken, and it says what it will do before doing it. Normal enhancement never reaches it.

There is no other network activity. No usage reporting, no analytics, no "anonymous statistics", no automatic updates.

Your images and AI training

Your images are not used to train anything. They cannot be — they never leave your computer.

What is stored on your computer

Settings, presets, saved queue	%LOCALAPPDATA%\Litesum\Enhance
Diagnostics log	the same folder — file names and errors, never image contents
Licence and computer identity	%LOCALAPPDATA%\Litesum, written by the Launcher

Temporary files are written beside the file being produced, never in a shared temporary folder, and are removed when the work finishes. A download that fails its integrity check is deleted rather than left behind.

Metadata in your exported images

All metadata is removed by default, including GPS coordinates. That is a deliberate choice: the most common way people accidentally publish their home address is an untouched EXIF block.

Tick Keep EXIF metadata to preserve camera, date and copyright fields — and be aware that includes location data if your camera recorded it.

The colour profile is handled separately and is preserved by default, because a profile is rendering information rather than metadata: stripping it would change how your photograph looks.

Telemetry

There is none. Nothing to switch off.

Crash reports

There is no crash reporter, so nothing is sent anywhere if the application fails. The trade-off is honest: if it crashes, we have nothing to work from beyond what you can tell us. A local-only crash log is planned.

Where the evidence lives

The full audit, including its limits and what is still unverified, is in docs/privacy-audit.md in the source repository.