Privacy

The short version

Nyx needs to know which machines a licence is running on, and it wants aggregate before/after numbers to tell which tweaks actually work. It does not need to know what you do on your PC, and it is built so that it cannot.

Your account

Sign-in is through Discord. We store your Discord user id, username, display name, avatar hash and — if you granted the email scope — your email address, which is used to send your licence key and nothing else. We never see a password because there isn't one.

Hardware identification

A licence is bound to hardware so that a key is not infinitely shareable. The way that works matters, so here it is in full:

• The client reads four things: your motherboard UUID, a CPU identifier, your system disk's serial number and the MachineGuid Windows generated at install.
• Each one is SHA-256 hashed on your machine before anything is sent. The raw values never leave your PC.
• The server then applies its own keyed HMAC on top of those hashes before storing them. A dump of our database cannot be matched against a known machine, by anyone, including us.
• The four components are stored separately so that replacing one part — a new SSD, a new network card — is recognised as the same machine rather than burning a seat.

Machine details

Alongside the fingerprint we store your Windows build number and edition, CPU model name, core count, RAM size, network adapter description, link type and speed. These decide which tweaks apply to you — the planner skips tweaks that need a newer Windows, more RAM, or a wired connection — and they are what lets us tell whether a tweak is failing on a particular driver. None of them identifies a person.

Measurement data

If you leave the share-results option on, each optimisation run uploads: the game and profile you chose, the tweak ids that applied and failed, and the before/after latency statistics. Those rows carry no account or licence reference — not anonymised later, but stored with no link in the first place, because the table has no column for one.

We use them for exactly two things: the aggregate numbers on the homepage, and deciding which tweaks stay in the catalog. A tweak whose runs show no median improvement gets demoted or removed however good the theory sounds. Turning the option off costs you nothing.

Route traces

A route trace records the hops between you and a game server, which includes intermediate router addresses. We store these to spot bad routes affecting many users. The first hop of a home trace is your own router's private address (192.168.x.x or similar), which is not routable and identifies nothing outside your house. We do not store your public IP address alongside them.

Snapshots

Your undo records live on your own disk, under %LOCALAPPDATA%\Nyx\snapshots. A copy is uploaded only if you tick the box, and only so support can talk you through a restore if a reboot goes badly. We keep the five most recent and delete the rest.

What we never collect

• Your browsing history, DNS queries or the hostnames you resolve
• Any game file, game memory, chat, or anything you type
• A list of your installed programs
• Keystrokes, screenshots or clipboard contents
• Your public IP address paired with your telemetry

Payments

Stripe handles checkout. Card details go to Stripe and never touch our servers; we receive a customer id, a subscription id, an amount and a status. Refunds and cancellations are managed through Stripe's own portal.

Deleting your data

Ask in Discord or by email and we will delete your account, your licences and your uploaded snapshots. Aggregate measurement rows cannot be deleted on request because there is no way to identify which ones were yours — that is the direct consequence of not linking them in the first place, and we think it is the right trade.

Self-hosting

Nyx's server is a normal application you can run yourself. If you point the client at your own instance with NYX_API_URL, none of the above involves us at all.