# LiveryLab Trust and Safety Notes

LiveryLab is a local Windows tool for Assetto Corsa EVO livery workflows. This
document explains what the release build is expected to do and what it does not
do.

## Local-Only App

- LiveryLab runs locally on your Windows machine.
- The app does not require an account or login.
- The app does not include telemetry, analytics, or automatic update checks.
- The app does not intentionally upload your files.

## File Access

LiveryLab reads Assetto Corsa EVO content and local LiveryLab project files so it
can inspect cars, create liveries, preview assets, manage reusable assets, and
package exports.

LiveryLab writes files only when you trigger actions such as:

- creating or editing a local livery,
- activating or updating a livery in Assetto Corsa EVO,
- creating, importing, exporting, or updating Driver Profiles,
- creating, importing, exporting, or updating tyre brand assets,
- creating, importing, exporting, or updating numberplate templates,
- creating, importing, exporting, or applying Custom Grid presets,
- exporting or importing Backup & Transfer bundles,
- importing or exporting portable packages,
- converting textures, meshes, UVs, or inspection outputs,
- syncing previews, snapshots, or thumbnails,
- moving a livery to the LiveryLab trash.

## Game Folder Writes

Game-folder writes use a preflight check before changing files. The app checks
that the selected Assetto Corsa EVO root exists, is writable, and that planned
write targets are inside the selected game root.

Actions that may write into the Assetto Corsa EVO game folder include Activate
in Game, Update in Game, Remove from Game, package extraction, Custom Grid
bridge installation or cleanup, game thumbnail synchronization, and other
workflows that explicitly confirm a game write.

Where practical, existing game files are backed up before being overwritten.
Destructive app actions use LiveryLab-specific trash, backup, or quarantine
locations instead of silently deleting user data.

## Installation And Local Data

Installer releases install LiveryLab into the selected installation directory.
By default, this is:

```text
%LOCALAPPDATA%\Programs\LiveryLab
```

Portable ZIP releases run from the folder where the complete ZIP package was
extracted.

Keep the app folder together. Do not move only `LiveryLab.exe` out of the
folder. The app depends on the bundled runtime and local data folders next to
the executable.

The app folder contains:

- `LiveryLab.exe`: app executable.
- `_internal`: bundled Python runtime, backend modules, web UI files and
  required libraries.
- `tools`: helper tools used by LiveryLab, including texture conversion tools.
- `LiveryProjects`: editable project workspace for livery and related source
  files.
- `LiveryLibrary`: local ready-to-activate library managed by LiveryLab.
- `LiveryPackageExport`: output folder for portable ZIP packages, Backup &
  Transfer bundles and exports.
- `UserData`: local app settings and WebView runtime data for this
  installation.

The final public package excludes local settings, user projects, custom
liveries, driver profiles, tyre brands, numberplates, and backups.

## Updates And Uninstall

Installer updates replace app files such as `LiveryLab.exe`, `_internal`,
`tools`, `VERSION`, `CHANGELOG.txt`, `README.txt`, and `TRUST.txt`.

Your `LiveryProjects`, `LiveryLibrary`, `LiveryPackageExport`, and `UserData`
folders are kept during installer updates. Setup does not modify Assetto Corsa
EVO game files.

The uninstaller removes installed app files and shortcuts. During interactive
uninstall, it can also remove LiveryLab library and app data if you explicitly
choose that option. Editable projects and exported packages are kept.

## Checksums

Official release packages include `SHA256SUMS.txt` with checksums for the
complete clean package. Use this file to verify that important files were not
changed after the release was built.

## Code Signing

Official LiveryLab release files are code-signed.

Code signing helps Windows verify that the executable comes from the expected
publisher and that it has not been modified after signing. However, Windows
SmartScreen, Microsoft Defender, or other antivirus tools may still show warnings
for newly released apps, newly downloaded files, or files with low reputation.

Always download LiveryLab from the official source. When running the installer
or portable EXE, check that Windows shows the expected publisher information.
Do not run modified or re-uploaded copies from unknown sources.

## Recommended Use

- Use releases from the official project source.
- Keep the complete LiveryLab folder together.
- Keep backups of important liveries, projects, and exported packages.
- Review confirmation dialogs before allowing LiveryLab to write into the
  Assetto Corsa EVO game folder.
- Do not manually delete or rename app-managed folders while LiveryLab is
  running.
