Reference

sumbawatoto Privacy Policy For Indonesia

Your sumbawatoto Privacy Policy path shows what we collect, why we use it and how you can ask for a change before opening an account.

Clear data purposesWallet record contextCookie choicesAccount access steps
sumbawatoto sumbawatoto Privacy Policy For Indonesia
CONTACT YOUR WAY

Privacy Questions Through Account Support

A clear contact route helps when your Privacy Policy question concerns a phone check, wallet reference or device sign-in. Start from the support path linked inside your account area and include the email or phone connected to your account, but never send a wallet password or full security code. We use those details to locate the right record and keep the request attached to your account.

Team online

Account access

If you cannot complete phone verification or sign in, use the account support path and describe the device step that stopped. We may ask for account identifiers already held by us so we can confirm ownership before discussing personal data.

Wallet records

For a DANA, OVO, GoPay or QRIS reference, send the date, amount reference and account contact through the support path. We use those details to check the record while avoiding requests for your wallet password or private security code.

Privacy requests

To ask about access, correction or deletion, state the request clearly and use the contact route shown in your signed-in account. We may verify your identity first, then explain what can be changed and what records must remain.

DATA HANDLING

What We Do With Account Records

We keep this Privacy Policy practical by linking each data use to an account task rather than collecting details without a stated reason.

Account details

When you open an account, we collect the contact details and verification result needed to create and protect that account. We use the phone step before access to reduce mistaken identity, and we keep your submitted details tied to the account record.

Device signals

A mobile or desktop sign-in can create technical signals such as device type, browser setting, session time and security events. These signals help us spot repeated access attempts and protect your account without treating a device signal as your identity by itself.

Cookies

Cookies and similar storage can remember a session, preserve a selected setting and help us understand whether a page loads correctly. You can manage cookie controls through your browser, although changing them may require another sign-in or limit some account page functions.

Wallet references

Payment records may include a DANA, OVO, GoPay or QRIS reference, along with bank transfer or virtual account details supplied during reconciliation. We use these records to check account status and do not need your wallet password to match a transaction.

Security records

We retain sign-in attempts, phone verification events and account changes for security checks and dispute handling. If an unusual session touches a title such as Live Roulette Gold, the related event may be connected to the account record for investigation.

Retention requests

You can ask what personal data we hold, request a correction or ask whether deletion is available where local law permits. We first confirm account ownership, explain any retention requirement, and record the outcome through the support contact attached to your account.

Privacy Policy Questions Answered

These Privacy Policy answers cover the account actions Indonesian customers ask about most often, including phone verification, wallet references, cookies, device access and requests to change stored data. If your case does not fit one of these answers, use the support path inside your account and describe the specific record or access step involved.

The sumbawatoto Privacy Policy covers data collected when you open an account, verify your phone, sign in, use wallet functions or contact support. It explains purposes, cookies, security records, retention and requests for access or correction where local law permits.

Phone verification helps us connect account access to the person who supplied the contact detail and helps identify unusual sign-in attempts. We record the verification result and related account event, then use it for account security and support handling.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use these references to reconcile account activity and check status, not to request your wallet password.

You can request a correction through the support path inside your account. Tell us which detail is wrong and provide the account contact used for verification. We may confirm ownership before changing the record and will explain any restriction where local law permits.

Cookies can keep your session active, remember a setting and help us detect page errors. Your browser controls whether some cookies are stored. If you remove them, the account may ask you to sign in again or may not retain selected page preferences.

Use the signed-in account support route and ask for a copy or explanation of your personal data. Include the account phone or email, but do not send a password or security code. We verify ownership before responding to protect the record.

This Privacy Policy applies to account activity connected with Indonesia access where local law permits. Eligibility and retention duties depend on local law. If you access from Yogyakarta, Jakarta or another location, we may apply the requirements connected with that access.