Reference

sigma slot Legal: know your account terms

sigma slot Legal puts account conditions, access rules and data choices in one place before you open an account.

Access depends on local lawClear account conditionsData request pathwayWallet record context
sigma slot sigma slot Legal: know your account terms
LEGAL HELP PATHS

Ask support when Legal details need clarity

A clear contact path helps when a Legal clause, account record or access decision needs explanation. We ask you to include the phone number linked to your account and a short description of the issue, without sending a password or full payment credentials. Our support route can connect a policy question with the account or wallet-status context needed to check it. Where local law permits, we can also explain the next step for a correction request or access concern.

Team online

Account access question

Use the account support path when phone verification, a location check or an access decision is unclear. We can point you to the relevant Legal wording and tell you which account detail may need correction before access can continue.

Wallet record query

For DANA, OVO, GoPay or QRIS records, share the transaction reference and date through support. We use those details to separate a wallet-status question from a Legal request, without asking you to disclose your wallet password.

Policy change request

If you want an account detail corrected or a data-use question answered, send the request through our policy contact route. Include the account phone number, the wording you are questioning and the change you are asking us to consider.

DATA AND ACCOUNT CARE

Browse how sigma slot handles Legal duties

Legal handling is practical: we separate identity details, access records and transaction references so a request can be directed to the right account process.

Account details

We use the phone number and other details you submit to identify your account and apply access checks. Before discussing private records, we may ask for a matching account detail so the request is not answered for the wrong person.

Transaction records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment-status question to an account event. We keep the reference separate from your wallet password and do not need that password for a policy request.

Cookies

Cookies can preserve session settings and help us understand whether the Legal page loads correctly on your device. You can adjust browser cookie controls, though changing them may affect account access, page continuity or the way policy wording is displayed.

Account security

Phone verification is part of the account access path, and we use checks when a request concerns private records. Keep your login details private, sign out on shared devices and contact support if an account action does not match your request.

Retention questions

Our policy contact route can explain why a record is retained, which category it belongs to and whether a request can be made to change or remove it. The outcome depends on local law and on duties connected with account security or payment reconciliation.

Who to contact

Send Legal, data or access questions through the support route linked to your account. Include a concise request and your account phone number, but never include a password, wallet PIN or complete card credential in the message.

Find answers before opening your account

These Legal answers cover the questions we expect you to ask before creating an account or requesting help with account records. We keep the wording tied to the actual access path, phone verification and local payment references used by the Indonesia service. If your situation is not listed, contact us with the smallest amount of account detail needed to locate the issue. Access depends on local law, and a bank or wallet provider may apply separate conditions.

Legal sets out the conditions for account access, data handling, security checks and contact requests. Eligibility depends on local law, so we cannot treat an account as available in every location. Check the current notice and complete phone verification only when the service is permitted for you.

Phone verification may be required before account access because it helps connect your request with the correct account record. Use a number you control and keep it current. If verification does not match your details, contact support rather than sending a password or wallet PIN.

The notice covers account details, device and session records, security events, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains the purposes for handling those records and the routes available for questions or changes.

Yes, you can send a correction request through the policy contact route. State the account phone number, identify the detail that is wrong and describe the requested correction. We may verify ownership first, and the outcome can depend on local law or records needed for security.

A wallet reference can help us locate the account event behind your request, but it does not replace account verification. Provide the payment rail, date and transaction reference for DANA, OVO, GoPay or QRIS. Never send a wallet password, PIN or complete credential.

You can ask our policy contact route which record category is involved, why it is retained and whether a change or removal request is available. Retention can differ for account security and payment reconciliation, and any response is subject to local law.

Use the account support path and include your account phone number, location context and a short description of the access issue. We can explain the relevant Legal condition or request a check. Do not create duplicate accounts while the matter is being assessed, as that can complicate verification.