Reference

Privacy Policy For Your sultan80 Account

Our Privacy Policy explains how we handle the account details you submit before you enter the lobby, including your phone verification record and wallet status.

Clear data choicesWallet-linked recordsMobile session controlsAccount help path
sultan80 Privacy Policy For Your sultan80 Account
CONTACT ROUTES

Get Privacy Policy Help Without Guesswork

A clear contact route matters when a phone check, wallet reference or account record needs attention.

Account help path Use the account help path for a Privacy Policy question about your phone verification, stored profile details or a request to correct an account record. Tell us which account step you mean, and share only the details needed to locate it.
Wallet status query For a privacy question linked to DANA, OVO, GoPay or QRIS, identify the wallet rail and the status shown beside the cashier event. We can then separate a payment reference from the personal account data connected to that event.
Security concern If your mobile session, phone verification or account access looks unfamiliar, contact us through the account help path and describe the device step involved. We use that context to review the request without asking you to publish sensitive credentials.
DATA CONTROLS

What We Do With Your Account Data

Our Privacy Policy follows the account journey from phone verification to wallet status, so each data use has a practical reason.

Account records

We use your phone verification record to connect you with the correct account and reduce confusion when you return from a mobile device. Profile details remain tied to your account path, while a request to change inaccurate data can be sent through account help.

Cookie choices

Cookies can keep a sign-in session and remember a setting between pages, but they are handled separately from a DANA, OVO, GoPay or QRIS payment reference. Your Privacy Policy request can ask which cookie category was used and for what account function.

Device sessions

When you move from mobile to desktop, session details help us identify the active account path and protect access. We do not require you to create another account for that device change; report an unfamiliar session through account help so we can assess it.

Payment references

A bank transfer, virtual account or QRIS reference helps us locate a cashier event, but it is not treated as a general profile detail. We use the reference for the related account task and ask for the payment name before checking its status.

Retention timing

We retain account, security and payment records for the period needed to operate the requested account function and meet applicable legal duties. A Privacy Policy request can ask about a specific record type, its purpose and whether the retention period has ended.

Change requests

You can ask us to correct account data, explain a data use or clarify a deletion request through the account help path. Include your account identifier and the exact field or record in question, while leaving out passwords, wallet PINs and full payment credentials.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and device questions you are most likely to have before opening an account. We focus on the records created by phone verification, mobile sessions and local payment references rather than describing unrelated lobby functions. Where a request involves eligibility or account access, the answer remains subject to local law. You can use the account help path for a question that needs a record-specific response.

This page contains the sultan80 Privacy Policy for account, device, cookie, security and payment-reference handling. Read it before opening an account, then use the account help path if you need clarification about a phone verification record or a wallet event.

The Privacy Policy covers details used for account access, including your phone verification record, session details, cookie choices and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use a DANA or QRIS reference to match a cashier event with the correct account and status. The reference is handled for that operational purpose, not as a general profile field. Ask through account help if you need a record-specific explanation.

Yes. Send a correction request through the account help path and identify the account field or record that appears inaccurate. We may need to verify the account step involved, but you should never send a password, wallet PIN or full payment credential.

Yes. It covers session details used to keep your account path working when you move between mobile and desktop. If a session looks unfamiliar, state the device and sign-in step through account help so we can assess the security concern.

We keep each record for the period needed for its account, security or payment purpose and for applicable legal duties. The Privacy Policy lets you ask about a particular record type, its purpose and whether its retention period has ended.

The Privacy Policy still explains how we handle your submitted data, but account access and eligibility depends on local law. Where local law permits, use the account help path for a question about the data connected with your account step.