Reference

suka2888 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a suka2888 account, sign in from a mobile browser, or connect DANA and QRIS.

Account clarityWallet dataCookie choicesPrivacy requests
suka2888 suka2888 Privacy Policy for Your Account
PRIVACY CONTACT ROUTES

Get Help With Your Privacy Policy

A privacy question should not be mixed with a game or payment query.

Account access Ask us to explain, correct or restrict account details through the support route connected…
Wallet records For DANA, OVO, GoPay or QRIS privacy questions, share the transaction reference and payment…
Device request Tell us whether the request came from a mobile browser or computer, along with…
DATA HANDLING DETAILS

Six Practical Privacy Controls

We keep this policy useful by connecting each privacy practice to a visible account action.

Collection

We collect details needed for an account request, such as contact data and phone verification status. Browsing records can include device type, session timing and pages opened during your account visit.

Cookie use

Cookies help keep your sign-in session connected to the right account area and remember necessary settings. You can review cookie controls in your browser, although changing them may affect account access.

Account security

We use phone verification and session checks to reduce unauthorised account access. Never send a password or wallet PIN in a privacy request; we only need enough detail to confirm the account issue.

Retention

We retain account and payment references only while they support administration, security checks, support handling or applicable obligations. When a record is no longer needed, we remove or anonymise it.

Correction

If your contact detail or account record is wrong, ask us to correct it through the signed-in support route. We may request an account step or verification detail before changing personal data.

Disclosure

We do not treat your account details as public content. Where a service partner must process a payment status or technical request, we limit the shared detail to that specific operational purpose.

Privacy Policy Answers Before Access

These questions address the points we hear before an account is opened or a privacy request is sent. Each answer relates to suka2888 Privacy Policy, including account records, wallet references, cookies, device sessions and the steps needed to contact us.

It covers account details, phone verification, device and session records, cookies, payment status references and privacy requests connected with your use of suka2888 where local law permits.

Phone verification helps us connect an account request to the correct account and reduce unauthorised access. We use its status for account security and do not need your private wallet PIN.

Yes. The Privacy Policy covers payment status and reference details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, not unnecessary wallet credentials.

We may record device type, session timing, browser settings and account pages opened during access. These details help connect a mobile sign-in issue with the correct privacy or security request.

Use the support route available inside your signed-in account and state which record needs correction. Include the relevant account step; we may verify ownership before making a change.

We keep account, security and payment references only for administration, support, security checks or applicable obligations. After that need ends, we remove or anonymise the record through our process.

Yes. Use the available support contact path and mention that your request concerns the Privacy Policy. Access and eligibility depends on local law, so we can clarify the relevant process first.