Reference

Privacy Policy For Your merdeka62 Account

Our Privacy Policy explains what we collect when you open a merdeka62 account, sign in from a mobile device, or check wallet status for DANA and QRIS.

Account dataWallet referencesDevice access
merdeka62 Privacy Policy For Your merdeka62 Account
CONTACT OPTIONS

Ask About Your Privacy Policy Rights

A clear contact route helps you ask what we hold, why we use it, or how to correct an account record.

Account request Use the account support path to ask for a copy of personal records linked…
Wallet query For a DANA, OVO, GoPay or QRIS reference, send the payment date, amount reference…
Access concern If a sign-in check or phone verification blocks a privacy request, tell our support…
DATA PRACTICES

Six Ways We Handle Your Account Data

We keep privacy work close to the account actions that create the record.

Account creation

When you open an account, we use the details you provide to create your profile and connect later sign-in activity…

Wallet references

DANA, OVO, GoPay and QRIS may return a reference or status connected with a payment request.

Cookies

Cookies and similar device storage can remember a sign-in state, protect an account session and keep a selected page available…

Mobile signals

A mobile browser can send technical signals such as browser type, operating system and session time.

Retention periods

We retain records for the period needed for account operation, security checks, support handling and payment reconciliation.

Change requests

To request a correction, access copy or deletion review, contact support from the account route and identify the record concerned.

Privacy Policy Questions About merdeka62

These answers cover the account and payment questions most often raised before someone opens an account. They describe the working policy in plain terms, including phone verification, browser storage, wallet references and requests for access or correction. If your situation involves a specific DANA, QRIS, bank transfer or virtual account record, contact support with the reference shown in your account.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references. It explains why we use each category, how retention works, and how you can ask for access, correction or deletion consideration.

No. Our account records may contain a DANA or QRIS transaction reference and status needed for reconciliation, but your wallet password remains with the wallet service. Do not send a wallet password in a support message or account request.

Phone verification helps connect an account request with the correct profile before private records are shown or changed. It can also help us investigate a sign-in from a new mobile browser. Access depends on local law and the route available to you.

Yes. Send a correction request through the account support path, identify the field or record that is wrong, and provide the registered phone number. We verify the request before changing data, especially where the record relates to GoPay, OVO or a bank transfer.

We keep records while they are needed for account access, security, support or payment reconciliation. A limited record can remain longer when a legal, dispute or transaction requirement applies. After the purpose ends, we remove or restrict the relevant data.

Cookies can preserve a sign-in session, protect the account route and remember page settings on your device. Browser controls let you clear or restrict them, but doing so may require another sign-in or interrupt a return from QRIS payment status.

Use the support path connected to your merdeka62 account and include the registered phone number plus the record involved. For a virtual account or bank transfer query, add the reference shown in your account so we can locate the correct entry.