Reference

Open the suku55 Privacy Policy

The suku55 Privacy Policy explains how we use account, wallet and device details when you access our casino, slot and sports areas.

Account dataWallet recordsDevice controlsCookie choices
suku55 Open the suku55 Privacy Policy
CONTACT THE POLICY TEAM

Browse Support Paths for Privacy Requests

A clear contact route matters when an account detail or wallet record looks unfamiliar. We use the support path beside the cashier area to help you ask about personal data, phone verification, login events or a payment reference. Include your account identifier and the date of the relevant event so we can locate the correct record without asking for unnecessary details.

Team online

Account privacy request

Use the account support route beside the cashier when you want to ask what personal details are connected with your suku55 account. We may ask you to confirm account ownership before discussing phone, login or wallet records.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, send the transaction date, amount shown in your account and the wallet name. We use those details to find the relevant record while limiting exposure of unrelated account activity.

Access correction request

If your phone verification detail or account contact data is wrong, tell us which field needs changing through the same support path. We may complete an ownership check before applying a correction to protect your account.

CONTROL YOUR DETAILS

Switch Through Data Handling Choices

Privacy controls work best when you know what each record does. We separate account access details from payment references, use device signals to protect sign-in sessions and keep cookie choices tied to…

Account details

We use your account identifier, phone verification result and sign-in history to confirm that the person requesting access matches the account. You can ask us to correct inaccurate contact details through the privacy support route.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us reconcile activity with your account. We do not need unrelated wallet content to answer a question about one transaction.

Cookies and devices

Cookies can remember session settings, while browser and device signals help us detect an unusual sign-in. On mobile, clearing site data can remove saved session choices and may require phone verification again.

Account security

We use sign-in events, verification status and device changes to investigate access that does not match your usual pattern. Never send a password or full wallet credentials when contacting us about a security concern.

Retention periods

We retain records only as long as needed for account operation, security checks, transaction reconciliation or a legal request. When a record is no longer needed for those purposes, our handling process removes or separates it.

Changes and requests

You can ask what data we hold, request a correction or raise a question about cookie use through support linked near the cashier path. We may verify ownership before changing or disclosing account-related details.

Ask About Your suku55 Privacy Policy

Search-style answers make the Privacy Policy easier to use when you are checking an account, device or wallet matter. These answers focus on the records we handle, the steps you can take and the access wording that applies to Indonesia.

The suku55 Privacy Policy covers account creation, phone verification, sign-in events, device signals, cookies, support messages and payment references. It applies when you access casino, slot or sports areas, including activity connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account.

We use phone verification to confirm account ownership and help protect sign-in access. If your verified detail is incorrect, contact support through the route beside the cashier. We may ask for an ownership check before changing it, and access depends on local law.

We may store a transaction reference, wallet name, status and related account identifier so we can reconcile DANA or QRIS activity. We do not need unrelated wallet content for that task. Send the date and reference through support if a record looks unfamiliar.

Yes. You can request a correction for account contact details, phone verification data or another inaccurate field through the privacy support route. State the field and the correct value clearly. We may verify ownership first, then confirm whether the change was applied.

Cookies can retain session choices in your mobile browser, while device signals help us identify unusual access. Clearing site data may remove those choices and require you to sign in or complete phone verification again. Cookie handling remains subject to your browser settings.

We keep records for the period needed to operate an account, check security events, reconcile a payment or respond to a legal request. When those needs end, the record is removed or separated under our handling process rather than kept without a purpose.

Use the support path linked beside the cashier and include your account identifier, question and relevant date. We can explain how the policy applies to your account or device. Any access or eligibility discussed with you depends on local law and the supported region.