Reference

Open amorbet Privacy Policy Details

amorbet Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity in Indonesia.

Clear data purposesWallet activity contextPhone verification stepsPolicy contact route
amorbet Open amorbet Privacy Policy Details
CONTACT PATHS

Ask About Privacy Through Your Account

A direct support path helps you resolve a privacy question without guessing which team handles it.

Account request Use the account support route to ask for a copy of personal data, a…
Wallet question For a privacy question linked to DANA, OVO, GoPay or QRIS, provide the relevant…
Access concern If a login or device change looks unfamiliar, contact support from the account path…
DATA PRACTICES

Explore How We Handle Your Data

Privacy controls work best when they match the actions you take every day. We separate account details from the payment references needed to reconcile a DANA, OVO, GoPay…

Account records

We collect details needed to create and maintain your account, such as contact information, phone verification status and sign-in events.

Device signals

When you move between a phone and desktop browser, we may record device type, browser data, approximate session timing and…

Cookies

Our site may use cookies for session continuity, security checks and selected preferences.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event can create a reference used to match a receipt…

Retention periods

We keep personal data only for the period needed for the purpose described in this policy, account security, dispute handling…

Your requests

You can ask us to access, correct or delete eligible personal data, and you can ask why a particular record…

Find Privacy Policy Answers Before Access

These Privacy Policy answers focus on the questions you may have before creating an account or returning from a mobile device in Indonesia. We explain the records connected with login, phone verification, cookies and local wallet activity in plain terms. If your case is specific, use the account support path so we can check the relevant record without asking you to share sensitive credentials.

The amorbet Privacy Policy covers account details, phone verification, device and browser signals, cookies, security events and payment references. It explains why we use those records, how we retain them and how you can request access, correction or deletion of eligible personal data through the account support path.

Phone verification helps us connect account access with the contact detail you supplied and reduce unauthorised sign-ins. We record the verification status and related security event, not your private one-time code for support use. Keep codes private, and contact us if a verification action was not yours.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account reconciliation. We use those references to match a receipt, check wallet status or answer a support request. Do not send wallet PINs, passwords or one-time codes.

Use the signed-in account support route and ask for access to your personal data. Include the registered phone or email and describe the record you want, such as a login event or payment reference. We verify account ownership before sending details and explain any lawful restriction that applies.

You can request correction of inaccurate account details or deletion of eligible personal data through support. We first confirm that you control the account, then assess whether the record is still needed for security, dispute handling or a legal requirement. We explain the result rather than silently changing the record.

The policy mentions cookies used for session continuity, security checks and selected preferences. You can clear or restrict cookies in your browser settings, but essential session cookies may be needed for login and account navigation. Removing them can sign you out or require another account check on your device.

Yes, access and eligibility depend on local law. If a local restriction affects account access or a data request, we apply the relevant requirement and explain the practical effect where possible. Your support request can still ask what record was used and which part of the policy applies.