Reference

Privacy Policy For Your Account

erek erek 42 Privacy Policy explains what we collect when you create an account, sign in, use DANA or QRIS, and open titles such as Live Baccarat Grand.

Clear data purposesWallet records explainedAccount request pathCookie choices
erek erek 42 Privacy Policy For Your Account
PRIVACY CONTACTS

Get Privacy Help Through Your Account

A clear support route helps when you need an answer about account data rather than a lobby question. Sign in, open the account support path, and describe the request in plain English with the email or phone detail attached to your account. If wallet status is part of the question, include the DANA, OVO, GoPay or QRIS reference while hiding passwords and security codes. We use the submitted details to locate the right record and may ask for an account step to confirm that the request comes from you.

Team online

Account request

Use the support link inside your signed-in account to ask what data we hold, request a correction, or ask how a record is being used. Include your account contact detail so we can route the request without asking you to send a password.

Wallet query

For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and status only. We can compare the wallet record with the account ledger while keeping your wallet PIN, one-time code and full security credentials out of the message.

Access check

A request involving account access may require confirmation from the signed-in session or the contact method attached to your account. This step helps us avoid sending account data to another person, including when a device was recently changed.

SIX DATA CONTROLS

Six Controls Behind Our Data Handling

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

Collection

We collect the account details you enter, contact signals used for verification, device and session data, and transaction references connected…

Purpose

We use data to open and maintain your account, confirm sign-in steps, reconcile wallet status, identify unusual access, respond to…

Cookies

Cookies and similar storage can retain sign-in preferences, security settings and page choices on your device.

Security

We check account contact details and session signals before handling sensitive requests.

Retention

We keep account, security and payment-reference records for the period needed for account administration, dispute handling, security checks or a…

Your request

You can ask for access, correction, deletion assessment, purpose clarification or a copy of relevant records through the signed-in support…

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account and wallet questions we expect from people connecting in Indonesia. They explain what can appear in our records, how a request moves through the account path, and why a security check may be needed. If your question concerns a specific DANA, QRIS, device or sign-in event, include that context without sharing secret credentials.

The erek erek 42 Privacy Policy covers account details, contact and verification records, cookies, device and session signals, wallet references, support messages and activity records linked to the site. It also explains how to request access, correction, deletion assessment or clarification about a specific record.

No. Our Privacy Policy describes wallet references such as a transaction identifier, status, amount and time, not your DANA or QRIS PIN. Do not send a PIN, password or one-time code through support. We use the reference to reconcile account activity and investigate a related request.

Sign in to your account, open the support path, and ask for access to the records linked with your contact detail. State whether you need account, cookie, device, wallet or support data. We may verify the signed-in session before preparing a response or sharing a copy.

Yes. Send a correction request through the account support path and identify the field that appears wrong, such as a phone detail or wallet reference. We may ask you to confirm the account contact method before changing the record, especially after a device change.

Cookies can remember sign-in preferences, security settings and page choices on the browser or mobile device you use. You can remove them through browser settings. After removal, the account may ask you to sign in again or complete a fresh verification step.

The Privacy Policy does not assign one period to every record. We retain account, security, support and payment-reference data for the time needed for account administration, dispute handling, security checks or a documented request, then follow the applicable removal process.

Yes. Send the request through the signed-in support path and mention the account contact detail, device and relevant event without sharing secret codes. We assess requests for accounts connecting from Medan, Semarang or elsewhere in Indonesia where local law permits.