Privacy Policy
Last updated: 31 July 2026
Modrex is built to respect your privacy. This policy covers both the Modrex desktop app and this website (modrex.net).
Desktop app
Modrex does not collect any data by default. The app includes an optional, opt-in analytics feature:
- Opt-in only. You are asked once on first launch and can change your choice at any time in Settings.
- What is collected if you opt in: anonymous usage events (features used, mods installed, app version, operating system). A random per-install ID is generated locally — it is never linked to your name, email, or any account.
- What is never collected: file paths, the text you type into mod search (only its length), game save data, your account credentials, or your name or email address.
- Processor, and your IP address: analytics events are sent to Google Analytics 4 through a proxy at modrex.net, running on Cloudflare Pages. The proxy reads the IP address your connection arrives from and forwards it to Google in the same request, so that country-level statistics reflect where you are rather than where the proxy is. The proxy does not store it and Modrex keeps no database of it. An IP address can count as personal data in some jurisdictions, so it is disclosed here even though it is used only for approximate location. See Google's Privacy Policy.
If you opt out (or never opt in), the app sends no analytics at all, and no IP address reaches modrex.net or Google from it.
Nexus Mods sign-in (optional)
Modrex can browse and install mods from Nexus Mods. That requires signing in to your Nexus Mods account, which happens in your own browser using Nexus's OAuth flow. Modrex never sees or handles your Nexus Mods password.
- What is stored: the access token and refresh token that Nexus issues, plus the time the access token expires. No password and no profile information is stored.
- Where it is stored: in your operating system's credential store (Windows Credential Manager, or a Secret Service provider such as gnome-keyring or KWallet on Linux). Only the expiry time is written to Modrex's own settings file.
- Where it is sent: only to Nexus Mods, to authorize your own requests to their API. These tokens are never transmitted to modrex.net or to any other server operated by Modrex.
- On Linux with no credential store: if no Secret Service provider is running, Modrex falls back to storing both tokens in plain text in its configuration file (
~/.config/modrex/settings.json), where other users of the same computer may be able to read them. Modrex shows a warning in Settings whenever this is the case. Installing and enabling gnome-keyring or KWallet and restarting Modrex moves the tokens into the credential store. - Removing it: signing out in Settings deletes both tokens from the credential store and from the settings file.
Your use of Nexus Mods is also governed by their own Privacy Policy.
Website (modrex.net)
This website uses Google Analytics 4 with Consent Mode v2. Analytics are denied by default and only enabled if you accept via the cookie banner. We do not use any other tracking, advertising networks, or third-party data brokers.
Data sharing
We do not sell, rent, or trade any data. We do not share data with third parties except as required by the analytics processor described above or by law. Nexus Mods sign-in tokens are never shared with anyone: they stay on your device and go only to Nexus Mods itself.
Changes
We may update this policy at any time. The "Last updated" date above will reflect any changes.