Reference

amdbet Privacy Policy for Your Account

Clear privacy choices start with knowing what we collect and why. This amdbet Privacy Policy covers account details, phone verification, device signals and wallet records connected with DANA…

Account clarityWallet recordsDevice controlsContact steps

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

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

Our Privacy Policy applies when you create an account, complete phone verification, sign in from a mobile browser or use a wallet route. We may receive your contact details, account activity, security events and transaction references needed to match a DANA, OVO, GoPay, QRIS, bank transfer

1
or virtual account record to the right account. We use these records to process requests, detect unusual sign-in activity, maintain account security and respond to support questions. We do not ask for a wallet password through support. Where access or eligibility is discussed, it depends on
2
local law. You can ask us which records we hold, why they are used and how long a category is retained through the contact path below.

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

CONTACT ROUTES

Get Privacy Help Near Your Account

A direct support route helps you handle a privacy question without repeating your account story. From Medan or elsewhere in Indonesia, open the support contact path while signed in and include your registered phone number, request type and any relevant transaction reference. We use those details to locate the correct record, and we may ask for an account check before changing private data.

Team online

Account requests

Use the signed-in support path to ask for account data access, correction or a copy of the records linked to your phone verification step.

Wallet questions

For DANA, OVO, GoPay, QRIS or bank transfer records, include the transaction reference only; never send a wallet password or full security code.

Device concerns

If a mobile browser or desktop sign-in looks unfamiliar, contact support from your account and mention the device path so we can check related security events.

CONTROL DETAILS

How We Handle Your Privacy Choices

Privacy work is part of each account step, from phone verification to a wallet status check.

Account records

We use your name, contact details and phone verification result to maintain the account record, answer account requests and connect…

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us reconcile a wallet event.

Cookies

Cookies can keep a session open, remember language or help detect an unusual sign-in.

Mobile signals

Our security checks may record browser type, device signals and sign-in time.

Retention

We retain each record only for the period needed for its stated purpose, account security, dispute handling or legal duties.

Changes and access

Ask to see, correct or question personal records through support.

Privacy Policy Questions About amdbet

These Privacy Policy answers address the account questions you may have before opening access or using a wallet route. They cover collection, cookies, verification, payment references, retention and contact steps. If your situation is not listed, send a signed-in request with enough detail for us to locate the relevant record.

It covers account details, phone verification, sign-in events, device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use the verification result to connect you with the correct account, protect sign-in activity and handle privacy requests. We do not ask you to disclose a private wallet password.

Yes. The Privacy Policy covers references needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity with your account, including receipt or status questions.

Yes. Use the signed-in support path, state that you are requesting account data and include your registered phone number. We may verify account ownership before releasing private records.

Send a correction request through support and identify the field that needs changing. We check the account first, then update the record or explain why a particular change cannot be made.

Cookies can retain a session, store language preferences and support sign-in security. You can adjust browser settings, but disabling cookies may require repeated login or limit account functions.

Retention depends on the record's purpose, such as account security, dispute handling or legal duties. Ask support which reason applies and whether a particular record can be removed.

amdbet Privacy Policy for Your Account

Get Privacy Help Near Your Account

Account requests

Wallet questions

Device concerns

How We Handle Your Privacy Choices

Account records

Payment references

Cookies

Mobile signals

Retention

Changes and access

Privacy Policy Questions About amdbet

01 What does the amdbet Privacy Policy cover?

02 Why does amdbet need phone verification data?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I request a copy of my amdbet data?

05 How can I correct details under this Privacy Policy?

06 What does amdbet do with mobile cookies?

07 How long are my records kept under the Privacy Policy?

Related Pages