Reference

Privacy Policy For Your suma55 Account

Our Privacy Policy explains what we collect when you open a suma55 account, verify your phone, enter the lobby on mobile, or use DANA and QRIS.

Account dataWallet detailsCookie choicesAccess requests
suma55 Privacy Policy For Your suma55 Account
DIRECT HELP ROUTES

Get Privacy Help Beside Account Support

A clear contact path matters when you want to ask about Privacy Policy data rather than a wallet balance or lobby session. We keep privacy questions close to the account and cashier support route, so you can identify the relevant phone verification, device session, or payment reference without sending sensitive details through an unrelated channel. When writing from Jakarta or elsewhere in Indonesia, include your account phone number only through the protected route displayed in your account.

Team online

Account privacy request

Use the support route shown inside your suma55 account to ask what personal data is linked to your phone verification. We may ask for an account step that confirms ownership before discussing records, and you should not send a wallet PIN or full payment password in your message.

Wallet data question

If your question concerns DANA, OVO, GoPay, QRIS, a virtual account, or bank transfer, include the payment rail and its status rather than the full credential. We use that context to locate the relevant record while limiting the payment details visible to support.

Correction or deletion

Ask through the same account support path when a name, phone detail, device record, or contact preference needs correction. We will explain which changes can be made, which records must remain for account safety, and what identity check is needed before action.

DATA HANDLING

How suma55 Handles Your Privacy Choices

We treat privacy as an account operation, not a banner that disappears after your first visit. Our controls connect phone verification, device access, wallet status, cookie choices, and retention decisions so we…

Account records

We collect account details needed to create and maintain your access, including a phone number and verification result. A single account may connect casino areas and local wallets, so we associate wallet status with your account rather than exposing it on a public page.

Payment references

For DANA, OVO, GoPay and QRIS, we use payment references and status information to match an account action. Virtual account and bank transfer records may also be retained for reconciliation, but we do not ask you to place a wallet PIN in a support message.

Cookies and devices

Cookies and device signals help us keep a session connected to the right account, remember selected access settings, and detect unusual sign-in behaviour. On mobile, the path from login to the lobby can create session data; clearing cookies may require phone verification again.

Security checks

Before we discuss private records or change account details, we may confirm ownership through the phone verification already attached to your account. This protects your data when a device changes, a session appears unusual, or someone asks about Live Blackjack Diamond activity.

Retention choices

We retain records only for the operational, security, dispute, or legal reasons described in this Privacy Policy. When you request deletion, we assess the specific record first; some account and payment references may need to remain for a defined purpose.

Your requests

You can ask for access, correction, clarification, or eligible deletion through our support route. Tell us whether the request concerns your phone record, cookie setting, device session, or payment reference, and we will use the narrowest practical check before replying.

Privacy Policy Answers For suma55

These Privacy Policy answers focus on the account questions you are most likely to have before opening access or using a wallet. We keep the wording practical: what we collect, why phone verification appears, how cookies affect a mobile session, and where to send a request. If your situation is specific, use the account support route shown on suma55 rather than sharing sensitive details in an open message.

The suma55 Privacy Policy explains how we collect, use, protect, retain, and respond to requests about account data. It includes phone verification, device signals, cookies, wallet references for DANA and QRIS, and records connected with account access where local law permits.

Phone verification helps us confirm that an account request comes from the account holder. We may use it before discussing private records, changing account details, or investigating a device session, including access to casino areas or wallet status.

Yes. The Privacy Policy covers payment references and status information connected with DANA, OVO, GoPay and QRIS, as well as virtual account and bank transfer records. We use those details to match account activity without asking for a wallet PIN.

A mobile session may create cookie and device records that keep login connected to the correct account and help detect unusual access. If you clear cookies or change devices, we may request phone verification before restoring private account access.

You can request correction or eligible deletion through the support route displayed inside your account. Tell us which record is involved, such as a phone detail, device session, or payment reference. We will explain any ownership check and retention reason.

Send an access request through the protected account support path and identify the category you want clarified. We may confirm your phone verification first, then explain the relevant account, cookie, device, or wallet reference without revealing another person’s data.

This Privacy Policy is written for access connected with Indonesia, including account and wallet activity in places such as Surabaya. Access and eligibility depend on local law, so local requirements may affect whether an account request can proceed.