Reference

apibet Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your apibet account, including login records, device signals and wallet references.

Account clarityCookie choicesWallet context
Browse Our Lobby Read FAQ
apibet apibet Privacy Policy For Your Account
HELP PATHS

Get Privacy Answers Through Account Help

Privacy questions are easier to resolve when you show us the exact account step that caused concern. We can trace a sign-in, phone verification request or wallet-status message when you contact support through the account help route. Include your registered phone number only through the secure contact path, and never send a password or one-time code. If a receipt from QRIS, DANA or bank transfer needs checking, keep its reference ready so we can locate the relevant record. Access remains subject to local law.

Team online

Account Verification

Ask about phone verification, sign-in records or a request to correct your account details through the account support path. We may ask for limited details to locate the right record, but we will not ask you to disclose your password or one-time access code.

Account Wallet Help

For a privacy question tied to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, share the receipt reference through support. We use that reference to check the status record without requesting your wallet PIN or banking password.

Receipt Status Check

If you think a payment receipt contains the wrong personal detail, contact us with the date, amount reference and payment rail name. We can explain which record is held, why it is needed and what correction route is available.

HANDLING DETAILS

Six Ways We Handle Your Data

The policy is practical: it tells you what happens around a login, a wallet reference, a cookie choice or a request to change your details.

Account records

We collect details needed to create and maintain your account, such as your phone number, login activity and verification status. We use them to confirm that the person requesting access matches the account record, especially after a device or browser change.

Device signals

Your phone or desktop browser can send technical details such as device type, browser version, session time and network-related signals. We use these details to identify unusual sign-in patterns and to keep an account session working correctly.

Cookie choices

Cookies and similar storage can remember a session, preserve a language choice or help us understand whether a privacy notice was displayed. You can manage cookie settings in your browser, although blocking necessary storage may affect sign-in and account verification.

Wallet references

A payment record may contain a rail name such as DANA, OVO, GoPay or QRIS, plus a transaction reference and status. We use that limited context to match a cashier event or receipt question, not to collect your wallet PIN.

Account security

Phone verification and sign-in checks help us protect account access. If Account Verification appears during login, follow the on-screen account step and contact support if the details do not match. Never share passwords, PINs or one-time codes with anyone.

Retention requests

We retain records only while they support the stated account, security, support or legal need, subject to local requirements. To ask about deletion, correction or a copy of your personal data, contact support through the privacy or account route with enough detail to identify your record.

Privacy Policy Questions From Indonesia

These answers address the searches we receive about the Privacy Policy and account records. They explain what you can request, which details may be needed, and how a wallet or device event fits into the policy. For a case-specific answer, use the support route named on this page and refer to your account step rather than sending sensitive credentials.

The Privacy Policy covers details used to create and support your account, including your phone number, verification status, sign-in activity and relevant device signals. We use them for access, security and support checks, and we apply the stated retention rules where local law permits.

Yes. Contact support through the account or privacy route and explain which detail is incorrect. We may request a limited account identifier to locate the record, then confirm the correction process. Do not send your password, wallet PIN or one-time verification code with the request.

Yes. The policy covers limited payment context linked to an account event, such as the rail name, receipt reference and status for DANA or QRIS. It does not require you to send a wallet PIN. Support can explain how a specific receipt record is used.

Cookies or similar storage can keep a mobile session active, remember a privacy choice and help display the correct account step. Browser settings let you remove or block them. If necessary storage is blocked, sign-in, phone verification or policy preferences may not work as expected.

We keep records while they serve an account, security, support or legal purpose, subject to applicable requirements. The retention period can differ by record type, such as a login signal or payment receipt reference. You can ask support which retention rule applies to your request.

Send a deletion request through the privacy or account support route with your registered contact detail and a clear description of the account. We verify the request before acting, and some records may need to remain when a legal, security or transaction requirement applies.

Yes. You can request a description or copy of personal data associated with your account through support. We first verify that the request comes from the account holder, then explain the available format and any records that must be withheld or retained under local law.

Related Pages

apibet Indonesia apibet Casino FAQ About Us Account information