Reference

moga4d Privacy Policy For Your Account

Our Privacy Policy shows how moga4d handles the details connected with your account, wallet records, device session and support requests.

Account dataWallet recordsCookie choicesSecurity steps
moga4d moga4d Privacy Policy For Your Account
CONTACT ROUTES

Where To Ask About Privacy Choices

A clear contact path matters when you want to ask about your Privacy Policy rights or an account record.

Account privacy path Use the support route beside your account area for a Privacy Policy question.
Wallet record check For a DANA, OVO, GoPay or QRIS record, share the transaction reference shown in…
Data change request Ask us to correct an eligible account detail through the same support path.
HANDLING PRACTICES

Account Data Practices At moga4d

We treat the Privacy Policy as an operating rule, not a page kept apart from daily account work. Phone verification, wallet matching, cookie controls and sign-in checks each have a defined purpose.

Data collection

We may collect your account contact detail, phone verification result, device session markers and payment reference. These fields help connect a request to your account and resolve a specific account or wallet record.

Cookie controls

Cookies can keep a signed-in session connected and help us recognise repeated device activity. Your browser settings provide a way to restrict cookies, although some account pages may then need another sign-in.

Account security

Before account access or a sensitive record change, we may check the phone detail linked to your account. Never share your password, wallet PIN or one-time code through a support request.

Retention timing

We retain account, payment-reference and support records only for the period needed for the stated service, account history or applicable legal duty. A removal request is assessed against those requirements.

Who can help

Our account support route handles questions about the Privacy Policy, stored details, cookies and wallet references. State the topic clearly so we can send the request to the relevant handling team.

Requesting changes

You can ask to view, correct or remove eligible data by using the account support path. We may verify your phone and ask for enough context to avoid changing another account's record.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account steps most relevant to an Indonesian customer. We focus on data access, wallet references, cookies, device sessions and requests for changes, so you can decide what to provide before opening or using an account where local law permits.

It covers account details, phone verification, device and cookie data, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect account access and sensitive changes with the correct account. We may use it when you ask about stored data or request a correction to an account detail.

Yes. The Privacy Policy explains how we use DANA and QRIS references to match an account request. We do not need your wallet password or PIN for that matching step.

You can ask through the account support path for eligible account data connected with your details. We may confirm your phone and ask which records you want us to locate.

Send a clear request through account support, naming the detail or record involved. We assess correction or removal against account handling needs and any applicable legal duty before responding.

Cookies can keep your sign-in session connected and help recognise device activity. You can restrict them in your browser, but some account pages may require another sign-in afterward.

Yes. Account access and related data handling depend on local law. We apply the Privacy Policy where local law permits and ask you to check your own eligibility before continuing.