Reference

stm55 Privacy Policy For Your Account

Our Privacy Policy explains how we handle the details you provide when you open an stm55 account, verify your phone, enter the Live Casino lobby or connect DANA…

Account dataWallet detailsDevice controlsPolicy requests

Browse Our Lobby Read FAQ

How QRIS Data Enters Our Policy

stm55 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details needed to create and maintain your account, including your name, phone number, verification result, login records and selected wallet status. When you use DANA, OVO, GoPay or QRIS, we receive payment references and status details needed to match an instruction

1
with your account; we do not need your wallet PIN. Bank transfer and virtual account records can include a bank reference, amount and processing status. Device type, browser data, IP address and session timestamps help us detect unusual login activity and keep the account path working
2
on mobile. We use these records for access, payment reconciliation, support and security, then retain them only as needed for those purposes or where local law permits. Eligibility for account access depends on local law. You can request clarification through our support path before opening an
3
account or while signed in.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT WHEN NEEDED

Privacy Help Beside Your Account Path

A clear contact route matters when a privacy question is connected to login or wallet status. We can help you identify which record is being discussed, explain a payment reference, or route a request to update account details. Send your request through the account support channel and include the phone number on your account, the issue category and any relevant reference; never send a wallet PIN or full password.

Team online

Account support

Use the support channel from your signed-in account to ask about stored details, phone verification or a correction request. We may ask for account ownership checks before discussing personal records.

Payment reference

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference and date. We use those details to locate status without asking for your wallet PIN.

Access concern

If a login or device change looks unfamiliar, tell us through account support and stop sharing access codes. We can review the session path and explain the next account-security step.

ACCOUNT DATA PRACTICE

Security Details From Login To Retention

We keep this policy practical by linking each data use to an account task: access, verification, payment matching, security or support.

Account creation

When you open an account, we use your submitted contact details to create the profile and send the phone-verification step. A correct number helps us connect later support requests to the right account.

Phone verification

The verification result confirms that the phone path belongs with the account request. We record the result and related timing, not your private messages, so access checks can be completed without collecting unrelated content.

Cookie choices

Cookies and similar device records help keep a signed-in session, remember a selected language or detect repeated failed access. You can manage browser permissions, although some account functions may then require another login.

Device security

Browser type, device signals and session timestamps help us compare a familiar login with an unusual one. On mobile, this supports the path from login to the lobby without reading files, photos or contacts.

Retention timing

We retain account, payment and security records for the period needed to provide access, resolve a request, protect accounts or meet applicable legal duties. When a record is no longer needed, our process removes or separates it.

Change requests

You can ask us to correct contact details, explain a stored record or review a deletion request through account support. We check account ownership first and tell you if a legal or security reason limits the change.

Privacy Policy Questions For stm55

These Privacy Policy answers address the searches we expect before an Indonesian customer opens an account. They explain what we collect, how wallet references work and how to reach us about a personal-data request. If your situation is not covered, use account support with the smallest amount of detail needed to locate the record.

It covers account details, phone verification, login and device records, cookie use, payment references, support requests, retention and change requests. It also explains how DANA, OVO, GoPay, QRIS and bank-transfer status can be linked to an account without collecting a wallet PIN.

We may collect the contact details you submit, your phone-verification result, login events, device and browser signals, and account activity needed for security or support. We do not ask for unrelated files, photos or contacts to complete the account path.

No. For DANA, OVO, GoPay and QRIS, we use payment references and status information to match an instruction with your account. Your wallet PIN and private wallet credentials should remain inside the relevant payment service and should not be sent to support.

Contact us through the signed-in account support channel and state which detail needs correction, such as a phone number or profile field. We first check account ownership, then confirm the action or explain why a legal or security reason affects the request.

Cookies and device records can keep your login session active, remember a selected setting and help identify unusual access. You can change cookie permissions in your mobile browser, but turning them off may require repeated login or limit parts of the account path.

We retain records while they support account access, payment matching, security or an open support matter, and for any period required by applicable law. After that need ends, records are removed or separated through our retention process where local law permits.

Yes, it describes the data path for Indonesian account requests and local wallet references, including DANA, OVO, GoPay and QRIS. Account eligibility and access depends on local law, so you should check the applicable position before opening or using an account.

stm55 Privacy Policy For Your Account

Privacy Help Beside Your Account Path

Account support

Payment reference

Access concern

Security Details From Login To Retention

Account creation

Phone verification

Cookie choices

Device security

Retention timing

Change requests

Privacy Policy Questions For stm55

01 What does the stm55 Privacy Policy cover?

02 What personal data does stm55 collect when I open an account?

03 Does stm55 see my DANA or QRIS wallet PIN?

04 How can I request a correction under the Privacy Policy?

05 How does stm55 use cookies on my phone?

06 How long does stm55 retain account and payment data?

07 Does the Privacy Policy apply to Indonesian account access?

Related Pages