Reference

abadi126 Privacy Policy For Indonesia

Our Privacy Policy explains how we collect, use, protect and retain your account details when you access abadi126, including through a mobile browser in Bandung or elsewhere in…

Account dataWallet activityCookie choicesRequest support
abadi126 abadi126 Privacy Policy For Indonesia
REQUEST HELP

Three Ways To Ask About Privacy

A clear contact route helps you act on this Privacy Policy without guessing which team to reach.

Account access If you cannot pass phone verification or reach your account, contact support with your registered phone number and device type. We use those details to locate the correct account record without asking you to share a password.
Wallet records For a DANA, OVO, GoPay or QRIS data question, include the date, amount reference and wallet name shown in your account. We can then separate a payment-status request from a broader Privacy Policy request.
Privacy requests Ask us to access, correct or remove eligible personal data through the support contact shown on our site. We check account ownership first, explain any retention requirement, and reply through a channel linked to your account.
DATA CONTROL

What We Do With Your Account Data

This Privacy Policy is designed around the points where data enters the abadi126 account flow: sign-in, phone verification, payment selection, device access and support contact.

Account collection

We collect details needed to create and maintain your account, such as contact information, phone verification status and sign-in events. Choosing a lobby title like Aviator Crash Game does not require us to collect unrelated profile details.

Payment references

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may retain a reference, status and timestamp rather than your complete wallet secret. These records help match receipts and resolve a disputed account entry.

Cookies and devices

Cookies and similar device signals help keep a signed-in session working, remember a language or region choice, and identify repeated security events. You can manage browser cookie settings, though changing them may affect phone verification or account access.

Security checks

We use sign-in history, device signals and verification steps to notice unusual account activity. If a login or wallet status stalls, support may confirm ownership before changing access details or discussing payment-linked data.

Retention period

We keep personal data only for as long as needed for account service, security, dispute handling or duties that depend on local law. When a record is no longer needed, we remove it or separate it from direct account identification.

Your request route

You can contact us to ask what eligible data we hold, correct an inaccurate detail or request deletion where local law permits. Include your registered contact and the precise record, such as a QRIS reference or device entry.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder before opening access. They explain what data enters the account record, how payment references and cookies are handled, what happens when you change devices, and how to contact us. If your question concerns a specific DANA, OVO, GoPay or QRIS entry, include its reference when you contact support so we can identify the right record.

It covers data connected with your account, phone verification, sign-in activity, device access, payment references, cookies and support messages. It also explains how we use, protect, retain and respond to requests about that data where local law permits.

Phone verification helps us connect access to the correct account and reduce mistaken or unauthorised changes. We record the verification result and related account event, but you should never send us your password or a complete wallet credential.

Yes. The Privacy Policy covers operational references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may use the reference, status and timestamp to match an account entry or answer a payment-data request.

Contact support using the channel shown on our site and state that you want an account-data access request. Provide your registered phone or email and the record you mean. We verify ownership before sharing data and explain any lawful retention limit.

You can request correction when an account detail is inaccurate or outdated. Tell support which field needs changing, such as a contact detail or verification record. We may require an ownership check and will explain the result under the Privacy Policy.

Cookies and device signals can keep your mobile session active, remember a selected setting and help identify unusual sign-in behaviour. Browser controls can remove or restrict them, but that may interrupt phone verification or require another account sign-in.

Ask support for deletion of eligible personal data and include your registered contact. We assess the request under local law, remove or separate records where permitted, and retain only material needed for security, disputes, account service or a legal duty.