Reference

Open Privacy Policy Before Account Access

tebasbet Privacy Policy explains how we collect, use and protect your account, device and payment details before you open the lobby.

Account dataWallet recordsCookie choicesYour requests
Browse Our Lobby Read FAQ
tebasbet Open Privacy Policy Before Account Access
REQUEST ROUTES

Contact Us About Your Privacy Policy

A clear contact path helps you ask about data without searching through account screens. Use the account help route when you need a copy, correction or explanation, and include the phone number linked to your profile so we can check ownership. If your question concerns a DANA, OVO, GoPay or QRIS record, attach the receipt reference shown in your cashier history. We use the same verification step before changing sensitive account details.

Team online

Account data request

Use account help to ask which profile details we hold, why a phone verification record is present, or how to correct a spelling or contact detail. We may ask you to confirm the linked number before sending or changing anything.

Wallet record question

For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference rather than your wallet password or PIN. We use that reference to locate the relevant record and keep unrelated account details out of the request.

Receipt status route

If a payment receipt or bank transfer status is attached to your data request, follow the cashier support path from your account. Our team can check the record against a virtual account or bank reference while protecting other account details.

HANDLING PRACTICE

Explore Data Choices Inside tebasbet

Privacy is handled through practical account steps, not a single setting hidden away from you. We separate sign-in checks from wallet reconciliation, use device and session details to protect access, and retain…

Data collected

We may collect your phone number, account identifiers, device details, session activity and payment references. A game entry such as Barong Dance Reels can be linked to account activity so we can secure access and resolve a record question.

Cookie handling

Cookies and similar device storage help keep your sign-in session working and remember relevant page choices. You can manage browser storage through your device settings, although removing it may require another phone verification when you return.

Account security

Phone verification helps us distinguish you from an unauthorised person requesting access or a data change. Keep your device and sign-in details private; we will not ask you to disclose a wallet PIN in a privacy request.

Retention periods

We retain account, payment and support records for as long as needed for account operation, dispute handling, security checks and applicable legal duties. When a record is no longer needed for those purposes, our process removes or de-identifies it.

Data corrections

You can ask us to correct inaccurate profile details or clarify how a record was used. Include the linked phone number and the exact field in question; we may pause the change until account ownership is confirmed.

Request contact

For access, deletion or processing questions, use the account help route and identify the Privacy Policy request clearly. We assess each request under the rules that apply to your location, because access depends on local law.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers cover the account and payment questions we expect before registration. They explain what happens during phone verification, how wallet records are matched, what cookies do on a mobile browser and how to reach us when you want a copy or correction. If your situation is not listed, use the account help route with the relevant reference.

It covers data connected with your account, phone verification, device sessions, cookies, support requests and payment references. It applies when you browse account pages, sign in, use the lobby or ask us to check a DANA, OVO, GoPay, QRIS or bank record.

Phone verification helps us confirm that the person requesting account access or a data change is linked to the account. It also supports security checks when a new device or unusual session appears. We use the result for account protection, not unrelated marketing.

We use DANA and QRIS references to match a payment instruction, receipt and account status. The record can include a reference, amount and status supplied for reconciliation. We do not need your wallet PIN for a Privacy Policy request, and you should never send it.

Yes. Contact us through account help, identify the Privacy Policy request and state whether you want a copy or a correction. Add the phone number linked to your profile and the specific record or field. We may verify ownership before responding.

Cookies can keep your session active and preserve selected page settings on a mobile browser. If you clear browser storage, we may ask you to sign in and complete phone verification again. You can manage storage in your device or browser settings.

Retention depends on the purpose: account operation, security, payment reconciliation, dispute handling or a legal duty. We keep a record while that purpose applies, then remove or de-identify it through our process. You can ask which purpose supports a particular record.

You can ask us to assess deletion through account help. We check the request against account security, unresolved payment records and legal duties, so not every record can be removed immediately. Any access or eligibility decision depends on local law and the facts of your request.

Related Pages

tebasbet Indonesia FAQ Access guide Barong Dance Reels Badminton Asia Championship Bet