Reference

Open your privacy choices clearly

This Privacy Policy explains how keralalottary collects, uses, stores, and protects your account data when you browse the lobby, use UPI, Paytm, PhonePe, or contact us.

Account dataUPI contextCookie choicesSupport requests
keralalottary Open your privacy choices clearly
CONTACT ROUTES

Check privacy help from our team

Privacy questions need a clear path, so we keep contact options separate from general account chat where we can.

Email privacy desk Write to [email protected] for access, correction, deletion, cookie, or retention requests. Use the email linked to your account so we can verify you without asking for sensitive payment credentials.
Account support chat Use chat after login if your request is tied to a recent session, device alert, or payment record. Our team may ask basic account checks, but never your password, UPI PIN, or full card data.
Security escalation If you think your account was accessed without permission, contact us as soon as possible. We can review login events, pause risky actions during checks, and explain what data was involved.
ACCOUNT CARE

Browse the policy controls we use

We write this policy around the account actions you actually take: registration, login, lobby browsing, payments, withdrawal checks, and support conversations.

Data we collect

We collect account details you provide, device and login signals, support messages, and payment references connected with UPI, Paytm, PhonePe, or Google Pay. We keep the collection tied to account access, safety, and records.

How cookies work

Cookies help keep you signed in, remember language and device choices, measure page errors, and detect unusual sessions. You can manage browser cookies, though some account pages may not work correctly without required session cookies.

Payment privacy

Payment providers share references, status messages, and basic account matching data so deposits and withdrawals can be reconciled. We do not ask for your UPI PIN, Paytm password, PhonePe password, or Google Pay passcode.

Security checks

Login history, device changes, failed password attempts, and withdrawal edits may be reviewed to protect your account. When a check is needed, we limit access to trained staff and record the reason.

Retention periods

Some account and transaction records must be kept for legal, tax, fraud-prevention, or dispute reasons. When data is no longer required, we delete it, anonymise it, or keep only what the law requires.

Your requests

You can ask to access, correct, delete, or receive a copy of your personal data where local law allows. We may need to verify your identity before acting on the request.

Discover answers about your privacy

These answers explain how the Privacy Policy applies when you create an account, use payment options, manage cookies, or ask us to update your records. They are written for India, but your access and rights can depend on the law that applies in your location.

We collect the details needed to create and protect your account, such as your name, mobile number, email, login records, device signals, and payment references. We keep the collection linked to account access, security, and legal duties.

No. We do not ask for or store your UPI PIN, Paytm password, PhonePe password, or Google Pay passcode. Payment partners send transaction references and status updates so your wallet records can be matched.

Cookies keep your session active, remember basic preferences, help us find page errors, and support account security checks. You can control cookies through your browser, but required session cookies are needed for login pages.

Yes, you can ask us to correct account data that is incomplete or inaccurate. We may ask you to verify your identity first, especially when the change affects payment records, withdrawals, or account access.

You can request deletion where local law allows. Some records may need to be kept for legal, tax, dispute, security, or fraud-prevention reasons before deletion or anonymisation can be completed.

Only staff who need access for support, security, or account checks can view your messages. We train our team to avoid asking for sensitive credentials and to record why data was accessed.

Email [email protected] from your registered address or use logged-in chat for account-specific privacy requests. Tell us what you want us to check, but never share passwords, wallet passcodes, or UPI PINs.