Reference

stm888 Legal For Clear Account Access

stm888 Legal sets out how we handle your account, payment records and access to the casino lobby in Indonesia.

Account termsData handlingLocal access
stm888 stm888 Legal For Clear Account Access
POLICY HELP

Get Help With Legal Policy Questions

A clear contact path matters when a Legal question affects your account or a payment record.

Account access For a Legal question about phone verification or account access, start from the account help path and describe the exact step that stopped you. We may ask you to confirm account details before discussing records, so your private credentials stay out of the request.
Payment records If a Legal request concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, attach the payment receipt reference rather than a wallet PIN. Our status check can then connect the record with the right account and policy question.
Data requests For a correction, deletion or copy request, use the policy contact route and state the change in plain English. We check the requester against the account before acting, then explain any limit that depends on local law or record retention.
DATA PRACTICE

See How stm888 Handles Policy Details

Legal handling is practical at stm888: we separate account identification from the secret credentials used to access it, keep payment references tied to the relevant transaction, and use access checks before discussing…

Account identity

We use the account details and phone verification step to confirm who is asking about a record. That check helps us avoid disclosing account data to the wrong person when a Legal request arrives through the support path.

Payment references

A DANA, OVO, GoPay or QRIS receipt reference helps us locate a transaction without asking for your wallet PIN. Bank transfer and virtual account references are handled as payment records, not as a substitute for account credentials.

Cookie choices

Cookies can keep a signed-in session and remember a policy preference on your device. You can adjust cookie controls in your browser, although blocking required cookies may affect the account step or prevent a policy page from loading correctly.

Account security

Keep your password, phone verification code and wallet PIN private. We do not need those secrets in a Legal request. If access looks unusual, describe the account step and date through support so we can check the event safely.

Record retention

We keep account, payment and support records for the period needed for account operations, security checks or a legal requirement. If you ask for removal, we explain which records can be changed and which must remain for that reason.

Policy changes

When a Legal policy changes, we update the wording on this page and identify the affected topic. You can ask us to clarify a clause, correct an inaccurate detail or explain how the change affects your account access.

Answers About stm888 Legal Access

These Legal answers cover the questions we expect before an Indonesian account holder opens access. They explain verification, personal data, cookies, payment records and requests for changes without turning policy language into a maze. Where a rule depends on location, we state that access depends on local law and point you to the relevant contact path.

The stm888 Legal page covers account access, phone verification, personal data, cookies, payment records and requests for corrections or removal. It also explains how to contact us about a policy question and when access depends on local law or where local law permits.

Yes. Access depends on local law, and some account or policy steps may differ where local law permits. Check the Legal wording before opening your account, complete the requested phone verification, and contact us if your location creates a question about eligibility.

Phone verification helps us confirm that a Legal request comes from the account holder before we discuss personal data or payment records. We may ask for account details, but you should never include your password, verification code or wallet PIN in a support request.

We use DANA, OVO, GoPay and QRIS references to match a payment status with the correct account and investigate a receipt question. Bank transfer and virtual account details can serve the same purpose. Send the reference and date, not private wallet credentials.

You can ask us to correct inaccurate account data through the policy contact route. State which detail is wrong and provide the account identifier requested for verification. We check your identity first, then confirm the correction or explain why a record must remain.

Cookies may keep your account session active and remember a policy choice on your device. Browser settings can block some cookies, but required cookies may be needed for the account step. If blocking them prevents access, contact us with the device and page details.

Use the policy contact path and quote the clause or describe the question in plain English. Include your account identifier only when requested, never a password or wallet PIN. We can clarify the wording, explain a data practice and outline the next account step.