Privacy policy

1. What we do not collect

• No account, name, email address or phone number.
• No advertising or cross-site tracking cookies.
• No wallet private keys, seeds or view keys, ever.
• No browsing history beyond the current session.

2. What we store

• Session data: a short display code, the SHA-256 hash of an opaque session token (never the token itself), balance, creation and expiry timestamps, and status.
• Payment data: payment reference, Monero subaddress, quoted XMR and EUR amounts, the exchange rate snapshot used, transaction hash, confirmation counts and timestamps.
• Ledger data: an append-only record of every credit movement (deposits and plays) with the balance after each entry.
• Security data: short-lived rate-limit counters keyed by hashed client identifiers, and CSRF tokens.
• Logs: technical logs without wallet credentials, seeds or raw IP addresses where avoidable.

3. Cookies

• xmr_session, HTTP-only, SameSite=Lax session cookie. Required to identify your temporary session.
• xmr_csrf, readable double-submit CSRF token. Required to protect state-changing requests.
• xmr_admin, HTTP-only administrator session, only set after an admin logs in.

No analytics or advertising cookies are used.

4. Why we keep payment and ledger records

Confirmed payments are irreversible, so accurate records are essential for supporting players, resolving disputes and preventing double crediting. Ledger and payment records are retained after a session ends and are not silently deleted. Records never contain wallet secrets.

5. Third-party services

Exchange-rate quotes are fetched from public market-data providers (for example CoinGecko or Kraken). Those requests contain no personal data beyond ordinary request metadata. Payments are verified through our own Monero wallet infrastructure, not through an external processor.

6. Your choices

• Sessions cannot be ended manually, so a balance is never forfeited by accident.
• Clearing cookies detaches your browser from the session.
• You may request deletion of non-financial metadata by emailing xmrlottery@onionmail.org with your payment reference. Financial records required for accounting are retained.

7. Security

Session tokens are stored hashed, cookies are HTTP-only and SameSite, all money movements are serialised under database row locks, and wallet credentials stay outside the application in environment configuration.