Skip to content

Privacy

chaython edited this page Nov 15, 2026 · 2 revisions

Privacy and local data

WMT is designed to keep application state on your Windows device. The project's published privacy policy is the authoritative source. This page summarizes the practical data flows for users and explains what to check before sharing logs or removing data.

Short version

  • WMT does not operate telemetry servers or send usage analytics to maintainer-controlled servers.
  • WMT stores settings, caches, backups, reports, and optional provider credentials locally.
  • Network requests happen only when a feature needs an external service: update checks, package searches, installs, game-library metadata, community cleaner rules, and similar.
  • Those services receive requests under their own privacy policies.
  • Logs, reports, and backups can contain personal and network identifiers. Redact them before sharing.
  • Removing the data folder removes most WMT state, but provider credentials and caches may also live in your Windows profile.

Provider settings with per-provider toggles

Provider settings. Providers can be enabled or disabled individually, which limits which external services WMT contacts.

Telemetry and project services

The published policy states that WMT:

  • Does not operate telemetry servers.
  • Does not collect usage analytics.
  • Does not run background tracking.
  • Does not automatically transmit personal data to servers owned or controlled by the WMT maintainers.

WMT is distributed through GitHub. GitHub records standard traffic metrics for repository visits, release downloads, and API requests under the GitHub Privacy Statement. Those metrics are aggregated by GitHub and are not a WMT telemetry system.

WMT may also contact GitHub-hosted metadata or release endpoints when a feature needs them, such as release download statistics or provider downloads.

What is stored locally

Most WMT state lives in a data folder next to the executable or WMT-GUI.ps1. The published policy also describes caches and authentication data in Windows user-profile locations such as %APPDATA% and %LOCALAPPDATA%. The exact paths depend on the WMT version, launch method, and providers used.

Data Examples Sensitivity
Settings settings.json, settings.json.bak Paths, provider choices, custom commands, ignore lists
Crash and activity data last-crash.txt, in-memory activity log Usernames, paths, exception text, recent operations
Backups RegistryBackups\, hosts_backups\, firewall_rules_*.wfw, driver exports Registry values, network configuration, installed drivers
Reports SystemReports_*, Installed_Drivers.txt, Driver_Store_Packages.csv, MyDevice_*.txt, DiskUsage_*.txt Computer name, username, IP/MAC addresses, device IDs, file paths
Provider logs package-install-logs\ Package IDs, installer output, paths, errors
Library caches steam_library.json, legendary_library.json, gog_library.json, launcher files Owned-game metadata and install paths
Cleaner caches winapp2.ini, winapp3.ini, cleanerml_cache.json, refresh status files Community rule definitions and timestamps
Compact state ProgramData\WindowsMaintenanceTool\compact-tracker.json, worker script, logs Tracked paths, compression state, scheduled-run output
Credentials data\gogdl\auth.json, Legendary's user.json Account access tokens; protect as passwords

See Settings and Data for the full file list.

Optional authentication data

WMT does not store Windows passwords. It can use optional third-party tools that keep their own authentication state:

  • Legendary / Epic: %USERPROFILE%\.config\legendary\user.json, or the path in LEGENDARY_CONFIG_PATH. WMT's managed executable lives in data\legendary, but the login token belongs to Legendary's config.
  • GOGDL / GOG: data\gogdl\auth.json. WMT can copy a valid auth.json from Heroic Games Launcher.
  • Steam: WMT reads Steam's installation and appmanifest_*.acf files; Steam manages its own login.
  • Package managers: WinGet, Chocolatey, Scoop, npm, pip, Cargo, RubyGems, Composer, and .NET SDK keep their own configuration and credential stores outside WMT's data folder.

The policy states that locally stored tokens are not uploaded to developer-controlled servers. When you use an authenticated provider, that provider receives account and service requests directly under its own terms.

When WMT contacts the network

Network access is feature-dependent. Common cases:

Feature Likely endpoint or service What is sent
Update scan and package search WinGet/Microsoft Store, Chocolatey, Scoop, npm, pip, Cargo, RubyGems, Composer, .NET SDK Package queries, IDs, versions, and normal request metadata
Windows Update Microsoft Update servers Update search and download requests
Software Catalog Provider registries and metadata sources Search terms and package identifiers
Game Library Steam, Epic/Legendary, GOG/GOGDL services Account requests, library queries, download metadata
Advanced Cleanup Community rule sources Rule-list download requests
Release statistics GitHub API Repository/release requests
MAS Activation get.activated.win A request for the activation script; the script then runs locally
Provider installation Provider release hosts Downloads of provider executables

WMT does not proxy these requests through a maintainer-controlled service. Each provider's own privacy policy applies. Offline or local features can continue to work without internet access, but update checks, downloads, metadata, and sign-in-dependent features cannot.

Third-party privacy policies

The published policy lists examples and links, including:

Review the current policy for the provider you use. Links and terms can change.

Reduce network activity

  • Disable providers you do not use in Updates > Providers.
  • Turn off Update Scans if you do not want automatic or tray-triggered scans.
  • Turn off Bg Jobs to stop background refreshes, library cache building, and automatic cleaning.
  • Use local/offline features such as cleanup preview, registry backup/restore, driver inventory, and system reports without signing in to game providers.
  • Do not run MAS Activation unless you intend to contact its endpoint and run its script.
  • Use Skip Downloads / Cache Only cleaner options when you want to rely on cached rules.

Disabling these features does not make WMT invisible to services you explicitly contact. It only stops WMT from initiating those requests on its own schedule.

Logs, reports, and screenshots

Before sharing anything, assume it contains:

  • Computer name and username
  • Windows edition, build, and installed updates
  • IP addresses, MAC addresses, DNS servers, and adapter names
  • Installed software, package IDs, and versions
  • File paths, drive letters, and folder names
  • Driver names, versions, and hardware IDs
  • Provider account names or library contents
  • Registry keys and values

Redact or crop screenshots. Replace usernames with user, computer names with PC, and IP addresses with documentation ranges such as 192.0.2.x. Remove tokens, cookies, API keys, and auth.json/user.json contents entirely.

Data retention and removal

Remove WMT settings only

  1. Exit WMT, including the tray icon.
  2. Rename settings.json to settings.json.old.
  3. Optionally remove settings.json.bak.
  4. Start WMT. Defaults are recreated.

This keeps backups, reports, logs, and provider files.

Remove most WMT data

  1. Exit WMT and stop any WMT-related scheduled task or background process.
  2. Back up anything you want to keep.
  3. Rename or delete the data folder.
  4. Start WMT and let it recreate the folder.

This removes registry backups, hosts backups, driver exports, firewall exports, logs, library caches, and GOGDL authentication. It does not necessarily remove Legendary's user.json in your profile or provider configuration outside data.

Remove profile data

Check WMT-specific folders under %APPDATA% and %LOCALAPPDATA%, plus:

  • %USERPROFILE%\.config\legendary\
  • %APPDATA%\heroic\gog_store\auth.json (if WMT copied from Heroic)
  • Provider-specific config and cache folders

Remove only folders you have positively identified. Do not delete the entire %APPDATA% or %LOCALAPPDATA% directory.

Uninstall

WinGet's uninstall removes the package-managed application, but it may not remove a data folder created beside a portable copy. After uninstalling:

  • Check the old install folder for data.
  • Remove the WindowsMaintenanceTool startup task if Start with Windows was enabled.
  • Remove the compact scheduled task if you used Compact Compression.
  • Remove shortcuts you created manually.
  • Review provider credential folders separately.

Secure deletion caveat

Deleting a file does not guarantee that its contents are unrecoverable, especially on SSDs with wear leveling, on file systems with snapshots, or in cloud-synced folders. For sensitive data, use an appropriate sanitization method or full-disk encryption and key destruction. WMT's cleaner is not a secure-erase tool.

Policy updates and contact

The published policy may be updated to reflect functional or compliance changes. The effective date at the top of the policy is authoritative.

For privacy questions, use the official project repository or issue tracker. Do not include passwords, API keys, session tokens, or credential files in an issue.

Related pages

Clone this wiki locally