Reference

Privacy Policy for Your suku33 Account

Our Privacy Policy explains how suku33 handles the details you provide when opening an account, signing in, checking wallet status or contacting support.

Account dataWallet referencesCookie choicesContact requests
suku33 Privacy Policy for Your suku33 Account
CONTACT YOUR WAY

Privacy Questions Reach Our Support Route

A clear contact path helps you resolve a Privacy Policy question without posting personal details in a public chat. From your account, use the support route beside the cashier area and include the phone number linked to your profile, the subject of your request and any relevant receipt reference. We use those details to locate the correct record, while you should leave out wallet passwords, one-time codes and full banking credentials.

Team online

Account access request

If you cannot sign in after phone verification, contact our account support route with your registered number and device type. We may ask for an account step or recent login detail to confirm ownership before discussing stored data or changing the contact record.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, send the transaction time, amount shown in your account and receipt code through support. We use the minimum details needed to trace the record and will not ask you to disclose a wallet password.

Privacy request

To ask for a copy, correction or removal of personal data where applicable, state the request clearly and use the phone linked to your account. We may verify account ownership first, then reply through the contact route attached to your profile.

DATA HANDLING

What We Do With Account Details

Privacy Policy decisions are tied to practical account events rather than broad profile building.

Account information

We may handle your name or chosen account label, phone number, verification status and sign-in history. These details let us connect a login to the correct profile and help prevent an unrelated person from receiving account or wallet information.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account record can include a reference number, amount and status. We use these fields to reconcile the account ledger and investigate missing or duplicated entries without requesting your private wallet credentials.

Cookies and sessions

Cookies and similar session tools can keep your sign-in flow working, remember selected settings and help us identify a session that behaves unusually. You can manage cookie controls in your browser, although blocking essential cookies may interrupt account access.

Device security

When you open the lobby on a phone or desktop, we may receive device and connection signals linked to the session. These signals support login protection and troubleshooting; they are not a request for access to your contacts, photos or unrelated device files.

Retention periods

We keep records only for the period needed for account operation, payment reconciliation, dispute handling, security checks or a lawful requirement. When a record no longer serves one of those purposes, we remove it, anonymise it or restrict access where appropriate.

Changes and requests

You can ask us to correct an inaccurate phone detail, explain a data use, provide accessible account records or remove data where applicable. Send the request through account support, and we may verify ownership before making a change or explaining a legal limitation.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. We keep the process connected to the actual suku33 account path: phone verification, mobile sessions, payment references and support requests. If a question concerns eligibility or access, the answer depends on local law and the details of your account.

It covers personal details used for account access, phone verification, session security, wallet references, cookies and support requests. It also explains retention, correction and removal requests. The Privacy Policy applies when you use the mobile or desktop account path, where local law permits.

We use your phone number to identify the account, complete the verification step before access and send account-related replies through the matching contact route. It also helps us separate your DANA, OVO, GoPay or QRIS reference from another account record.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, including a receipt code, amount shown and status. We use those details to reconcile account activity, and we do not need your wallet password to investigate a receipt.

You can contact account support and ask for the personal data connected with your profile. Include your registered phone number and describe the records you need. We may verify ownership before responding, and the final scope depends on local law and retention duties.

Send a correction request through the support route linked to your account, identifying the incorrect field and the replacement detail. We may ask you to complete phone verification or another ownership check. Once confirmed, we update the record where local law permits.

Cookies can keep a login session active, retain selected settings and help identify unusual access from a mobile device or desktop. You can adjust browser cookie controls. Blocking essential cookies may prevent the account path from loading correctly or may require another sign-in.

Use account support to request removal and provide the phone number linked to your profile. We first verify ownership, then check whether records must remain for payment reconciliation, security, disputes or a lawful requirement. Any removal is handled where local law permits.