Reference

merdeka777 Privacy Policy for Your Account

Account clarity comes first: the merdeka777 Privacy Policy explains how we handle your phone verification, mobile browser activity and wallet details when you use DANA or QRIS.

Account dataWallet detailsCookie choicesAccess requests
merdeka777 merdeka777 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Privacy

A clear contact path helps when you want to ask what we hold or correct an account detail.

Account support desk Open the support desk from your account path and ask for a copy, correction or explanation of personal data connected with your verified phone number.
Wallet record check For DANA, OVO, GoPay or QRIS questions, send the transaction reference and wallet name so we can connect your request with the correct account record.
Access concern If a phone verification step blocks account access, tell us which device and browser you used; this gives our support desk useful context without sharing your password.
DATA PRACTICE

Data Choices Across Wallet and Device

We keep this policy practical by tying each data use to an account task you can recognise. Phone verification supports account control, wallet references support payment matching, and browser signals help us…

Account data

We may hold your account name, verified phone detail and login events to maintain account access, respond to support requests and check that a request comes from the right account holder.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event with your account without treating the wallet number as a public profile.

Cookies

Our cookies can retain session settings and useful preferences on your browser. You can remove or block them in device settings, though some account steps may then need repeating.

Account security

Phone verification, login event checks and limited access to account records help us investigate unusual access. Never send your password or a full verification code through support.

Retention period

We keep records while they support an active account, a wallet reconciliation or a valid support request, then remove or separate them when they are no longer needed.

Changes and requests

Ask our support desk to access, correct or clarify your data. Include your verified phone detail, the requested change and a receipt reference when the request concerns DANA or QRIS.

Privacy Policy Questions From Indonesia

These answers address the Privacy Policy searches we hear most often before an account is opened. They explain the records connected with phone verification, local wallets, cookies and device access, while keeping the request path simple. If your situation is specific, use the support route above and avoid sending passwords or complete verification codes.

The merdeka777 Privacy Policy covers account details, phone verification, wallet references, cookies, device signals, support requests, retention and the ways you can ask us to access or correct a record.

We use phone verification to connect account access with the correct account holder, help investigate unusual login activity and handle privacy requests safely. Access depends on local law and the account path available to you.

Yes. The Privacy Policy explains that DANA and QRIS references may be used to match a wallet event or receipt with your account. We ask for only the details needed to locate that record.

You can contact our support desk with the phone detail verified on your account and ask which personal records we hold. We may need account checks before releasing details connected with your request.

Send the support desk the field that is incorrect, the requested correction and enough account context to locate it. For a wallet matter, add the DANA, OVO, GoPay or QRIS receipt reference.

On a mobile browser, cookies can remember session settings and preferences. You can clear or block them in browser controls, but login or phone verification may need to be repeated afterward.

We retain records while they support account access, wallet matching, security checks or an active support request. When a record is no longer needed, we remove it or separate it where appropriate.