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.

Restoring a damaged model. Every model is installed with the application, and a healthy installation never downloads one. If a model file goes missing or is damaged, Litesum Enhance first rebuilds it from files already on your computer. Only if that is not possible does it download a fresh, verified copy. It does that at start-up for the upscaling models, and through the Repair button in About, which says what it will do before doing it. No image data is involved, and normal enhancement never reaches this code.

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
Crash log	the same folder, crash-<date>.txt, written only if the application stops unexpectedly
Timings of past jobs	the same folder, throughput.json: how long enhancements took on this computer, used for time estimates
Working pictures	the same folder, scratch, only while the application is open
Licence and computer identity	%LOCALAPPDATA%\Litesum, written by the Launcher

While Litesum Enhance is open, the pictures it is working on wait in its own scratch folder, never in a shared temporary folder. They are removed when you close it, or at the next start if it closed unexpectedly. An exported image is written to a temporary file beside it and renamed once it is complete. 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.

To keep some of it, choose from the Metadata list. Keep camera details, remove location keeps camera, lens, exposure, date and copyright and removes GPS coordinates. Keep all metadata keeps everything, including location 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

Nothing is sent anywhere if the application stops unexpectedly. It writes a crash log to your own computer instead (see above). The log holds technical details and no image data. You can choose to send it to us if you would like help.