Reference

Your Privacy Policy path on stk88

stk88 Privacy Policy shows what account details we collect, why we use them and how you can ask for a correction or deletion.

Account dataCookie choicesWallet recordsRequest path
stk88 Your Privacy Policy path on stk88
REQUEST HELP

Get help with a privacy request

A clear contact path matters when your account data needs attention. Send a request through the account support route and include the phone number or email linked to your profile, plus the specific change you want us to check. We may ask for an account step or verification detail before discussing private records. This protects your wallet history and keeps another person from requesting changes to your DANA, OVO, GoPay or QRIS details.

Team online

Account request

Use the support path connected to your account when you want a copy, correction or explanation of personal details. Include your registered contact and the exact Privacy Policy question, so we can locate the relevant record without asking you to send wallet credentials.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, tell us the date, amount reference and wallet name shown in your account. We can direct the request to the payment record without asking for your wallet PIN, password or one-time code.

Login privacy help

When a phone verification or login session blocks your request, explain which device path you used, such as mobile browser or desktop browser. We will keep the conversation focused on account access and privacy rather than asking for unnecessary personal details.

DATA CONTROL

Security choices behind your account

We keep the Privacy Policy practical by linking each promise to a handling step you can recognise.

Collection scope

We collect details you enter for an account, verification data used to protect access and transaction references created when you…

Cookie controls

Cookies and similar browser storage can remember session preferences and help us understand whether a login path is working.

Account security

Phone verification is checked before account access, and we may examine device or session signals when a login appears unusual.

Retention timing

We keep account, payment and support records only while they serve account operation, security, dispute handling or a legal duty.

Correction requests

If your phone number, email or account detail is wrong, contact support with the correction and a way to identify…

Policy contact

For a Privacy Policy question, state whether you want access, correction, deletion or an explanation of use.

Privacy Policy answers for stk88

These Privacy Policy answers address the searches we hear before an Indonesian account is opened. They explain the practical difference between account details, device data, cookies and payment references, while keeping the request path clear. If your situation is not covered, contact support from the account route and describe the exact record or access step you want us to check.

It covers personal details used for your account, phone verification, device and cookie data, payment references, support messages and retention. It applies to the website and mobile browser path from login to the lobby where local law permits.

We use phone verification to help confirm that the person requesting account access matches the account record. It can also help us investigate an unusual login without asking you to disclose a wallet PIN or one-time code.

Yes. The policy covers references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. These references help match a payment event to the correct account without giving us your private wallet credential.

Use the account support route and ask for access to your personal data. Include the registered phone number or email and describe the records you mean, such as profile details, phone verification or a payment reference. We may verify your identity first.

You can ask us to correct an inaccurate phone number, email or profile detail through support. Explain the error and the replacement value. We may confirm account ownership before making a change that could affect access or wallet history.

Start with your browser privacy controls to inspect or remove optional cookies and stored site data. If you need a record-level explanation, contact us with your device path, such as mobile browser or desktop browser, and the cookie question.

We retain records while they support account security, payment reconciliation, dispute handling or a legal duty. When those purposes end, we aim to remove or anonymise the data. You can ask support to explain the retention reason for a particular record.