Reference

Privacy Policy for your India account

Account data, UPI payment records and cookie choices are handled under this Privacy Policy before you open your account and while you use the lobby.

UPI dataPaytm recordsPhonePe recordsCookie choices
rkludo Privacy Policy for your India account
CONTACT ROUTES

Privacy contact routes for India

Privacy requests should reach the team that handles account data, not a general lobby queue. Send enough detail for us to match your request to the correct account, but avoid sharing card images, UPI PINs or private wallet passwords. We may ask for a narrow verification step before sharing or changing data, because privacy access must go to the correct account holder.

Team online

Privacy email

Use [email protected] for requests about access, correction or erasure. Include your account email, the payment rail involved if relevant and the date range, so we can locate records without asking for extra data.

Account help desk

If your privacy query relates to login access or a wrong mobile number, our help desk can route it to the privacy team after a short account check. Do not post payment screenshots in open chat.

Security channel

Use the security contact path when you suspect account access from a device you do not recognise. We can freeze risky sessions, check recent data changes and explain what privacy records were affected.

DATA PRACTICE

How we handle privacy requests

Our privacy work starts before data reaches your account page. Forms ask for account details in small steps, payment records are kept apart from login credentials, and cookie choices are separated from…

Account data

We keep account identifiers, contact details, login events and preference settings so your account can be accessed, secured and serviced. Where a field is optional, we mark it clearly before you submit it.

Payment records

UPI, Paytm and PhonePe activity may create reference IDs, time stamps and status codes in your wallet record. These help us reconcile credits and withdrawals without collecting your private banking PIN or app password.

Cookie choices

Cookies help keep you signed in, remember language choices and detect unusual session activity. You can manage non-essential cookies through your browser, while security cookies remain needed for login protection.

Device security

We may record device type, IP range, browser version and failed login events. These signals help us spot account misuse, respond to security reports and decide when extra verification is needed.

Retention periods

We keep data only for account operation, legal record needs, dispute handling and fraud checks. When a purpose ends, records are erased, anonymised or kept in restricted storage for the remaining lawful period.

Change requests

You can ask us to correct contact details, close outdated profile fields or provide a copy of account data where applicable. We verify the requester first, then confirm the action taken by email.

Privacy Policy questions for your account

These answers explain how the Privacy Policy works when you create an account, use local payment options or ask us to change stored data. They are written for India account access and focus on practical steps: what we collect, why we use it, how long records may stay with us and how you can contact rkludo for privacy help.

It covers account details, contact data, payment references, device signals, cookie settings and privacy request records. It also applies to session logs created when you access lobby areas such as Blackjack, Bingo or Fishing War.

We collect payment references to match UPI, Paytm and PhonePe activity with your wallet, check transaction status and resolve disputes. We do not need your wallet password, UPI PIN or private banking credentials.

Yes, you can request a copy where applicable under law. We may verify your email, mobile number or recent account activity before sending data, so private records are not released to the wrong person.

Email the privacy team with the field that needs correction and the accurate detail. For sensitive changes, such as mobile number or payment identifier, we may request a verification step before updating the record.

Retention depends on the data type and legal need. Some session logs are short-lived, while payment and dispute records may stay longer for reconciliation, fraud checks, tax needs or lawful record duties.

Our cookies focus on account access, preference settings, security checks and service measurement linked to our domain. You can clear or block non-essential cookies in your browser, though login protection may still require essential cookies.

Write to [email protected] with your account email and a clear request. If the concern involves account misuse, include the last login time or device you noticed, but never share private payment passwords.