Reference

Legal access for Indonesian accounts for anjaytoto

Legal clarity comes before your first lobby entry with anjaytoto. For Indonesia, account access depends on local law, and we ask you to complete phone verification before account…

Indonesia policyPhone verificationWallet recordsLocal-law access
anjaytoto Legal access for Indonesian accounts for anjaytoto
CONTACT PATH

Where policy questions reach our team

A clear contact route matters when a Legal question affects your account or wallet record. We ask you to use the support contact displayed within your signed-in account, include the registered phone details and describe the policy point in plain English. For account questions from Surabaya or elsewhere in Indonesia, access still depends on local law, and we may ask for a receipt or reference before discussing account-specific details.

Team online

Account policy request

Use the signed-in support route to ask about account eligibility, a policy notice or a phone-verification step. Include your registered details so we can locate the correct record.

Wallet record question

For DANA, OVO, GoPay or QRIS references, send the payment receipt or transaction code through the account contact path. We use that detail to separate policy checks from status questions.

Access clarification

If a Legal notice affects access to the lobby, tell us when it appeared and which device path you used. We can explain the next account step where local law permits.

DATA PRACTICE

How anjaytoto handles account records

Our Legal process is tied to practical account handling rather than broad promises. We use the registered phone, wallet references and sign-in events to check requests, protect account ownership and respond to…

Phone verification

Before account access, we use the registered phone step to help confirm ownership. A request to change that number may require another account check before Legal records are updated.

Payment references

DANA, OVO, GoPay and QRIS references are retained when needed to match an account action or resolve a receipt question. We do not treat a wallet label as proof of ownership by itself.

Cookie settings

Cookies can support sign-in continuity and saved session preferences. You can manage browser cookie settings, although removing them may require you to repeat an account step.

Account security

Keep your phone details private and sign out on shared devices. If you notice an unfamiliar account action, contact us through the signed-in support route with the relevant reference.

Record retention

We keep account, payment and contact records for the period needed to operate the account, reconcile requests and meet applicable Legal duties. Retention can vary by record type.

Change requests

To request a correction or deletion, use the account contact path and state which record needs attention. We may verify your phone details before assessing the request.

Legal answers before you open account

These Legal answers focus on the questions we expect you to ask before account creation or when a policy notice interrupts access. We keep the route practical: check local eligibility, complete the requested account step and send the right record through support. If a rule is location-dependent, access depends on local law rather than on a promise made by the lobby.

It explains account eligibility, phone verification, wallet references, cookies, record retention, security requests and contact steps. It also clarifies that access depends on local law for your location.

Access is available only where local law permits. Before creating an account, check the rules that apply to you, then complete the requested phone-verification step if access is allowed.

Phone verification helps us confirm account ownership before access and before certain changes. If your registered number changes, we may request additional details before updating the account record.

We may retain DANA or QRIS references to match an account action, receipt or status question. Send the transaction code through the account support route if a record needs checking.

Use the signed-in contact path, identify the record and explain the correction or deletion requested. We may verify your registered phone details before assessing what can be changed.

Retention depends on the record and the applicable Legal duty. We keep account, payment and contact details only for the period needed for account operations and request handling.

Note the notice, device path and time it appeared, then contact us from the account support route. Include any relevant receipt or reference so we can explain the next step.