Reference

Privacy Policy for Your Account Data

Clear control over account, KYC, cookie and wallet data starts here: this Privacy Policy explains what we collect, why we use it, how long we keep it and…

KYC data useUPI privacy contextCookie choicesAccount access checks
pushpaexch Privacy Policy for Your Account Data
CONTACT ROUTES

Policy Help From Real Support Paths

Privacy questions should reach the right team without you repeating the same details across channels.

Email privacy desk Send data access, correction or deletion requests through our privacy email with your account…
Live chat handoff If you start in live chat, ask for a privacy handoff rather than sharing…
Wallet record queries For UPI, Paytm or PhonePe privacy queries, share the transaction time and masked reference…
DATA PRACTICE

Data Care Across Account Steps

Each account step creates a different privacy need, so we avoid treating every detail the same way.

Account sign-up data

We collect details such as name, mobile number, email and login record to create and secure your account. These fields help us contact you about privacy requests and confirm that a change request is genuine.

KYC and access checks

Where checks apply, document data is used to confirm identity, location and account eligibility under local law. Access depends on local law and is available where local law permits, so these checks may affect account features.

Wallet and payment records

UPI, Paytm, PhonePe and Google Pay references are stored with wallet activity so we can reconcile entries and investigate mismatches. We mask or restrict sensitive fields where full detail is not needed for the task.

Cookies and device signals

Cookies help keep your session active, remember basic settings and protect against unusual access. Device signals may include browser type, IP range and login time, and you can change cookie settings in your browser.

Game session records

Round IDs for titles such as Lightning Roulette, Ganesha Gold, Crash X or Fishing War may be linked to your account record. This helps resolve privacy-linked account queries without exposing unrelated session history.

Retention and deletion

Some records must be kept for security, payment reconciliation or legal duties, even after a deletion request. When retention is no longer needed, we remove or anonymise data using an internal case record.

Privacy Policy Questions Before Joining

Before you join, you may want to know how your data moves through the account flow and what choices you have after registration. These answers focus only on Privacy Policy matters: collection, access, correction, deletion, cookies, sharing and local-law eligibility checks for India.

We collect the details needed to create and protect your account, such as name, mobile number, email, login records and device signals. Where required, KYC details may be collected for identity and local-law access checks.

Wallet references help us match a transaction to your account and answer privacy or reconciliation queries. We aim to use masked references where possible and restrict full payment details to teams that need them.

Yes. Send a request through the privacy email with your account ID and registered mobile number. We may verify your identity before sharing a copy so that your data is not sent to another person.

Contact support and state which detail needs correction. We may ask for proof before changing identity-linked fields, especially where the update affects KYC, wallet matching or account recovery.

You can request deletion, and we will assess what can be removed. Some records may need to stay for payment reconciliation, security checks or legal duties before they can be deleted or anonymised.

Yes. Cookies are used for session continuity, account safety, language settings and site performance checks. You can manage many cookie choices in your browser, though some settings may affect how account pages load.

Use the privacy email or ask live chat for a privacy case handoff. Account access and eligibility depend on local law and are available where local law permits, so we may verify location or identity before replying.