Reference

edm303 Privacy Policy For Your Account

Our Privacy Policy explains how edm303 handles the account, device and payment data connected with your access to Live Baccarat Salon, local wallets and the wider lobby.

Account dataWallet recordsCookie choicesAccess requests
Explore The Lobby Read FAQ
edm303 edm303 Privacy Policy For Your Account
PRIVACY HELP ROUTES

Where To Ask About Your Data

A direct support route helps you ask about the Privacy Policy without describing your issue in a public channel. Start from the account help or contact path shown on edm303, then include the phone number or account identifier linked to your request. We use that step to locate the right record, check a wallet reference such as GoPay or QRIS, and avoid sending account data to the wrong person. Requests from Bandung and other Indonesian locations follow the same access process where local law permits.

Team online

Account help

Use the account help contact path when you want to ask what data is linked to your login, phone verification or device session. Include your registered contact detail so we can match the request before discussing account records.

Wallet record check

If your question concerns DANA, OVO, GoPay or QRIS, mention the relevant payment reference and approximate date. We can explain which transaction record we hold without asking you to share a wallet password, PIN or full bank credentials.

Security request

Use the security contact path if a sign-in, phone verification or device session looks unfamiliar. We may ask for account checks before changing access, helping us protect your data while we investigate the event.

HANDLING YOUR DATA

How We Apply The Policy

The Privacy Policy is practical at each account step: collection starts with the details you submit, use follows the service action you request, and retention is limited by operational or legal need.

Account collection

When you open an account, we collect the fields needed to create access and complete phone verification. A sign-in may add an IP address, device type and event time so we can recognise unusual access and respond to a security question.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep references that help match a request to your account. We do not ask you to place a wallet PIN or full banking password into an edm303 form.

Cookie controls

Cookies and similar storage can remember a session, preserve a selected language or help us understand which policy page was opened. You can clear or restrict them through your browser settings, though sign-in may need to be repeated.

Security checks

Phone verification, session checks and device signals help us assess whether an account request comes from the person who opened it. If a session appears unusual, we may pause the requested change until the account check is complete.

Retention period

We retain account, security and transaction records only for as long as needed for the stated service purpose, account protection or a legal duty. When a record is no longer required, our handling follows the removal or de-identification process available to us.

Change requests

You can ask us to correct inaccurate account data, explain a recorded payment reference or clarify how a cookie was used. Send the request through account help and identify the affected record; we may verify ownership before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and device questions you are most likely to have before opening edm303. Each answer stays focused on data handling, payment references, access requests and the steps used to protect your account where local law permits.

The edm303 Privacy Policy covers data connected with account creation, phone verification, sign-in, device sessions, lobby access, support requests and payment references. It explains our purposes, cookie handling, retention approach, security checks and the route you can use to request correction or clarification.

Yes. Our Privacy Policy includes references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use those references to match an account request, while wallet PINs and full banking passwords should not be sent to us.

We collect the registration fields you submit, the contact detail used for phone verification and technical events such as device type, IP address and sign-in time. These records help provide account access and identify unusual sessions; we use them for the purposes described in the Privacy Policy.

Start through the account help contact path and state which record needs correction, such as a phone detail or account identifier. We may ask you to confirm ownership before changing it. This process supports a clear Privacy Policy request without exposing your data in a public message.

Cookies or similar storage can keep a session active, remember a language choice and record that you opened a policy page. You can clear or restrict them in your browser settings. If you do, the account may ask you to sign in again or repeat a device check.

We keep payment references, login events and account records for the period needed for the stated service purpose, account security or a legal duty. The exact period can vary by record type and local requirements. When retention is no longer needed, we follow our available removal process.

You can ask through account help for a description of the data linked to your account, including phone verification, device events or a QRIS transaction reference. We verify the request before responding and apply any access or eligibility condition that depends on local law.

Related Pages

edm303 Indonesia About Us FAQ Account information Access guide