Reference

Privacy Policy for Your sukma bola Account

The sukma bola Privacy Policy shows which account, device, and payment records we handle when you verify your phone, sign in, or use DANA and QRIS.

Account data explainedWallet records identifiedCookie choices availableRequest path included

Explore Our Lobby Read FAQ

Know What DANA and QRIS Records Show

sukma bola Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Clear payment context helps you understand our policy before entering the cashier. We may record the selected rail, transaction reference, amount, time, and status for DANA, OVO, GoPay, QRIS, virtual account, or bank transfer activity; we do not ask for your wallet PIN. We also process

1
registration details, phone-verification results, sign-in events, browser identifiers, support messages, and activity needed to keep your account working. These records support identity checks, payment receipt matching, security controls, service delivery, dispute handling, and legal duties. Your eligibility depends on local law, and privacy rights can vary
2
under the rules that apply in Indonesia or your location. We share data only where operations, security, payment processing, or a valid legal request requires it, and we keep records only as long as those purposes or applicable duties remain.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY CONTACT PATH

Reach Account Help From the Cashier

A direct account path keeps privacy requests tied to the correct profile. Sign in, open the cashier-side account help area, and state whether you need access, correction, deletion, or an explanation of a payment record. If sign-in is blocked, use the account recovery route before sharing sensitive details. Our support availability appears inside the account so you can see when help is active. For policy access without signing in, open sukmabola.club/privacy-policy/ in your mobile browser and keep the relevant payment receipt nearby.

Team online

Payment record questions

After signing in, open account help beside the cashier and identify the payment rail and transaction reference. You may name DANA, OVO, GoPay, or QRIS, but never send us your wallet PIN, password, or full security code.

Profile correction requests

Tell account help which profile field is inaccurate and provide enough detail to locate it. We may verify your phone and account ownership before changing stored data, reducing the chance that another person alters your name or contact details.

Access or deletion requests

Ask through the signed-in account path for a copy of eligible data or deletion of records no longer required. We will explain any identity check, legal retention need, or security record that prevents immediate removal of a specific entry.

DATA HANDLING PRACTICE

Control Data Across Mobile Account Access

Practical controls apply from phone verification through the mobile path from login to the lobby. We separate account details, payment references, cookie settings, and security events according to their purpose, while limiting…

Account data collection

We collect details you enter during account creation, including contact and phone-verification data, plus identifiers created for your account. This lets us confirm access, connect support requests to the right profile, and detect attempts to enter an account without permission.

Payment record handling

For DANA, OVO, GoPay, QRIS, virtual account, and bank transfer activity, we handle references and status data needed to match receipts. BCA, BRI, Mandiri, or BNI may also appear when the selected transfer route supplies that context.

Cookie and device choices

Browser storage can preserve your sign-in session, security state, and selected preferences on a phone. You can clear or block cookies through browser settings, though doing so may end the session and require another login or phone check.

Account security records

We log sign-in time, browser type, device signals, and network address where needed to identify unusual access. Keep your password private and use account recovery if your phone changes, rather than sending credentials through a payment receipt message.

Purpose-based retention

Retention follows the reason a record exists, including account service, payment reconciliation, security checks, disputes, and applicable legal duties. When a record is no longer needed for those purposes, we remove it or detach it from direct account identification where practical.

Correction and escalation

Start with account help when your profile, device history, or wallet status appears incorrect. We may request phone verification or a matching transaction reference before acting, then explain the result and any record we must continue holding for legal or security reasons.

Get Privacy Policy Answers Before Joining

Specific answers make it easier to decide what data you are comfortable providing. The questions below cover the sukma bola Privacy Policy, phone verification, wallet references, mobile cookies, account access, correction, and deletion. They also explain what happens when you browse the policy without signing in and how to raise a concern from the cashier-side account help path. Read these points before opening an account, then return whenever your device, phone number, or preferred payment rail changes.

The Privacy Policy covers profile and contact details, phone-verification results, sign-in and device events, browser cookies, support messages, game-session records, and payment references. It also explains why we process these records, when sharing may occur, and how long a purpose may require retention.

No. For DANA or QRIS activity, we may receive a transaction reference, amount, time, selected rail, and completion status needed to match a receipt. You should never place a wallet PIN, password, or full security code in an account help message.

Sign in and open account help beside the cashier, then ask for access to eligible data linked to your profile. We may verify your phone or account ownership first. If you cannot sign in, complete account recovery before supplying sensitive request details.

Yes, you can ask account help to correct inaccurate profile data. State which field needs attention and be ready to confirm account ownership through phone verification. Some changes may require extra checks when they could affect sign-in security or payment receipt matching.

You can request deletion through the signed-in account help path. We remove eligible data when it is no longer needed, but certain payment, dispute, security, or legal records may need to remain. We will explain the reason if a specific record cannot be removed.

It describes browser storage used for sign-in sessions, security state, and account preferences on your phone. You can clear or block these items in browser settings. That choice may sign you out, reset preferences, or trigger another phone-verification step during access.

Yes. Open sukmabola.club/privacy-policy/ directly in a mobile browser to read the policy without signing in. You can check the data categories, payment context, cookie choices, retention approach, and account help route before deciding whether to provide registration details.

Privacy Policy for Your sukma bola Account

Reach Account Help From the Cashier

Payment record questions

Profile correction requests

Access or deletion requests

Control Data Across Mobile Account Access

Account data collection

Payment record handling

Cookie and device choices

Account security records

Purpose-based retention

Correction and escalation

Get Privacy Policy Answers Before Joining

01 What data does the sukma bola Privacy Policy cover?

02 Does sukma bola receive my DANA or QRIS wallet PIN?

03 How do I request access under the Privacy Policy?

04 Can I correct my phone number or account details?

05 Can I ask sukma bola to delete my account data?

06 What cookies does the Privacy Policy describe?

07 Is the Privacy Policy available before I open an account?

Related Pages