Reference

moga4d Privacy Policy For Your Account

moga4d Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check DANA and QRIS status.

Clear data purposesCookie choicesAccount access controlsContact request path
moga4d moga4d Privacy Policy For Your Account
DIRECT HELP

Where To Ask About Your Account Data

A clear support route helps when a Privacy Policy question concerns login, wallet status, or a correction request.

Account data request Ask us to confirm the account details connected with your phone verification. We may request an account step before replying, so a private request is matched to the correct person rather than another moga4d account.
Wallet record check For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the transaction reference and date through support. We use the reference to check status without requesting your wallet password.
Cookie question If a cookie setting changes how your account page opens on mobile or desktop, contact support with the device path you used. We can explain the setting and the policy reason for that cookie.
CONTROL DETAILS

Six Controls Behind Your Privacy Policy

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Phone verification

Before account access, we use the phone verification step to connect your login with the account record you created. This reduces confusion when you change devices and gives support a specific account reference.

Device signals

A mobile or desktop login can create device and session signals for security checks. These signals help us identify unusual access patterns; they are reviewed for account protection, not used as a substitute for your consent choices.

Cookie controls

Cookies can retain a language, session, or preference setting on your browser. You can manage browser controls, although removing a required session cookie may interrupt the account page until you log in again.

Payment matching

We match DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references with the account action that created them. This lets support investigate a receipt or pending status without collecting unnecessary wallet credentials.

Retention review

We keep a record while its stated purpose, account security need, dispute handling, or legal requirement remains. When that reason ends, our handling follows the retention process described in this Privacy Policy.

Change requests

You can ask us to correct account details, explain a data use, or clarify access to a record. Include your verified phone number and request purpose so we can respond through the proper account contact.

Privacy Policy Answers For moga4d Accounts

These Privacy Policy answers address the account questions we expect before you open access. They cover collection, payment references, cookies, corrections, retention, and the local access rule. If your situation is not listed, use the account support contact beside the cashier path and describe the exact step that raised your question.

It covers account details, phone verification, device and session records, cookies, support messages, game activity references, and payment records from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains purposes, retention, security handling, and contact options.

We use your phone number for account creation and verification before access. It helps us match a login or support request to the right account, especially when you move between a mobile device and desktop. We do not ask for a wallet password.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account steps. We use those references to reconcile an account action or answer a receipt question without requesting full wallet credentials.

You can contact us through the account support route and request a correction. Include the phone number linked to your account, the detail you believe is wrong, and the reason for the request. We may verify account access before changing any record.

Cookies can remember a session, language, or browser preference. Removing optional cookies may change saved settings, while removing a required session cookie can interrupt the account page. Your browser controls let you manage cookies, and support can explain the related policy purpose.

We retain each record for the operational, security, dispute, or legal purpose stated in the Privacy Policy. When that reason ends, handling follows our retention process. A support request can ask why a particular record remains and whether correction or removal is available.

You can read this Privacy Policy from Indonesia, but account access and eligibility depend on local law. We provide access where local law permits. If a local restriction affects your account request, contact support and ask which policy or access condition applies.