Reference

Open gomu 10 slot Privacy Policy

DANA, OVO, GoPay and QRIS records stay connected to the account details you submit, while our Privacy Policy explains why we use each piece of data.

Clear data purposesCookie choicesAccount request pathIndonesia access context
gomu 10 slot Open gomu 10 slot Privacy Policy
REQUEST HELP

Switch to a clear privacy contact path

A privacy question should not get lost beside a wallet query, so we separate data requests from ordinary account assistance. Use the support route connected to your account and describe the request plainly, such as a copy of your data, a correction to your phone detail or a question about a QRIS receipt. We use the account step to confirm that the request concerns you before sharing or changing records.

Team online

Account data request

Open the account support path and ask for a copy of the personal data linked to your gomu 10 slot profile. We may ask for the phone verification step again so the response goes to the correct account holder.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include the date and receipt reference in your request. We check the cashier record against your account without asking you to send a wallet PIN.

Cookie assistance

When a mobile browser keeps an old session or removes a preference, contact support through the account route and name your device type. We can explain the cookie setting involved without requesting unrelated account data.

DATA HANDLING

Browse how our privacy controls work

Privacy is handled through practical account controls rather than broad promises. We limit staff access to records needed for account, payment or security work, and we use verification before discussing personal details.

Account security

Phone verification is part of account access, and sign-in events can be checked when a session looks unusual. We do not ask for your wallet PIN or full bank password when handling a privacy request.

Payment references

A payment record may show a rail such as BCA, BRI, Mandiri, BNI, DANA or QRIS and a transaction reference. We use those fields to reconcile status, while avoiding collection of credentials that belong only to your bank or wallet.

Cookie settings

Essential cookies help keep your account session active on a phone or desktop browser. Optional cookies may support page preferences or technical measurement, and your browser controls let you clear stored cookies or change permission.

Device signals

We may receive browser type, operating system, approximate connection data and security events from the device used to open the lobby. These signals help us investigate failed access without treating your device as a separate account.

Retention approach

We keep personal records for the period needed to provide account access, reconcile a wallet status, protect the service or meet a legal request. When a record is no longer needed for those purposes, our handling process removes or de-identifies it.

Change requests

You can ask us to correct inaccurate contact data, explain a data use or provide an available copy. Send the request through account support, include the relevant detail, and complete identity checks before we make a change.

Check Privacy Policy answers before access

These Privacy Policy answers focus on the questions that arise before opening an account from Indonesia. We explain the records connected to DANA and QRIS, how cookies behave on a mobile device, what happens when you ask for correction, and why phone verification may be required. If your question is not listed, use the account support path and refer to the exact policy topic.

It covers account details, phone verification, sign-in events, device signals, cookies, lobby activity used for technical purposes, and payment references. It also explains retention, security access, correction requests and the contact route available to you.

Phone verification helps connect an access request to the correct account and reduces the chance of another person receiving account data. We may repeat that check before sending a data copy or changing contact details.

We may retain a payment rail, receipt reference, status and related account match for DANA or QRIS activity. We do not need your wallet PIN for this process, and wallet credentials remain with the wallet provider.

Use the support route connected to your account and state that you want a personal data copy under the Privacy Policy. Include the account phone detail, complete the identity check, and tell us whether the request concerns access, payments or cookies.

Yes. Send a correction request through account support and identify the field that is wrong, such as a phone detail or account contact record. We verify the request before changing the record and may explain any retention reason.

Essential cookies can keep your sign-in session and selected page settings available while you move between the lobby and account area. Your browser can clear them or block optional cookies, although clearing essential cookies may require another sign-in.

Access and eligibility depend on local law. The Privacy Policy explains how we handle data if you open an account where local law permits; it does not change any legal restriction or remove the need to meet account checks.