Reference

esa4d Privacy Policy for Your Account

The esa4d Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, browse Live Roulette or Wolf Gold, and use DANA…

Account accessWallet recordsCookie choicesSupport requests
esa4d esa4d Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Beside Your Account

A clear contact route helps when a privacy request and an account issue arrive together. We ask for enough detail to locate your record, but not for a wallet password or an unnecessary payment credential. From Semarang or elsewhere in Indonesia, use the support route shown on our site and mention the relevant account step, device path or wallet reference so we can direct the request correctly.

Team online

Account access

If your phone verification or mobile-browser login does not match, contact support through the route shown on the site. We use the account details you provide to check identity before discussing stored records.

Wallet record

For a DANA, OVO, GoPay or QRIS reference connected with your account, send the receipt number and date through the listed support path. Do not send a wallet PIN or full password.

Privacy request

To ask about access, correction or removal, state the request clearly and include your account phone number. We may ask for an account check before changing personal details or releasing a copy.

HANDLING DETAILS

What Happens to Your Personal Data

We keep the policy practical: each data use connects to an account action, security check, payment match or support need.

Registration details

We collect details entered during account creation, including your phone number and chosen access credentials. This lets us link verification to one account and identify the correct record when you contact us.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be retained for reconciliation. We use transaction identifiers to match a request, not to request your private wallet PIN.

Cookies and sessions

Cookies and session markers help keep your login path connected while you move from the account page to the lobby. Your browser settings can remove or restrict them, although some account steps may then need repeating.

Device signals

We may record browser type, device signals and security events when you sign in. Comparing a new mobile-browser session with earlier access helps us identify unusual account activity before support changes account details.

Retention period

We retain records only for as long as they support account operation, payment reconciliation, security checks or a documented support request. When a record is no longer needed, we remove it or separate it from direct account identity.

Changes and contact

You can ask us to correct account data, explain a stored record or change available contact details through the site support route. We may verify ownership before making an update to protect your account.

Privacy Policy Answers for esa4d

These Privacy Policy answers focus on the account, device and wallet questions you are most likely to ask before opening access. If your situation is unusual, send the account step and relevant reference through the available support route so we can assess the request against this policy.

It covers data used for account creation, phone verification, login sessions, mobile-browser access, wallet references, cookies, security checks and support requests connected with esa4d services where local law permits.

No. We use payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account to match account activity. Never send a wallet PIN or account password through support.

Phone verification connects the access request to the correct account and helps us protect records when a new browser or device is used. It also supports account changes requested through our contact path.

Cookies and session markers keep your login path connected between account pages and the lobby. You can restrict them in your browser, but repeating verification or losing a session may follow.

Yes. Contact us through the support route displayed on the site, identify your account phone number and state whether you want access or correction. We may confirm ownership before responding.

We keep records while they support account operation, payment reconciliation, security checks or a documented request. After that need ends, records are removed or separated from direct account identity.

The policy describes our handling for Indonesian account access, including requests from Semarang and Makassar. Availability and eligibility depend on local law, so access is provided only where local law permits.