Public policies
Privacy policy
Connecting a plugin folder includes anonymous recognized-library measurement for aggregate ownership, co-install, compatibility, and recommendation statistics.
Connected library
When you connect your first folder, IndiePlugins creates a stable anonymous library ID and sends recognized catalog plugin IDs, formats, architectures, verified IndiePlugins install events, and controlled package outcomes such as download failed, hash mismatch, or verified. Package outcomes never include a local path or local file hash. This measurement is part of the connected-library feature and continues when saved folders refresh.
What stays local
Folder paths, file hashes, unrecognized filenames, usernames, projects, presets, license information, and detailed installation history remain on your computer. A support report contains app version and counts, not those details.
Reports and takedowns
When you submit a report, IndiePlugins stores the information you provide so the team can investigate, contact you, preserve a review record, and take action. Reports are shared internally with reviewers and may be shared with the affected developer or source operator when needed to verify a claim. Do not send passwords, license keys, private project files, or unnecessary personal information.
Disconnecting
Public catalog browsing does not require a connected library. IndiePlugins Settings can disconnect saved folders, stop future synchronization, and delete the corresponding anonymous library snapshot, install events, and package outcomes.
Other website data
The website also stores collections you publish, sponsored-placement interactions, submitted reports, and ordinary server security logs. Sponsored reporting uses opaque campaign IDs and a short-lived first-party session value for deduplication; developers receive aggregate results, not individual histories.
Effective for the Windows public beta · last updated August 16, 2026.