Safety and privacy
What Nadare does with your account, your data and your network — and what it deliberately does not do.
What Nadare does not do
- No anti-cheat tampering. Nadare does not touch, bypass or disable anti-cheat. It is not a cheat and it changes nothing inside the game.
- No game files shipped. Games are downloaded from the publishers’ own servers. The repository contains the launcher, its icon and its docs — nothing else.
- No credentials shipped or shared. Tokens are minted from your own login and stay on your machine.
- No telemetry, no analytics, no crash reporting. Nothing about you is sent to the Nadare project (PRIVACY.md).
- No packet rewriting or proxy trickery. It talks to the same endpoints the official client does.
Not affiliated, and the terms are theirs
Nadare is community software. It is not affiliated with, endorsed by or supported by any game publisher, and it stands in for the publisher’s launcher when it talks to game servers. Publishers write their own terms and enforce them as they see fit; Nadare does not claim otherwise. Game names, cover art and trademarks belong to their owners and are used only to describe what the software can launch.
Your logins
- Account logins live in the keyring (Secret Service / KWallet), under
nadare-launcher. With no keyring available, Nadare asks you to log in each session instead of writing a token to disk. - Other secrets may use
~/.config/nadare/secrets.jsonwhen no keyring exists. - Logs are masked before they are written, and the support report reads only a bounded tail of each log.
- Scan only the QR code your own Nadare window shows.
What talks to the network
On its own, Nadare contacts the project host at every start for the update check and the notices feed — both can be turned off in Settings. Everything else happens because you asked for it: an install, an update, a sign-in, a launch. The full, per-host table is in PRIVACY.md.
Downloads are verified over HTTPS with a bundled CA list. If your network intercepts
TLS, nothing Nadare does will look different to you — nadare doctor --tls
checks the two known forged-chain test hosts.
The Sandbox (on by default)
Since 0.1.0b22 every game that offers it plays inside the Sandbox: it hides your
home folder, other drives, the session bus, the keyring and the ssh/gpg agents
from the game — the game sees its own folder. It uses bubblewrap, and
the publisher installers Nadare runs are wrapped too. A game whose folder is too
broad to protect (your whole home folder, a whole drive) does not start
unprotected: Nadare stops and asks you to move it. One switch on the game’s page
turns the Sandbox off for that game. doctor reports whether
bubblewrap is available. Details:
docs/SECURE-MODE.md.
Get it from the right place
Only from the official releases page
or our Flatpak repository, flatpak.nadare.app. You can check the
AppImage’s SHA-256 sum and GPG signature (how);
Flatpak checks its repository’s signature by itself. A modified copy could send your
logins somewhere else.
Found a security problem?
Do not open a public issue for a vulnerability. Report it privately, as described in SECURITY.md; the Discord is fine for a quiet ping first.
This page is a summary written for humans. The authoritative documents are ACCOUNT-SAFETY.md, PRIVACY.md and SECURITY.md in the repository. Questions: Discord ↗ · issues ↗.