Privacy without profiling
Kairnox does not build marketing profiles. The data we retain is used to operate keys, protect the service, and maintain aggregated usage counters.
1. No advertising analytics
The website does not include Google Analytics, advertising pixels, or marketing tracking tools. We do not sell data or use your browsing activity to build an advertising profile.
2. Anonymous counters
We retain only aggregated daily totals: flows started, first steps completed, flows completed, and keys generated. These counters contain no Roblox ID, key, or identifier that can be used to identify a user.
3. Data required for a key
During a flow, Kairnox stores a random identifier, step status, and expiration dates. The key is stored in encrypted form and as a non-reversible fingerprint so it can be verified.
On the first valid use in the launcher, the submitted Roblox ID is linked to the key. This prevents the same key from being used by another account. We do not retrieve the Roblox username, inventory, friends, or account content.
4. Cookies
During the public flow, temporary cookies may be used to secure the return from a verification step and restore an unfinished flow in the same browser. Page scripts cannot access them. No advertising or audience-measurement cookies are installed.
5. Abuse prevention and recovery
The application does not store your raw IP address or User-Agent in its database. A non-reversible cryptographic fingerprint of the IP address is used temporarily to limit abuse and, together with the browser’s temporary identifier, restore an unfinished flow. A checkpoint becomes unusable after six hours without progress and its data is removed during the next automatic cleanup. The hosting provider, reverse proxy, or verification-step provider may still create its own technical logs according to its configuration and privacy policy.
6. External verification services
When you choose a verification provider, you temporarily leave Kairnox. That provider processes your visit under its own terms. Kairnox receives only the technical proof required to accept or reject the step.
7. Retention
Expired flows, expired or revoked keys, and temporary technical limits are deleted automatically. Anonymous daily counters may be retained to monitor the overall operation of the service.
8. Security
Keys and technical data required by the service are protected by access controls. We limit collection to what is needed to operate the service, validate keys, and prevent abuse.
Do you accept these terms?
You can now start the key generation flow.