Reference

ecd38 n4d Privacy Policy Explained

ecd38 n4d Privacy Policy shows what we collect when you open an account, sign in, use DANA or QRIS, and contact our support route.

Account dataWallet recordsCookie choicesAccess requests
Browse the lobby Read FAQ
ecd38 n4d ecd38 n4d Privacy Policy Explained
CONTACT THE DESK

Where To Ask About Privacy Policy

A clear contact route matters when you want to understand or change account data. Start from the support path inside your signed-in account and include the email or phone detail connected to…

Account support path Open the support area after signing in and select the privacy request option. We use your account details to locate the correct record, then explain the next verification step before discussing account data.
Wallet status request If a DANA, OVO, GoPay or QRIS record looks unfamiliar, send the visible reference and date through the account support route. We can check the stored transaction status without asking for your wallet password.
Access or correction Ask us to provide, correct or clarify personal data connected with your account. Include the specific field or record in question; we may verify phone access before making a change where local law permits.
DATA PRACTICES

Six Privacy Policy Commitments

We keep the Privacy Policy practical by linking each explanation to an account action you can recognise.

Account collection

We collect the details needed to create and maintain your account, including contact information and phone verification results. Sign-in history can help us identify an access issue without asking you to repeat the full account process.

Device signals

Your mobile or desktop browser may send device type, language, session and security signals. These details help separate a normal return to the lobby from an unusual sign-in, especially when your phone changes networks.

Cookie controls

Cookies can keep a session active, remember selected settings and show whether a page loads correctly. You can adjust cookie controls in your browser, although turning some storage off may require another sign-in.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference, amount and status records. We use them to match account actions and support checks, not to request your private wallet password.

Security handling

Phone verification and sign-in checks help protect account access. Keep your password, one-time code and wallet credentials private; our support route should not need those secrets to locate a payment or privacy request.

Retention requests

We retain records for account operation, security checks, disputes and legal duties for as long as those needs require. You can ask what we hold, request a correction or ask about deletion, subject to applicable law.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the account actions people ask about most: opening access, checking wallet records, using a phone, changing stored details and contacting us. They are written for the ecd38 n4d account path in Indonesia and should be read with the full policy above. Where a request affects a legal or security record, the result depends on local law.

The Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can ask about, correct or delete data where local law permits.

We collect the details needed for account creation and access, such as contact information and phone verification results. We may also record browser or device signals, session events and account actions so we can protect sign-in and respond to a support request.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match a wallet action to your account; we do not need your wallet password.

Sign in, open the account support area and send an access request that identifies the email or phone detail on your profile. We may verify phone access before responding, and the records we can provide depend on local law and security requirements.

You can request a correction through the signed-in support path. Name the field that appears wrong and provide the accurate replacement. We may ask for an account check before changing it, particularly when the detail is linked to phone verification or wallet status.

We keep account, security, payment-reference and support records for the period needed to operate the account, investigate disputes, protect access or meet legal duties. You can ask about a specific record; deletion or restriction depends on local law and the reason for retention.

Use your mobile browser settings to inspect or remove cookies and similar storage. The Privacy Policy explains that session storage can support sign-in and page settings. If you clear it, we may ask you to sign in again when you return to the account.

Related Pages

ecd38 n4d Indonesia Access guide About Us LinkAja Instant Payout Live Roulette Diamond