Reference

Privacy Policy For Your stm888 Account

Our Privacy Policy explains how we handle the details connected with your stm888 account, from phone verification to wallet status when you use DANA, OVO, GoPay or QRIS.

Account dataWallet checksCookie choicesPolicy requests
stm888 Privacy Policy For Your stm888 Account
PRIVACY HELP

Get Clear Answers About Your Data

A direct support path helps you resolve Privacy Policy questions without guessing which account screen to use.

Account request Use the account support route when you want a copy of personal data, a correction to your phone details or help understanding a verification record. We may ask you to confirm account ownership before discussing anything connected with your stm888 profile.
Wallet question If a DANA, OVO, GoPay or QRIS reference appears in your account history, include its date and status in your message. We can then connect the privacy question to the relevant payment event without requesting unrelated personal details.
Access concern For a login or device concern, describe whether you used a mobile browser or desktop browser and what changed. We use this context to check account security records and explain the Privacy Policy step that applies to your request.
DATA HANDLING

What Your Privacy Policy Covers

We keep the practical parts of our Privacy Policy close to the actions you take on the site.

Account details

We may handle the phone number and verification details you submit when opening or entering your account. These details help connect the right person to the right profile. Ask us to correct a mistake, and we will explain the ownership check required before making a change.

Payment references

A DANA, OVO, GoPay or QRIS transaction can leave a reference, amount status and time connected with your account event. We use that record to trace a receipt or wallet question. The Privacy Policy does not turn a payment reference into permission to access your wallet.

Cookies

Cookies and similar browser storage can keep a session active or remember a setting on your mobile browser. You can clear browser data through your device settings, though doing so may require another account sign-in. Ask support which cookie category relates to your question.

Account security

We check sign-in patterns, device context and phone verification events to help protect account access. If a login looks unusual, we may request another ownership step before sharing or changing personal data. Never send a password or wallet PIN in a Privacy Policy request.

Retention periods

We keep different records for different periods because an account detail, a security event and a payment reference serve different purposes. The applicable period depends on the record and local requirements. Contact us with the record type, and we will explain the retention basis available to you.

Change requests

To request access, correction or removal, send the account phone number, the requested action and enough context to identify the record. We first confirm ownership, then respond with the available action or the reason a record must remain where local law permits.

Privacy Policy Answers For stm888

These Privacy Policy answers cover the searches we expect from someone deciding whether to open an account. They explain what may be collected, how wallet references are handled, what happens on a mobile device and how to ask for a change. If your situation is not listed, use the account support route with the relevant record details.

The stm888 Privacy Policy covers account details, phone verification, browser cookies, device and sign-in records, wallet references and support requests. It also explains why we use those records, how retention works and how you can ask for access, correction or removal where local law permits.

Yes. The Privacy Policy covers references created when your account uses DANA, OVO, GoPay or QRIS. We may use the reference, status and time to trace an account event or receipt question. We do not ask for your wallet PIN in a privacy request.

You can request access to personal data connected with your stm888 account through the support route. Include your account phone number, the record you want and the reason for the request. We confirm account ownership first, then explain what can be provided.

Send a Privacy Policy request stating the incorrect detail and the replacement you want recorded. A phone number, verification detail or profile field may require an ownership check before we change it. We will explain the next account step and any local-law restriction.

Our Privacy Policy covers cookies used for sessions and browser settings. You can clear them through your phone browser controls, but clearing storage may sign you out and remove saved choices. If a cookie still appears after clearing, contact support with your device path.

You can ask us to remove eligible account data through a Privacy Policy request. We confirm ownership and check whether a record must remain for security, payment tracing or a legal duty. Where local law permits, we explain the removal step and its effect.

The policy can be read as a public page, but account access and some data rights depend on local law. If you are in Indonesia, we assess the request against the rules that apply to your location and tell you which action is available.