Reference

sumobola login Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you create an account, complete phone verification, access the lobby on mobile or desktop, and use DANA, OVO, GoPay or…

Account collectionWallet recordsCookie choicesAccess requests
sumobolalogin.club page image
CONTACT ROUTES

Get Privacy Help Beside Account Support

A privacy question should not leave you guessing which team to contact. We route account, wallet and cookie questions through the same support path connected to…

Account access request Use the account help route when a phone verification record, sign-in detail or profile…
Wallet data question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction…
Cookie request If a browser setting changes your sign-in experience, tell us whether you used mobile…
HANDLING DETAILS

What This Policy Means In Practice

We keep this policy tied to actions you can recognise: creating an account, confirming a phone number, opening Live Baccarat or Mahjong Panda, checking a wallet status, and…

Account creation

When you open an account, we use the submitted contact details to create your profile and support sign-in.

Device signals

A mobile or desktop browser may provide device and session signals used to recognise repeated sign-ins, detect unusual access and…

Cookie controls

Cookies can remember sign-in continuity and selected preferences. You may adjust them in your browser settings, but disabling necessary storage…

Wallet matching

DANA, OVO, GoPay and QRIS references, along with bank transfer or virtual account details, help us match a receipt to…

Record retention

We retain account, security and transaction records for the period needed to operate the service, resolve disputes or meet legal…

Change requests

You can ask us to correct eligible account details, explain a data use or request removal where local law permits.

Privacy Policy Answers For Indonesia

These Privacy Policy questions cover the account and wallet situations you are most likely to check before opening access. We keep each answer tied to a practical step, from browser cookies and phone verification to a DANA receipt or a request to change stored details.

It covers account details, phone verification, device and browser signals, cookies, wallet references, support requests and retention. It also explains how we handle correction or removal requests where local law permits.

Yes. The policy covers DANA, QRIS, OVO, GoPay, bank transfer and virtual account references used to match a receipt, check wallet status or investigate an account-related payment question.

Phone verification is an account access check. We use its record to connect the confirmed phone step with your profile and to help investigate sign-in questions without asking you to share your password.

Cookies can support sign-in continuity, preferences and security checks. You can adjust browser permissions, but disabling necessary cookies may require another verification step or interrupt part of your account access.

Yes. Send an account help request naming the field that needs correction and the related account step. We verify the request before changing records, subject to local law and security requirements.

We keep records while they are needed for account operation, security checks, wallet disputes or legal duties. When those needs end, eligible records are removed or anonymised under our retention process.

You can ask for removal through the privacy support route. We first verify your identity and check whether a record must remain for security, dispute handling or a legal requirement before confirming the outcome.