How HWID licensing works

Every Favade license is bound to the hardware it was first activated on. The mechanism is called HWID locking - Hardware ID - and it's a standard approach for software where redistribution would otherwise be trivial.

What gets fingerprinted

On first activation, the publisher reads a small set of stable hardware identifiers and hashes them together to produce your HWID fingerprint:

CPU identifier - derived from a stable CPUID register, not the brand string.
Primary disk volume - the serial of your boot disk.
Machine GUID - a Windows-assigned identifier set at OS install time.

These three are combined and hashed; the resulting fingerprint is what's stored against your license. The raw values themselves are not transmitted in the clear or stored alongside it.

Why HWID locking

Stops casual sharing. A leaked license key can't be used by someone else because their hardware fingerprint won't match.
Lets us issue resets manually. Real users switch PCs; a manual reset workflow lets us tell legitimate cases apart from a key being passed around.
Keeps the price low. Without HWID locking, every license sold becomes one key shared by many people, which forces the price up to compensate.

Switching PCs

The reset workflow:

Open a ticket in the Discord server explaining you're moving to new hardware.
An admin reviews the request - usually within a few hours during European working time.
If approved, your fingerprint is cleared and the publisher will rebind on next launch.
The reset is logged. Reasonable use is fine; abuse triggers a cooldown.

What counts as "reasonable"

A new build, a fresh OS install, a swapped motherboard, a switch to a different machine - all reasonable. Resetting daily so multiple people can take turns using one license is not, and is the abuse case the cooldown exists to discourage.

What's stored about your hardware

Just the hash. We don't see your CPU model, your disk model, or your Windows GUID - only the derived fingerprint that lets us recognise the same machine on a future login. See the privacy policy for the full picture.