Reference

eppgbm Privacy Policy In Plain English

eppgbm Privacy Policy explains what we collect when you open an account, enter the lobby, or connect DANA, OVO, GoPay and QRIS, and why each detail is needed.

Clear data purposesWallet details explainedPhone access controlsIndonesia policy path
Browse Our Lobby Read FAQ
eppgbm eppgbm Privacy Policy In Plain English
PRIVACY HELP

Three Ways To Request Account Help

A clear contact path matters when a privacy question appears beside a login or wallet issue.

Account access request Ask us to confirm which account details are linked to your phone verification step. We may request matching account facts before responding, because a privacy reply should reach the account holder rather than another person using the same device.
Wallet record question For DANA, OVO, GoPay or QRIS questions, include the transaction date, amount shown in your account and payment reference. We use that narrow set to trace status, while you should keep wallet passwords and one-time codes private.
Correction request If your phone, name or account detail needs correction, send the requested change through our support path after signing in. We compare the request with your account step and may ask for verification before changing a record.
DATA CONTROLS

How We Protect Your Policy Choices

Our privacy work follows the account journey rather than collecting details without a purpose. We separate sign-in, wallet status and support records where practical, limit account changes behind verification, and use device…

Account data

We may hold your phone contact, verification result, account settings and sign-in history so we can open the correct account and respond to access requests. We use the details for account operation, payment matching and security checks connected with your eppgbm profile.

Device signals

A mobile browser can send device type, browser details, language setting and basic access times. We use these signals to keep a session consistent and flag unusual sign-ins; they do not give us your device passcode or wallet password.

Cookie choices

Cookies can keep your sign-in flow, remember selected settings and help us understand whether a policy page loads correctly. You can adjust cookie controls in your browser, although removing them may require you to repeat account verification or preference steps.

Payment matching

When you use DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI transfer routes, we retain the reference and status needed to reconcile the account entry. We do not ask you to provide a wallet PIN, card secret or one-time code.

Security checks

Phone verification, sign-in records and device signals help us detect an account access attempt that does not match your usual pattern. If a check pauses access, use the support route and provide the account detail requested there, not a private wallet credential.

Retention requests

We keep records only while they support account operation, payment reconciliation, security or a legal requirement. You can ask what remains linked to your account, request a correction or ask about removal; we will explain any record that must stay for a stated reason.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain the practical difference between account data, device signals and payment references, along with the route for correction or access requests. If your question is not covered, use the support path attached to your account area and mention the exact record you want us to check.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. We use those records for account access, payment matching, security and legal duties. Access depends on local law, so your location may affect whether the service is available.

Your phone number supports the account access step and helps us connect a verification result to the correct profile. It can also help us investigate a sign-in question. We do not need your DANA, OVO or GoPay wallet password for this process.

Yes. It covers the payment reference, selected rail and status needed to match a DANA, OVO, GoPay or QRIS entry with your account. For bank transfer or virtual account use, we may retain the reference and reconciliation result, not your private banking password.

We may receive your browser type, device category, language setting and basic access time when you use a mobile browser. These signals help keep the login path consistent and identify unusual access. They do not provide access to your device files, passcode or wallet credentials.

Use the support route connected to your signed-in account and describe the record you want to access or correct. Include the phone contact or payment reference that helps us locate it. We may verify your identity first, then explain the available response and any required retention.

The period depends on why a record exists. We retain account, payment and security records while they support operation, reconciliation, fraud prevention or a legal duty. You can ask us to explain what remains linked to your profile and why a particular record cannot yet be removed.

Yes. Browser controls let you adjust or remove cookies used for sign-in continuity, saved settings and page performance checks. Removing them may make you repeat verification or preferences. For a specific cookie question, contact support from your account path and tell us which device and browser you use.

Related Pages

eppgbm Indonesia eppgbm Casino Badminton Indonesia Open Bet Java Treasure Slots Access guide