Reference

Privacy Policy for India account data

Our Privacy Policy maps how account details, wallet records, device signals and lobby activity are handled when you open an account with sportbooks.

India account dataUPI privacy contextPaytm and PhonePe recordsCookie choices
sportbooks Privacy Policy for India account data
CONTACT ROUTES

Ask about privacy records

Privacy questions are handled through the same account support routes you already use, but we treat data requests as a separate queue. Include your account email or phone number, the date range you mean, and the exact right you want to exercise. Do not send full card, UPI PIN, OTP or password details in any message.

Team online

Email privacy desk

Write to [email protected] with your account email or registered mobile number. We use that detail only to locate your record, confirm ownership and reply with the next step for your privacy request.

Live chat privacy ticket

Open chat after logging in and ask for a privacy ticket. The agent can record your request, but account deletion, data export and correction requests may require an email confirmation for safety.

Account centre requests

Your profile area lets you check core details such as name, phone, email and payment references. If something is wrong, raise a correction request so we can update eligible fields after verification.

ACCOUNT CARE

How we handle Keno privacy

We run privacy controls around the full account path, from first registration through payment checks and support messages.

Data we collect

We collect account identifiers, contact details, verification results, device data, login events, wallet references and lobby activity. These records help us run your account, check transactions and answer support messages tied to your profile.

Cookies and device signals

Cookies help keep your session active, remember language choices and detect unusual login patterns. You can manage browser cookie settings, though some account and security functions may not work correctly without them.

Payment record handling

UPI, Paytm, PhonePe and Google Pay references may include transaction IDs, timestamps, status codes and account-linked wallet data. We use these records to reconcile payments, process withdrawals and answer payment queries.

Retention approach

We keep personal data only as long as needed for account operation, payment records, dispute checks, fraud controls and legal duties. When a record is no longer needed, we delete or anonymise it where possible.

Security controls

Access to personal data is limited by role, logged for internal checks and protected with encryption where suitable. We also monitor unusual access attempts so we can act quickly if your account looks exposed.

Changes and deletion

You can ask us to correct, export, restrict or delete eligible data. Some records, such as payment logs and dispute files, may be kept for a lawful period even after your request is processed.

Privacy Policy questions for India

These answers explain the practical parts of the Privacy Policy, including what data we collect, how payment records are handled, and how you can make a privacy request. They are written for your account relationship with us, not as general legal text. For anything specific to your account, contact support with your registered details.

We collect details needed to create and protect your account, such as name, contact details, login records, device signals, payment references, verification results, support messages and activity connected with lobby pages you open.

Payment records are used to match deposits, process withdrawals, resolve failed transactions, handle refund checks and maintain account history. We do not ask for UPI PINs, OTPs or passwords in support messages.

Yes. Send a request from your registered email or through logged-in chat. We may ask for extra confirmation before sharing a copy, so your account data is not released to the wrong person.

You can ask us to correct eligible details such as contact fields or spelling errors. Some fields may need verification before we update them, especially when they affect payments, withdrawals or identity checks.

Retention depends on the record type. Support chats may be kept for service checks, while payment logs and fraud-related files may need longer storage because of disputes, accounting duties or legal requirements.

Access is limited to staff and vendors who need it for account support, security checks, payment processing, analytics or legal duties. We use role-based access so personal data is not broadly visible.

This policy is applied with India context in mind, including local payment methods and lawful requests. Where account access or eligibility is discussed, it depends on local law and is available where local law permits.