How the keys are made
Every character is picked with crypto.getRandomValues, the browser's cryptographically secure random number generator, and not Math.random. The tool throws away the few random values that would make some characters likelier than others, so each character in the alphabet has the same chance. All of it runs in this page. Nothing you generate is sent anywhere.
The Clavem style is the format Clavem uses for the keys it issues: 25 characters in five groups of five, from the Crockford base32 alphabet, which leaves out I, L, O and U. A key read aloud or retyped from a printout is much harder to get wrong that way.
What the entropy figure means
Entropy in bits counts how many equally likely keys exist: each bit doubles the number. A Clavem-style key has 25 characters from a 32-character alphabet, so 25 × 5 = 125 bits. A UUID v4 has 122 random bits, because 6 of its 128 bits are fixed version and variant markers.
What matters for security is the number of keys you have issued, not only the size of the space. If an attacker needs to hit any one valid key, the average work is the space divided by the number of issued keys. An 8-character key from a 32-character alphabet has 40 bits, about 1.1 trillion keys. With a million keys issued and 1,000 guesses a second, an attacker finds one in about 18 minutes. At 125 bits the same attack takes longer than the age of the universe.
Using the keys
These are random strings, not licenses. A key only works once your system knows it: store it against an order, check it on a server and decide how many devices may use it. Clavem does that when a customer pays through Stripe, and you canimport keys from another system. To test a pasted list for mistakes and duplicates, use thelicense key format checker.
Questions
Are the keys sent to a server?
No. The keys are made by code running in your browser and are never sent anywhere or stored. Reloading the page discards them.
Is a random key enough to stop piracy?
No. A key only helps if a server checks it, limits how many devices use it and can revoke it. Anyone can copy a key. For checks without a network, use a signed token instead of a key pattern.
How long should a license key be?
Long enough that guessing is hopeless at the rate an attacker can try. The attack estimate above shows the average time for your format, number of issued keys and guess rate. The more keys you have issued, the shorter the time, because any one of them is a hit.
Will a key made here work in Clavem?
Only if you import it. Clavem creates its own keys when a customer pays through Stripe. Keys from other systems can be imported and then match as written.
See how Clavem checks keys in the API reference, or verify tokens offline with theoffline verification guide. More tools are listed under free tools.