Reference

Privacy Policy for your koko500 account

When you open an account to reach Speed Baccarat, Big Bass, Football Strike or UPI wallet features, this Privacy Policy tells you what account, device, payment and support…

UPI privacy checksPaytm record handlingPhonePe wallet dataCookie choices

Explore the Lobby Read FAQ

How our India privacy terms work

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

Our Privacy Policy explains how koko500 collects and uses data linked to your account, wallet activity, device, location signals and support messages. We use these details to create your account, verify access, process UPI, Paytm, PhonePe or Google Pay records, protect the wallet, answer requests and

1
meet legal duties that apply in India. We do not sell your personal data. Some checks may involve payment processors, verification teams, hosting services or security tools that help us run the account flow. Access and eligibility depend on local law and are available where local
2
law permits. If a rule in your region changes, we may adjust account access, retention periods or verification steps. You can ask us to correct, access or delete eligible records, subject to legal, security and transaction needs.

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

HELP PATHS

Three ways to reach privacy support

Privacy requests need a clear route, so we keep contact paths tied to your registered account.

Email privacy request Use our privacy email from the contact page and write the account ID in the subject line. Tell us whether you want access, correction, deletion or cookie help so the request reaches the right team.

Live chat handoff If you start in live chat, ask for privacy support and we will move the chat to a secure ticket. Do not paste full UPI IDs, Paytm wallet data or passwords in chat.

Account ticket trail For payment-linked privacy questions, open a ticket after logging in. The ticket keeps your request, our replies and any verification steps in one place, which helps us respond without exposing extra account data.

ACCOUNT SAFETY

Six controls behind your privacy

We handle privacy as an account safety process, not as a one-time page. Each control below explains what happens when your data moves through login, wallet, game session, cookie or support systems.

Account data collection

When you join, we collect details needed for account creation, login security and age or region checks allowed by law. We keep the collection narrow and connect each field to a clear account purpose.

Payment record care

UPI, Paytm, PhonePe and Google Pay records are used to match payments, handle withdrawals and trace failed attempts. We keep transaction references separate from chat replies unless support needs them to answer you.

Cookie choices

Cookies help us remember session status, device type and security signals. You can manage browser settings, but some cookies are needed for login, fraud checks and keeping your account session from breaking.

Access controls

Only trained team roles can open personal records, and access is linked to support, payment checks, security checks or legal duties. We log internal access so unusual activity can be investigated.

Retention periods

We keep account and payment records only while needed for service, legal, tax, dispute or security reasons. When those reasons end, we delete, anonymise or separate records from active account tools.

Change requests

You can ask us to correct wrong details, receive a copy of eligible records or delete data that no longer needs to be kept. Some records may remain where law or security requires it.

Privacy questions before you join

Before you open an account, you should know how your data is handled and what choices you have. These answers focus on the Privacy Policy only: collection, cookies, payment records, support access, security checks, retention and your request rights. If your case involves local eligibility, access depends on local law and is available where local law permits.

It covers account details, login records, device data, IP address, cookie data, payment references, support messages and verification records. We collect these only when they relate to account access, wallet activity, safety checks or legal duties.

We use payment references to match your wallet activity, trace failed payments, verify withdrawals and answer payment-linked privacy requests. Full payment credentials should not be sent to chat; references are enough for most checks.

Yes. Send a privacy request from your registered email or account ticket and explain what is wrong. We may verify your identity first, then update eligible records unless legal or security reasons require the earlier record.

Yes. Cookies and similar storage may support login sessions, device recognition, language settings and security checks on mobile browsers. You can change browser settings, but required cookies may be needed for account access.

Support messages are available only to teams handling your request, payment issue, security check or legal duty. We do not ask you to share passwords, and we may mask sensitive payment details during ticket handling.

Retention depends on the record type and the reason it was collected. Account, payment and security records may be kept for legal, tax, dispute or fraud-prevention needs, then deleted, anonymised or separated from active tools.

Contact privacy support through email or an account ticket and state that you want deletion. We will verify your account, check whether any legal or security reason requires retention, and confirm what can be removed.

Privacy Policy for your koko500 account

Three ways to reach privacy support

Six controls behind your privacy

Account data collection

Payment record care

Cookie choices

Access controls

Retention periods

Change requests

Privacy questions before you join

01 What personal data does this Privacy Policy cover?

02 How are UPI, Paytm and PhonePe records used?

03 Can I ask koko500 to correct my account details?

04 Does the Privacy Policy cover cookies on mobile?

05 Who can see my support messages?

06 How long do you keep my data?

07 How do I request deletion of eligible records?

Related Pages