Reference

awsbet Privacy Policy for Your Account

awsbet keeps the Privacy Policy close to the account steps that matter: phone verification, wallet records and access from your device.

Clear data purposesWallet records explainedPhone access controlsCookie choicesSupport request path
awsbet awsbet Privacy Policy for Your Account
HELP WITH REQUESTS

Ask About Privacy Policy Changes

A clear contact route matters when you want to understand or change personal details held with your account.

Account contact Open the support path from your signed-in account when you want to ask about…
Receipt context If your request concerns DANA, OVO, GoPay or QRIS data, add the payment date…
Support hours Check the support page for the current hours and contact route before sending a…
DATA HANDLING

What We Do With Account Details

Privacy Policy choices are easier to use when each data purpose is visible. We separate account access records from wallet references, device activity and cookie settings so a request can target the…

Account security

Phone verification helps us connect account access with the number you supplied. A new device or unusual sign-in may trigger an extra check before sensitive account details are changed, reducing the chance that another person alters your records.

Device signals

When you move from a phone to desktop, we may record browser, device and sign-in events for security and fault checking. These signals help us investigate an access issue without reading unrelated files stored on your device.

Cookies

Cookies can keep a session open, remember selected settings and show which page failed to load. You can adjust cookie controls in your browser, although blocking essential cookies may stop phone verification or account access from working correctly.

Wallet records

DANA, OVO, GoPay and QRIS activity may leave a payment reference, amount status and time record in the account ledger. We use those fields to match a receipt or status question, not to request your private wallet PIN.

Retention period

We keep account, security and payment records only for the period needed for the stated purpose, account protection or a legal duty. After that period, we delete or separate the record from direct account identifiers where that is permitted.

Change requests

You can ask us to correct eligible account details, explain a data use or close an account through the support contact shown in your account area. We may request phone verification before acting, so a private request is not changed by mistake.

Privacy Policy Answers for awsbet

These Privacy Policy answers focus on the searches we expect from someone preparing to open or use an awsbet account in Indonesia. We cover phone verification, wallet references, cookies, device access, correction requests and account closure without turning the page into a general lobby description. If your question is not listed, use the support path shown after login and include only the details needed to locate your account.

The awsbet Privacy Policy covers account details, phone verification, sign-in and device records, cookies, wallet references, support requests and retention. It explains why we use each category and how you can ask for access, correction or eligible removal through the account support path.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps. We may retain the payment status, time and receipt reference needed to match an account event, but we do not need your wallet PIN.

Phone verification links your account to the number you supplied and helps us confirm a request to change sensitive details. It can also help us investigate a sign-in problem from a new device. Never share a one-time code with another person or in a support message.

Cookies can maintain your signed-in session, save selected settings and help us identify a page or device fault. You can control optional cookies in your browser. Essential cookies may be needed for phone verification, account access and the policy request path to function.

You can contact us through the signed-in support route to ask what eligible account details we hold or to request a correction. Include your registered phone number and the specific record concerned. We may verify your account before releasing or changing personal details.

We retain account, security and payment records for the period needed for account protection, payment reconciliation or a legal duty. When that purpose ends, we delete or anonymise records where permitted. Support can explain the relevant retention category for your request.

You can ask for account closure through the support contact shown after login. We first check the request against your phone verification and account details. Some records may remain for security, payment reconciliation or legal duties, even after account access is closed.