Reference

agembet Privacy Policy for Your Account

The agembet Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Live Roulette or Aztec Gems, and use DANA, OVO…

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How Your Account Data Moves

agembet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers information supplied during account opening, including contact details and phone verification needed before account access. We also record operational events such as sign-in time, device type, page activity and payment status so we can identify a stalled wallet step or protect an

1
account from unusual access. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may appear in transaction records, while the payment provider handles its own data under its terms. We use this material for account administration, security checks, support replies and legal obligations that apply
2
where you access the service. Access and eligibility depends on local law. You can ask us about a specific record through the account help path, and we will explain the applicable handling or correction route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP ROUTE

Get Help With a Privacy Request

A clear contact route matters when your account record or wallet history needs attention. We keep privacy questions separate from ordinary lobby requests, so you can identify the record, device or payment reference involved. Use the account help path shown after sign-in, and include only the details needed for us to locate your request.

Team online

Account access

If you cannot sign in to send a Privacy Policy request, use the account help path and describe the phone verification step that stopped you. Do not send your password.

Wallet record

For a DANA, OVO, GoPay or QRIS question, include the transaction date and visible status rather than full wallet credentials. We use that reference to locate the relevant account event.

Data request

Ask for access, correction or deletion through the contact path attached to your account. We may need to verify account ownership before changing personal details or releasing a copy.

DATA CONTROL POINTS

What We Do With Your Details

We handle personal data according to the purpose connected to your account and the request you make.

Account opening

When you create an account, we use the submitted contact details and phone verification result to establish access. We do not ask you to place payment credentials in a privacy request.

Device activity

A phone or desktop session can create technical records such as browser type, access time and security signals. These help us recognise unusual sign-ins while you move from login to the lobby.

Cookie choices

Cookies and similar storage can remember session state and selected settings. Your browser controls can remove or restrict them, although some account-access steps may then need to load again.

Wallet references

A payment record may show a rail such as QRIS, DANA or bank transfer, plus status and timing. We use these references to reconcile account activity without treating them as your wallet password.

Retention timing

We keep records only for the period needed for account operation, security checks, support handling or legal duties that apply. The period can differ by record type and local requirements.

Changes and contact

To correct a name, phone detail or other account record, contact us through the account help route. We verify ownership first, then confirm whether the requested change is available.

Privacy Policy Questions Answered

These answers address the privacy searches we expect from an Indonesian account holder before opening access. If your case involves a particular sign-in, device or wallet event, use the account help route and identify the relevant record without sharing secret credentials.

It covers account details, phone verification, device and session records, cookies, wallet references, support requests, retention and requests to access or correct your personal data.

We use the verification result to establish that the account access step belongs to you and to help detect unusual sign-ins. It is handled for account administration and security purposes.

Yes. The policy explains how account-side references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may be used to match status and support requests.

You can request a correction through the account help path. Tell us which field is wrong, and we may verify account ownership before changing the record or explaining why a change cannot be made.

Send an access request through the contact route linked to your account. Include the relevant account detail or date, but never include your password or complete wallet credentials.

Cookies or similar storage can retain session state and settings when you use a mobile browser. Browser controls can restrict them, but login and verification steps may need to load again.

Yes. Account access and eligibility depends on local law. We apply the rules relevant to your location, and our policy contact route can explain the process for a location-specific request.

agembet Privacy Policy for Your Account

Get Help With a Privacy Request

Account access

Wallet record

Data request

What We Do With Your Details

Account opening

Device activity

Cookie choices

Wallet references

Retention timing

Changes and contact

Privacy Policy Questions Answered

01 What does the agembet Privacy Policy cover?

02 Why does agembet collect phone verification details?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I ask agembet to correct my personal data?

05 How do I request a copy of my agembet data?

06 How does the Privacy Policy handle cookies on mobile?

07 Does access to agembet depend on local law?

Related Pages