Reference

Privacy policy for your account

This page explains what we collect, why we need it and how we protect it when you open and use your account.

Account detailsCookiesIdentity checksLocal law
playkaro Privacy policy for your account
REQUEST PATHS

Where to send privacy requests

Use the same routes you use for account help when you need a privacy action. We accept access, correction and deletion requests through the in-account form, the registered email address and the…

In-account form Send the request from the support area after sign-in. That lets us link the query to your account faster and keeps the thread tied to the right record set.
Registered email Write from the email tied to your account so we can confirm the sender. Include the issue, the change you want and any reply address you want us to use.
Contact page If you cannot reach the account area, send the request through the contact page and mention it is a privacy matter. We route it to the right team and reply after checks.
KEEPING THINGS ORDERED

How we protect account records

We handle privacy work with a few simple rules. Only people who need the record can reach it, and access is logged.

Data use

We use the details you share to create the account, process support requests and keep the service running. We do not use them for unrelated purposes without a legal basis or your valid request.

Cookies

Cookies help us remember your session, language choice and login state. They also help us spot unusual sign-in patterns and reduce repeated checks when you return from the same device.

Account safety

Protect your account with a strong password and keep OTPs private. If you suspect someone else reached your account, contact us at once so we can lock the thread and check activity.

Retention

We keep records only as long as we need them for account handling, dispute work, payment checks or legal duties. After that, we delete or de-identify them where the law allows.

Contact route

For access, correction, deletion or a question about how a record is used, send the request from your registered email or the in-account form so we can verify the sender.

Change requests

If your details change, tell us through support and attach the updated fields. We will review the request, confirm what can be changed and keep an audit trail for safety.

Common privacy questions answered

These questions cover what we collect, why we keep it and how you can ask for changes. If a rule differs by location, the local rule applies. We keep the process plain: use the registered email or the in-account form, confirm identity when asked and wait for our reply through the same channel. That helps us protect your account and keep the request tied to the right records.

We collect the details you enter, login records, device signals and payment-related records needed to run the account, verify requests and handle UPI, Paytm and PhonePe activity. We do not ask for extra details without a clear reason.

Cookies help us keep you signed in, remember language choice and reduce repeated checks on the same device. They also help us spot unusual access patterns so the account stays protected.

We may share limited details with service partners who help us host systems, process requests or check for misuse. They only get what they need for the task and must handle it under our instructions.

We keep records only for the period needed for account handling, dispute work, audit checks and legal duties. After that period, we delete or de-identify them where the law allows.

Send the request from your registered email or the in-account form, say what you want changed and attach any proof we need. We will confirm identity before making the update.

Yes. Use the same contact route and ask for access to your account records. We will verify the request, explain what can be shared and respond through the same channel.

Where local law differs from this page, the local rule applies and access is available only where local law permits. If a request cannot be completed, we will explain the reason through support.