Reference

Privacy Policy for India account data

Roulette, Mahjong Ways, Football Strike, UPI, Paytm and PhonePe all create account records when you use goldsbat, and this Privacy Policy explains how we handle those records.

Account dataCookie choicesUPI contextPaytm receiptsPrivacy requests
Explore the Lobby Read FAQ
goldsbat Privacy Policy for India account data
CONTACT PATHS

Reach us about privacy requests

Privacy questions need a clear path, not a long chase through unrelated screens. Use the contact option that matches your request, and include the mobile number or email tied to your account…

Privacy email Write to our privacy team with the mobile number or email linked to your account. We use those details only to locate the record, confirm control, and reply with the next step.
Account chat If you are signed in, open account chat and choose the privacy topic. Chat can help with cookie choices, data correction requests, and status checks without asking you to repeat basic account details.
Security request Use this path if you think another person has accessed your account data. We can lock sensitive actions while we check recent sign-ins, device records, and wallet activity linked to UPI, Paytm or PhonePe.
DATA CARE

How we handle your account data

Our Privacy Policy is written around the records we actually handle: account sign-ins, payment references, gameplay logs, support messages, cookies and security events.

Data we collect

We collect account details, contact fields, device signals, wallet activity, gameplay logs and support messages. These records help us run your account, answer privacy requests, check payments and detect account misuse.

Payment records

UPI, Paytm, PhonePe and Google Pay transactions create reference IDs, timestamps, status messages and wallet entries. We use them to match deposits, check withdrawals and respond if you dispute a payment entry.

Cookie choices

Cookies help keep you signed in, remember language settings and measure page performance. You can adjust browser controls, though some account and security features may not work correctly if key cookies are blocked.

Account security

We use sign-in checks, device records, wallet monitoring and restricted staff access to reduce misuse of personal data. If we detect unusual activity, we may pause sensitive actions while we confirm control.

Retention periods

We keep data only for as long as it is needed for service, legal, tax, dispute, fraud prevention or security reasons. When a record is no longer needed, we delete it or make it non-identifying.

Request handling

You can ask to access, correct or erase eligible personal data. We first confirm your account control, then assess the request against legal duties, security needs and transaction records we must keep.

Privacy Policy questions from India

These answers explain the main privacy choices available to you when you hold an account with us. They cover data collection, payment references, cookies, correction requests, deletion requests and account access. For anything that depends on your state or local rules, availability follows local law and applies only where local law permits.

We collect the details you enter, such as name, mobile number, email, login data and verification status. We also create account records for security checks, wallet entries, support contact and service activity.

Yes. We store payment references, timestamps, status updates and wallet entries so deposits and withdrawals can be matched. We do not store your full banking credentials or UPI PIN in our systems.

Yes, you can request access to eligible personal data linked to your account. We may ask you to confirm control through the registered mobile number or email before we prepare a response.

Contact support from your account or write to the privacy team with the current and new details. We may require verification before changing contact fields, because those details control account access and privacy replies.

You can ask us to erase eligible data. Some records may need to remain for legal, tax, dispute, fraud prevention or security reasons, especially where they relate to payments, withdrawals or account control.

Access is limited to team roles that need the data, such as support, payment checks, security, risk control or legal response. Staff access is restricted, logged where practical, and tied to work duties.

Cookies help with sign-in, account safety, language settings and page measurement. You can manage them in your browser, but blocking essential cookies may affect login, wallet actions or support access.

Related Pages

Neon City Scarab Riches Rummy Register