Reference

merdeka77 Privacy Policy For Your Account

Our Privacy Policy shows how we handle the account details behind Live Casino, Wolf Gold and wallet activity, so you can decide what you share before opening an…

Clear data purposesWallet record contextAccess request pathCookie choices

Explore Our Lobby Read FAQ

How DANA And QRIS Data Is Used

merdeka77 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your payment record helps us match an account action with the wallet or bank route you selected. For DANA, OVO, GoPay and QRIS, we may receive transaction references, status details, account identifiers and confirmation time, while the payment provider handles its own records under its terms.

1
Bank transfer and virtual account references are used to reconcile the same account activity. We also use your contact details for account access, phone verification and requests about a receipt or stalled status. Device details, login time and security events help us detect unusual access around
2
Live Casino, Rocket Crash or other account areas. We do not describe payment data as permission for unrelated messages. Access depends on local law, and where local law permits, you can ask what we hold, request a correction or raise a concern through our support route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTE

Get Help With Privacy Requests

A clear support route matters when you want to check a record, correct an account detail or ask why a wallet status is attached to your profile.

Access request Ask us to locate the personal data connected with your account. Include your registered phone detail and we will use the account path to check the request before sharing records.

Wallet question For an OVO, GoPay, DANA or QRIS status question, provide the payment reference and approximate time. That lets our support route separate a receipt check from an account access issue.

Correction request If your name, phone detail or account record needs a change, tell us which field is incorrect and why. We may request a matching account step before applying the update.

DATA PRACTICE

Account Security Beside Wallet Status

We keep this policy practical by linking each data use to an account action: access, verification, payment matching, security or support.

What we collect

We may hold your account name, phone detail, login events, device signals and payment references. These fields help connect phone verification, wallet status and account security without treating every device detail as a profile fact.

Cookie choices

Cookies and similar device storage can keep an access session active and help us understand security events. You can manage browser cookie settings, although changing them may affect account access steps.

Account protection

Before account access, phone verification can connect the request to the registered account. We also examine login timing and device signals for unusual activity rather than relying on a password alone.

Payment matching

For a bank transfer, virtual account or local wallet receipt, we compare the reference with the account record. This supports status checks while keeping payment-provider data separate from unrelated account details.

Record retention

We keep personal data while it serves access, security, payment reconciliation, support or a legal duty. When a record is no longer needed, our handling follows deletion or de-identification procedures.

Request changes

You can ask for access, correction or deletion where local law permits. Use the support route with your registered phone detail, explain the request, and we may verify account control first.

Privacy Policy Questions For merdeka77

These Privacy Policy answers address the account, device and payment questions we expect before registration. They also explain how to reach us when a record needs checking, especially when your activity involves DANA, OVO, GoPay, QRIS or a bank transfer.

It covers account details, phone verification, device signals, cookies, payment references, security events, retention and requests to access or correct personal data connected with your account.

Yes. We may use DANA and QRIS references, status details and confirmation times to match a payment with your account. The payment provider keeps its own records under its terms.

We use the registered phone detail for account access, verification, support matching and security checks. It can help us locate your account when you ask about a record or payment status.

You can ask what personal data is connected with your account where local law permits. Send the request through our support route with your registered phone detail so we can verify account control.

We retain data while it supports access, security, payment reconciliation, support or an applicable legal duty. The period can differ by record type, and unnecessary data is removed or de-identified.

Yes, where local law permits. Tell us which account field or payment record is incorrect, or which data you want removed. We may complete an account verification step before acting.

Use the account help path and describe the concern clearly. Include a payment reference only when needed for a DANA, OVO, GoPay, QRIS or bank transfer record check.

merdeka77 Privacy Policy For Your Account

Get Help With Privacy Requests

Account Security Beside Wallet Status

What we collect

Cookie choices

Account protection

Payment matching

Record retention

Request changes

Privacy Policy Questions For merdeka77

01 What does the merdeka77 Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS records?

03 How does merdeka77 use my phone detail?

04 Can I request my personal data from merdeka77?

05 How long does the Privacy Policy keep my data?

06 Can I ask for a correction or deletion?

07 Who should I contact about a Privacy Policy concern?

Related Pages