Privacy and data handling

---

In short

• All app data is stored locally — in the ErrantLauncher folder next to the executable.
• No telemetry. The app does not send statistics, usage reports or diagnostics to the developer.
• The app itself makes no outbound network requests — not for update checks, analytics or activation.
• The network is only used when you open it yourself: launching a link card, a custom command, or a program with its own internet access.
• No account, registration or internet connection is required.

What data the app creates

Data	Where it is stored	Contents
Sections, categories, cards	ErrantLauncher\sections\*.json	Names, paths to your files and programs, commands, links, launch settings, favorite marks, group composition
Settings	ErrantLauncher\settings.json	Theme, accent color, language, startup section, card styles, tray behavior
State	ErrantLauncher\state.json	Window position and state, last opened section, launch counters
Icons	ErrantLauncher\custom-icons\	Icon files you added and icons extracted from programs
Logs	ErrantLauncher\logs\	Local diagnostic logs app.log and bootstrap.log — technical messages about the app's operation and errors
Service backups	ErrantLauncher\.backup\, .mass-import-backups\	Automatic backups of data files

Everything listed stays on your computer or your drive. The app does not write to the Windows registry or the user profile.

What is sent to the developer

Nothing. The app has no telemetry, analytics, automatic error reports, online update checks or statistics collection.

The developer only receives what you voluntarily send yourself when contacting support — for example, the text of a message describing the problem or an attached log. What is useful to attach and what not to send: Support and bug reports.

Network requests

The app itself

The app code contains no network calls: Errant Launcher does not contact the developer's servers, does not check for updates and does not download data from the internet. The only network-related action is opening addresses in your browser at your command:

• URL / URI card types;
• links in the "About" window (website, documentation, bug report page, GitHub releases, project support).

Opening a link is performed by the operating system and your browser — further interaction with the site follows their rules, not the launcher's.

Through user cards

Keep in mind that cards launch your programs and commands:

• a launched program may access the internet under its own rules;
• command cards execute what you wrote in them — including network commands;
• mass import can scan network paths (UNC) if you enable the corresponding filter — the read is performed from your network resources at your choice.

So "no telemetry" does not mean "no network activity at all": network activity is created by the programs and commands you launch, not by the launcher itself.

Logs

Local logs are kept in ErrantLauncher\logs\. They may contain technical details: error messages, paths to data files and configuration file names. Logs are never sent anywhere — but before attaching them to a bug report, it makes sense to review the file and remove details you do not want to disclose (for example, paths containing folder names).

Imported files

The "Import configuration" feature warns: the imported file is not checked by the launcher for safety and may contain commands and links. Import configuration files only from sources you trust.

Deleting data

• Deleting the ErrantLauncher folder erases all local app data — no copies exist on third-party servers.
• The "Delete all data" function in settings does the same from inside the app (after two confirmations).
• Temporary unpacked files in %TEMP%\.net\ErrantLauncher contain only the app's libraries and can be deleted manually while the app is closed.