Reference

Open with clear Privacy Policy control

Your lottrey account can hold identity details, wallet records, cookie choices and gameplay logs from rooms such as Turbo Blackjack, Fruit Party and Spribe Aviator.

Account dataCookie choiceUPI, Paytm, PhonePeIndia law context
lottrey Open with clear Privacy Policy control
CONTACT PATHS

Check privacy contact routes

Privacy requests work faster when they arrive with enough account context.

Privacy email Write to [email protected] from the email used on your account.
Account support Use in-account support when you can still sign in.
Payment queries For UPI, Paytm, PhonePe or Google Pay privacy queries, include the transaction reference and…
POLICY CARE

Browse our data care steps

The Privacy Policy is built around practical account events: opening an account, signing in, adding funds, playing a game, asking support for help and requesting a payout.

Account data

We keep core account details such as name, phone number, email address and verification status so you can sign in, recover access and receive account-specific privacy replies when you contact us.

Payment records

Payment references from UPI, Paytm, PhonePe and Google Pay are kept with wallet activity so deposits and withdrawal checks can be matched, audited and investigated if you raise a privacy query.

Cookie choices

Cookies help remember sign-in state, security checks and basic site preferences. You can adjust browser settings, but some account pages may ask you to sign in again after changes.

Device security

We record device, IP and session signals to detect unusual access, protect your wallet and reduce account takeover risk. These records are handled separately from support conversations where possible.

Retention windows

We keep data only for account operation, legal duties, dispute handling and security checks. When a record is no longer needed for those purposes, we delete it or reduce it where practical.

Change requests

You can ask to access, correct or delete personal data. Some payment and security records may need to stay longer when law, fraud checks or unresolved disputes require it.

See Privacy Policy answers

These answers explain the parts of the Privacy Policy you may need before opening or managing an account. They cover data collection, payment records, cookies, sharing, deletion and local law. If your situation is specific, contact us with your account email so we can respond against the right record.

We collect details such as name, email address, phone number, sign-in records, device signals and verification status. We use them to create your account, protect access, answer support requests and meet legal duties.

Payment records help us match deposits, review withdrawal requests and trace disputed transactions. We use references such as transaction ID, date, method and wallet status, not your full banking credentials.

Yes. Contact [email protected] from your account email and explain what needs correction. We may ask for verification before changing name, phone, payment or identity fields linked to account security.

You can request deletion, and we will assess it against account status, payment records, disputes and legal duties. Some records may be retained where required for security, fraud checks or compliance needs.

Cookies support sign-in sessions, basic preferences, security checks and traffic measurement. You can adjust them in your browser, though disabling certain cookies may require repeated sign-ins or reduce account page functions.

We share data only where needed for payments, verification, hosting, support tools, security checks or lawful requests. Partners receive the relevant data required for that task and must handle it with care.

Access and eligibility depend on local law, and the service is available where local law permits. Privacy records may also be handled differently when a legal request or regional requirement applies.