Privacy¶
Latentry runs on your own computer, and is built to send nothing anywhere you did not choose and to leave as little behind as it can. This page says what goes over the network, and what is kept where, so you can check it against what you expect.
What goes over the network¶
- To your backends, the ones you set up: prompts, settings and source pictures for each run, and the backend's token if it has one. A token is only ever sent to the server it was set up for.
- Downloads you start: installing and building Latentry (npm packages, and the UI's font, which the build fetches once and then serves itself), and, from the Setup page, the engine (uv, Python, PyTorch, diffusers), the models you pick and the WD14 tagger. Two more come from the engine itself, once each: the pose models, on the first run with a pose, and, on the first load of an SDXL model kept as a single file, the pipeline's small config files (scheduler, tokenizer) from Hugging Face. Later loads read them from the cache.
- Nothing else. No telemetry, no update checks, no analytics. The anonymous usage reports of Next.js and Hugging Face are turned off.
Prompt fields and the gallery's search have the browser's spell check and autofill turned off: some browsers check spelling by sending the text to an online service.
The browser only talks to Latentry itself. Latentry listens on 127.0.0.1
unless you set LATENTRY_HOST; see
Other devices and security before opening it to a network.
What is kept, and where¶
| Where | What | When it goes |
|---|---|---|
| The gallery's save folder | Every finished picture, with its prompt and settings inside the file (the LoRAs used, by name and weight); WD14 tags, when you tag a picture there; LoRA hashes only if you turn Write LoRA hashes on | When you delete the files |
.env.local, latentry.settings.json |
Backends, folders and options, and backend tokens (in the settings file when typed on Settings) | When you change or delete them |
latentry.models.json |
Model info you saved: a checkpoint's file name, its link and recommended settings. Only this computer and owner devices can read it, and Latentry never opens the link | When you delete it on the generate page, or delete the file |
.runtime/, models/ |
The engine, the models and the tagger you downloaded | When you delete them, or uninstall |
Hugging Face's cache (~/.cache/huggingface, or HF_HOME) |
The config files of a single-file SDXL model (no weights, no prompts) | When you delete it |
| This browser (localStorage) | The generate form, the prompt shared across backends, saved characters, the chosen backend, and display preferences such as tags under cards, the parts of the generate form you hid and the Settings section you opened last | Kept between visits. Clear the site's data to remove it |
| The engine's memory | A hash of each LoRA file a run asked hashes for (only with Write LoRA hashes on) | When the engine stops |
| Latentry's memory | Runs in progress; each backend's last run, pictures and prompt, for an hour after it ends (a minute for a secret run); thumbnails, and the gallery's index of a folder (date made, size, model, LoRAs, a hash of each prompt, the seed) | The last run after that time; the rest when Latentry stops |
| A ComfyUI backend's computer | Its history of the prompts Latentry ran; the last source and mask uploaded for img2img (input/latentry/<id>-source.png, -mask.png) and the last skeleton for a pose (-pose.png; the reference picture it came from goes to Latentry's engine only); pictures in its temp folder |
History and uploads: right after a secret run; otherwise the next upload replaces them and ComfyUI keeps its history. The temp folder: when ComfyUI restarts |
Not kept anywhere: the gallery's search, order and filters (they last only as long as the page), and pictures from other folders, which are only read.
Secret mode¶
Secret mode keeps what you type out of the browser's storage, blurs the gallery and hides prompts and settings until you choose to show them. Pictures are still saved to the gallery folder.
What Latentry does not do to your files¶
It writes only into its own save folder: new pictures, and tags you ask for. Folders of other tools are read-only. It never deletes, moves or renames a picture. To do that, Show in folder opens the picture in your file manager (only from the computer Latentry runs on).
Reading other tools' pictures¶
From a picture's metadata the gallery reads only what holds generation settings: PNG text, and in JPEG and WebP a few EXIF fields (UserComment, ImageDescription, Make, Model). It never reads location, camera details or embedded thumbnails.