Reference

emera4d Privacy Policy For Your Account

emera4d Privacy Policy sets out what we collect when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataCookie choicesWallet detailsSecurity steps
Explore Our Lobby Read FAQ
emera4d emera4d Privacy Policy For Your Account
CONTACT THE TEAM

Three Clear Routes For Privacy Help

A privacy question should not disappear inside a general account request. We keep the contact path close to the same account and cashier areas you already use, so you can point us to a login record, wallet reference or device issue without sending unrelated details. Your request may involve access, correction, deletion where applicable, cookie choices or a question about retention.

Team online

Account data request

Ask us to locate the account details connected with your phone verification or sign-in path. Include the account identifier you can safely provide, and we will use it to narrow the request before discussing any record.

Wallet status query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, send the relevant reference and date through our support path. We use those details to check a status without asking you to share a wallet password.

Password Reset Help

If a privacy request follows a lost login, start with Password Reset Help and then tell us which account detail needs attention. We separate identity checks from the request itself so a reset does not expose unrelated records.

DATA CONTROL POINTS

Six Privacy Checks Inside emera4d

We treat privacy as an operating task, not a footer link. The controls below describe how we handle account records, browser activity, wallet references and security events in day-to-day service work.

Data we collect

We may receive phone verification details, sign-in events, device and browser signals, cookie selections, support messages and payment references. For QRIS or a wallet route, we use the transaction status needed to connect the request to your account.

Cookie choices

Cookies can keep a session active, remember a language or help us detect a broken mobile path. Your browser controls can clear or restrict them; doing so may require another sign-in and can affect account continuity.

Account security

Phone verification, sign-in records and device signals help us assess unusual access before account details are discussed. Never send a wallet PIN or password in a support message, including when asking about DANA or GoPay.

Retention approach

We keep records for as long as they serve account security, transaction reconciliation, support handling or a legal need. When a record no longer serves a valid purpose, our handling follows the applicable retention requirement.

Who to contact

Use our account support path for a copy request, correction, deletion question or cookie concern. Adding the affected sign-in date, device path or payment reference helps us identify the right record without collecting extra personal details.

Requesting changes

You can ask us to correct an account detail or explain how a record is used. We may need to confirm that the request comes from the account holder before changing, disclosing or removing data.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear most often before an Indonesian account is opened or checked. We keep the examples practical, from phone verification and cookies to DANA references and a mobile sign-in. If your question is not covered, use the account support path and avoid sending passwords, wallet PINs or unrelated personal details.

It covers data linked to your account path, including phone verification, sign-in activity, device and browser signals, cookies, support messages and wallet references. It also explains retention, security checks and how to ask for access or a correction where local law permits.

We may record a DANA or QRIS transaction reference, amount status and related account event so a cashier request can be reconciled. We do not ask you to send a wallet PIN or password, and the exact handling depends on the payment route.

Your phone number supports account creation and the verification step before access. We may connect verification events with sign-in security and support requests, so we can distinguish an account-holder request from an unverified message.

Yes. Send a correction request through the account support path and identify the record you believe is wrong. We may confirm your account identity before making a change, and the available action depends on local law and the record's purpose.

Cookies can support a remembered session, language setting or device troubleshooting. You can restrict or clear them through your browser, although that may sign you out or remove saved preferences. Our Privacy Policy explains which cookie purpose is connected to each setting.

We retain account, support and payment-reference data only while it supports security, reconciliation, service handling or an applicable legal requirement. The period can differ by record type, so you can ask us to explain the retention basis for a specific item.

You can ask what account data is connected with your phone verification, device path, support message or wallet reference. We may need an identity check before responding, and access or eligibility depends on local law and any lawful retention requirement.

Related Pages

emera4d Indonesia Live Roulette Grand About Us FAQ Pekanbaru Casino Lobby