Reference

maimun88 Privacy Policy for Indonesia Accounts

Andar Bahar, Starlight Princess and Rocket Crash sit behind one account path, so our Privacy Policy explains exactly what we collect when you create an account, open the…

Account dataWallet recordsCookie choicesSecurity checks
maimun88 maimun88 Privacy Policy for Indonesia Accounts
CONTACT ROUTE

Ask About Privacy Before Opening Your Account

A clear contact route matters when you want to understand a record or request a correction. Our support path connects privacy questions with the account and wallet context that created the record, so you can refer to a phone verification, QRIS receipt or device login without sending unnecessary details. Use the contact route displayed in your account area, and we will assess the request under applicable law.

Team online

Account privacy request

Use the account contact route to ask what personal details are linked to your login. Include your registered phone number only through the secure form, not in a public message.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and approximate date through the private support path. We use those details to locate the correct entry.

Access correction

If a device check or phone verification blocks account access, tell us which step stopped. We may request extra confirmation before changing personal details or restoring the account path.

SECURITY PRACTICE

What Our Privacy Process Does With Your Data

We separate ordinary account activity from security events so the Privacy Policy can be applied to a real account situation rather than a vague profile.

Account creation

When you create an account, we collect the phone and login details needed to identify your account path. Phone verification can be required before access, and we do not ask you to post those details publicly.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status with your account. We use the reference to resolve a record, not to describe unrelated activity.

Cookie controls

Cookies can remember session settings, measure page performance and support account security. You can adjust cookie controls through your browser, although blocking necessary cookies may affect login or policy access.

Device security

We may note device type, browser details and unusual login signals when you move from mobile to desktop. These checks help us question an unfamiliar session before account or wallet details are changed.

Retention period

We keep account, payment and security records only for the period needed for the stated purpose, account support or a legal requirement. When a retention need ends, records are removed or handled according to applicable law.

Changes and contact

You can ask us to access, correct or clarify personal details through the account contact route. We may verify ownership first, then explain the result, any limitation and the next available step.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the records created by local wallets, the device path used for login, cookie choices and the way you can contact us. If your situation involves a legal restriction, the outcome depends on local law and the details we can verify securely.

It explains how we handle account details, phone verification, wallet references, device signals, cookies, security events and contact requests connected with your use of our pages and account path.

Yes. The Privacy Policy covers payment references and status details created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records.

Device type, browser signals and unusual login patterns help us identify an unfamiliar session. We may use them before changing phone details, restoring access or discussing a wallet record.

You can send an access request through the private contact route shown in your account area. We may verify account ownership first and may limit a request where local law requires it.

Tell us which account detail is wrong through the secure contact path and explain the requested correction. We may ask for phone verification or another ownership check before making a change.

Use your mobile browser’s privacy or cookie settings to adjust permission. Necessary session cookies may still be needed for login, account security and access to the Privacy Policy page.

You can request removal through our account contact route. We first check identity, active account needs and legal retention duties, then explain which records can be removed and which must remain.