Reference

Privacy Policy for your kalodata account

This Privacy Policy explains how we collect, use, protect, and retain the data linked to your kalodata account, including login details, device signals, payment references, and support chats.

Account dataCookie choicesIndia privacy contactUPI Paytm PhonePe context

Browse lobby Read FAQ

How this policy applies in India

kalodata Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Our Privacy Policy covers the data we handle when you open an account, verify details, use the wallet, contact support, or change privacy preferences. We collect only what we need for account access, fraud checks, transaction matching, legal record keeping, and service messages. Access to the

1
lobby and account services depends on local law and is available where local law permits. Payment references from UPI, Paytm, PhonePe, and Google Pay are used to match deposits or withdrawals with your account, not to see your full banking activity. We may keep some records
2
after closure where law, dispute handling, or security checks require it. You can ask us to correct data, close your account, or raise a privacy request through the contact paths below.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

Three ways to reach our privacy team

Privacy requests work better when they include the email or mobile number linked to your account, the request type, and any payment reference if the query…

DATA CONTROLS

Six checks behind your data choices

We treat privacy as an account operation, not a hidden back-office task. Your requests are logged, identity checks are matched to the account, and payment-related queries are separated from general support messages.

Data collection

We collect account registration details, login events, device signals, wallet references, and support messages. Game activity records may include session IDs for titles such as Live Roulette or Spribe Aviator when needed for account checks.

Payment records

UPI, Paytm, PhonePe, and Google Pay references help us match a deposit or withdrawal to your account. We store transaction IDs, time stamps, and status updates, not your UPI PIN or full bank login data.

Cookies

Cookies help keep your session active, remember basic preferences, and detect unusual sign-in patterns. You can change browser cookie settings, although some account and security functions may not work as expected without them.

Security checks

We use password controls, session monitoring, and verification steps when privacy changes affect account access. If a request looks unusual, we may pause the change until your identity is confirmed.

Retention periods

Some data is removed when it is no longer needed, while payment, dispute, and fraud-prevention records may stay longer where law or account protection requires it. We apply retention by record type.

Your requests

You can ask to correct account details, receive a copy of certain data, withdraw optional communication consent, or close an account. We explain if a record cannot be deleted right away.

Privacy Policy questions before you join

These answers explain how the Privacy Policy works in real account situations: sign-in, payments, verification, cookies, support, and closure. They are written for India and should be read with the full policy text. If your request involves local law, account access, or a payment dispute, contact us so we can check the exact record.

We collect the details needed to create and protect your account, such as name, contact data, login credentials, device signals, verification data, wallet references, and support messages connected to your activity.

We use payment references to match deposits, withdrawals, refunds, and dispute checks with your account. We do not ask for your UPI PIN, full bank password, or private wallet login details.

Yes. Send a correction request through privacy email or signed-in chat, with the detail that needs changing. We may ask you to verify identity before updating contact data or payment-linked records.

You can request deletion or account closure. Some records may need to remain for legal, fraud-prevention, payment matching, or dispute reasons, and we will explain the reason if immediate deletion is not possible.

Cookies support sign-in sessions, language choices, security checks, and basic site measurement. You can change cookie settings in your browser, but account access and fraud detection may be affected.

Only teams that need the case can access the request, such as privacy, account security, payments, or support. We limit access by role and keep a record of case handling.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests can still be raised through the contact paths if you need help with account records.

Privacy Policy for your kalodata account

Three ways to reach our privacy team

Six checks behind your data choices

Data collection

Payment records

Cookies

Security checks

Retention periods

Your requests

Privacy Policy questions before you join

01 What personal data do you collect when I open an account?

02 How are UPI, Paytm, PhonePe, and Google Pay details used?

03 Can I ask for my account data to be corrected?

04 Can I ask for my data to be deleted?

05 Why do you use cookies on kalodata.net?

06 Who can access my privacy request inside kalodata?

07 Does account access depend on where I live?

Related Pages