Fairness & proof

We take fairness seriously. Before a draw, we freeze the exact list of ticket IDs and publish a cryptographic fingerprint (a SHA-256 hash) of that list. This fingerprint is shown on the site as listHash.

When the draw happens, we generate a secure 32-bit random number (rand32) on the server and use it to pick a winner by index in the frozen list of tickets.

Verification does not require any personal data. The public values (listHash, rand32, ticket count) are sufficient to check the integrity of the process.

How the winner is picked

1. We sort all tickets by ticket number and take the list of their internal IDs.
2. We compute SHA-256 over that ticket ID list and publish it as listHash.
3. At draw time, we generate a random 32-bit integer (rand32).
4. The winning index is rand32 % N, where N is the number of tickets.

Verify it yourself

High-level steps:

• Use the published listHash and rand32 from the result page. These are public, non-identifying values.
• We can provide a deterministic simulation tool that replays the draw using only the ticket count (N),listHash, and rand32 to show the winning index calculation (rand32 % N)—no personal data required.
• Optionally, for deeper audits, we can share a salted and anonymized ticket ID list or a zero-knowledge style proof that the frozen list matches the hash, without exposing entrant identities.

This approach avoids sharing any personal information (GDPR-friendly) while still letting anyone verify the draw logic.