Reference

Your stm123 Privacy Policy, Clearly Set Out

Your stm123 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby and use DANA, OVO, GoPay or QRIS.

Account data explainedWallet records coveredCookie choices availableContact route included
stm123 Your stm123 Privacy Policy, Clearly Set Out
HELP WITH YOUR DATA

Get Policy Help Beside Account Support

A privacy question should not leave you searching through the lobby. Use the account help link beside the cashier path and describe the record, device or account step you want us to check. We can connect your request to the relevant login, wallet or verification reference without asking you to publish personal details in a game chat. If your access issue comes from a phone change or a QRIS receipt, include that context so we can route the request under this Privacy Policy.

Team online

Account help link

Open the account help route beside the cashier path when you need to ask about stored details, phone verification or a Privacy Policy request.

Wallet record check

Tell us whether the reference concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account so we can locate the correct payment record.

Device access request

If a phone or browser no longer reaches your account, share the access context through support; we use it to check security signals without exposing your data.

HOW WE HANDLE DATA

Security Details You Can Check

Our approach starts with purpose: account records support access, wallet matching, security checks and requests made under this Privacy Policy.

Account creation

We use the details entered during account opening to create your account, send access-related prompts and connect your phone verification with the correct account record.

Wallet matching

A DANA, OVO, GoPay or QRIS reference helps us match a transaction status to your account. Bank transfer and virtual account records follow the same purpose.

Cookie controls

Cookies can keep a session working and help us understand access errors. You can manage them through your browser settings, although some account steps may then need repeating.

Device security

We may compare device and browser signals with account activity when a login looks unusual. This helps us review access without treating a device signal as your identity alone.

Record retention

We retain account, wallet and support records only while their stated purpose or a legal requirement remains. A retention request can be raised through the account help route.

Your requests

You can ask for a copy, correction or removal of eligible personal data. Include your account contact and request type so we can verify ownership before making a change.

Privacy Policy Answers For stm123 Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or returning from a mobile device. We explain account data, wallet references, cookies, access requests and the contact route in direct terms. If your question concerns a specific DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, mention that payment rail when you contact support. Access and eligibility depend on local law.

It covers data collected during account creation, phone verification, login, wallet activity, cookie use, device access and support requests. It also explains retention, security checks and how you can ask for access, correction or removal of eligible personal data.

Phone verification links the account to a contact step and helps us check that an access request comes from the account holder. We use the result for account security and access handling, not as permission to collect unrelated phone details.

Yes. The Privacy Policy covers transaction references and status connected with DANA, OVO, GoPay and QRIS. Bank transfer and virtual account records are covered too, because we need those references to match wallet activity and respond to account questions.

Cookies can keep your session available, remember necessary account steps and help us identify access errors. You can manage cookies in your browser settings. If you remove required cookies, login or phone verification may need to be completed again.

You can ask for a copy of eligible account, wallet or support records through the account help route beside the cashier path. We may verify your account contact first, then explain which records can be provided under applicable local requirements.

Send a correction or removal request through account support and identify the record you want changed. We check account ownership before acting. Some details may need to remain for security, transaction matching or a legal requirement, and we will explain that reason.

Access and eligibility depends on local law. Where local law permits, you can use the account path from a supported phone or browser and reach the relevant lobby. Our Privacy Policy still applies when you use DANA, OVO, GoPay, QRIS or bank rails.