Reference

Legal terms for your sakti33 account

sakti33 Legal terms explain how account access, wallet records, game availability and personal data are handled for you in Indonesia.

Account termsData choicesLocal-law access
sakti33 Legal terms for your sakti33 account
CLEAR CONTACT ROUTES

Get Legal help without guessing

A clear contact route matters when a policy question affects your account. We organise help around the exact issue: access and verification, wallet status, or a request about personal data. Start from the account help path and include the phone number or payment reference connected to your question. This lets us check the relevant record without asking you to repeat the full story. For account eligibility, our answer remains subject to local law.

Team online

Account access

Use the account help path when phone verification, sign-in status or a local-law access question prevents you from reaching your account. Include the affected phone number so we can identify the correct record.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the payment reference through the cashier support path. We use that reference to trace status without requesting your wallet password.

Data requests

Ask through support when you need a personal-data copy, correction or clarification about retention. Tell us which account detail is involved, and we will direct the request to the relevant policy contact.

DATA HANDLING DETAILS

Your policy choices stay visible

We handle this Legal area through practical account controls rather than vague promises. Your phone verification connects access to the account record, while payment references help us separate a wallet-status question from…

Personal data

We use account details to create access, complete phone verification, match support requests and maintain payment records. We do not need your DANA, OVO or GoPay password to investigate a wallet reference.

Cookies

Cookies can keep a browser session connected to the correct account and help preserve policy preferences. You can manage cookie permissions through your browser settings, although some account steps may then need to be repeated.

Account security

Phone verification is required before account access, and we ask you to protect the phone and sign-in details linked to your record. Never send a password or wallet PIN through a support request.

Record retention

We keep account, payment and support records for the operational or legal period that applies to each record. A retention question can be raised through support with the relevant account or payment reference.

Policy contact

For a Legal question, use the account help route and describe the clause or record involved. We can direct questions about access, data use, cookies, retention or payment evidence to the appropriate contact path.

Change requests

If your name, phone detail or another account field needs correction, request the change after signing in where possible. We may ask for verification before editing a record tied to wallet activity.

Find answers before opening an account

These Legal answers focus on the questions we expect you to ask before using sakti33 in Indonesia. They explain access, data, payment records, cookies and contact steps without replacing the full policy notice. If your circumstances are different, send the specific question through the account help route so we can respond to the record involved.

It covers account creation, phone verification, access conditions, personal data, cookies, payment records, retention and requests to correct account details. It also explains how to contact us about a policy question. Access depends on local law and the account steps shown to you.

Access and eligibility depend on local law. Where local law permits, you may continue after completing the required account and phone-verification steps. If your location or circumstances create uncertainty, contact support before opening an account and ask about the applicable access position.

Phone verification connects the person requesting access with the account record and helps us handle later account or payment questions. It is required before account access. Keep control of the verified phone and do not share its security codes with anyone.

We may retain payment references, status details and related account notes so we can trace a deposit or withdrawal question. These records do not require your wallet password. For a correction or clarification, send the payment reference through the cashier support path.

Yes, send the request through the account help path and identify the account field or record involved. We may ask for verification before releasing or changing personal data. Requests about retention, cookies or payment evidence can use the same contact route.

Cookies may keep your browser session connected to the correct account and remember policy preferences. You can adjust permissions in your browser settings. If cookies are restricted, some sign-in or verification steps may need to be completed again.

Start with the account help route and describe the specific clause, access decision, data field or payment record involved. Include your account phone number or reference where relevant, but never send a password, wallet PIN or verification code.