Reference

Privacy Policy for your account

Open your account with clear privacy terms: we explain what data we collect, why we need it, and how you can ask us to correct or remove it.

Account data useCookie choicesUPI contextSupport requests
sattamk Privacy Policy for your account
CONTACT PATHS

Three ways to reach privacy support

Privacy questions should not get lost inside routine account chat, so we route them through named paths.

Privacy email Write to [email protected] with your account email, request type and a short description. Do not include card scans or bank screenshots unless our privacy team asks for them through a secure reply.
Account inbox Use the message area after signing in when your request relates to wallet records, login history or personal details. Account messages help us match your request without asking for extra identity proof.
Chat handoff Start with chat if you need quick direction on cookie settings or where to submit a privacy request. The agent can pass the case to our privacy team when account changes are needed.
ACCOUNT SAFETY

Six privacy controls we use

This policy is practical, not decorative. It covers the account moments where data actually moves: sign-in, wallet use, game access, payment references, cookie settings and support contact.

Data collection

We collect details you enter, account activity, device type, approximate location signals and payment references. This helps us run logins, wallet checks, support replies and fraud screening without asking for the same details again.

Cookie handling

Cookies help remember sessions, language choices, security prompts and pages you used before reaching the lobby. You can adjust browser settings, but some account features may need cookies to work correctly.

Payment records

For UPI, Paytm, PhonePe and Google Pay, we store references such as transaction IDs, status updates and time stamps. These records help reconcile balances and answer wallet disputes tied to your account.

Access control

Privacy requests that change personal details, contact data or wallet records require account checks first. We use those checks to reduce false requests and keep another person from changing your profile.

Retention rules

We keep account and transaction records only for business, legal, security and dispute needs. When retention is no longer required, we delete, anonymise or separate records from active account systems.

Policy updates

When we change this Privacy Policy, we update the page date or account notice where needed. Important changes may be shown after sign-in so you can read them before continuing.

Privacy Policy questions answered

These answers focus on the privacy choices you can make before and after opening an account. They explain what we collect, why payment records matter, how cookies work, and how you can reach us when you want a correction, access to records or account-related privacy help.

It covers details you provide, login records, device signals, cookie data, account activity, payment references and support messages. It also explains why we use those records and when limited sharing may be needed.

We keep transaction references, status updates and timestamps to match deposits, withdrawals and wallet disputes to your account. These records help us check whether a payment reached the wallet correctly.

Yes. Send your request through [email protected] or the account inbox after signing in. We may verify your identity before sending data, because the file can include wallet and login records.

Use your account settings where editing is available, or contact privacy support for details that are locked. We may ask for verification before changing name, contact or wallet-linked records.

Cookies may record session activity, pages opened, device type and preferences. We use them for account security, page function and basic measurement, not to sell your personal data to outside advertisers.

Limited sharing may happen with payment processors, security tools, hosting partners, fraud checks, legal requests or support systems. Each sharing purpose must relate to running, protecting or administering your account.

Access and eligibility depend on local law and are available where local law permits. If a location rule affects your account, related privacy choices may also be handled under that rule.