Reference

How betidb Protects Your Personal Data

Your personal data is handled with precision at betidb — from the moment you open an account to every deposit you make via DANA, OVO, GoPay, or QRIS…

Data encrypted in transitDANA, OVO, GoPay, QRIS protectedAccount data access on requestRetention periods disclosedContact us to update your data

Explore Lobby Read FAQ

What Data We Collect and Why

betidb Service availability depends on jurisdiction. Users are responsible for checking local law before access.

When you open an account with betidb, we collect your name, email address, phone number, and payment identifiers linked to DANA, OVO, GoPay, or QRIS. We use this data to verify your identity, process withdrawals, and maintain accurate account records. Transactional data — including deposit timestamps

1
and amounts — is retained for a minimum of five years to meet financial record obligations. Device identifiers and browser session data are collected to detect unauthorised access and keep your account secure. We do not sell your personal data to third parties. Data sharing is
2
limited to payment processors, fraud-prevention partners, and where local law requires disclosure to regulatory bodies. Access to your data depends on local law and the jurisdiction from which you connect.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY CONTACT PATHS

How to Reach Us About Your Data

If you need to update, access, or request deletion of your personal data, our privacy support team is reachable seven days a week.

DATA HANDLING STANDARDS

Six Ways betidb Handles Your Data Responsibly

From cookies to withdrawal verification, every data-handling step at betidb follows a documented process. Players in Jakarta and Yogyakarta go through the same account security checks — no regional shortcuts are applied.

Encryption in Transit

All data exchanged between your device and our servers uses TLS 1.3 encryption. This applies equally to account logins, DANA deposits, and OVO withdrawal requests — no plain-text transmission at any step.

Cookie Controls

We use session cookies to keep you logged in and analytics cookies to understand which pages you visit most. You can manage or disable non-essential cookies at any time through the cookie preference panel in your account.

Withdrawal Verification

Before a withdrawal is processed to GoPay or QRIS, our system cross-checks the registered wallet ID against your account record. This step prevents misdirected payments and flags any mismatched data for manual review within 30 minutes.

Retention Policy

Transaction records are kept for five years in line with financial compliance requirements. Account profile data is deleted within 90 days of a verified account closure request, unless a legal hold applies where local law requires longer retention.

Third-Party Data Sharing

We share data only with our payment processor partners — the gateways behind DANA, OVO, GoPay, and QRIS — and with fraud-prevention services. We do not share your data with advertisers or unrelated commercial third parties.

Your Right to Access

You can request a full export of your stored personal data at any time through Account Settings or via email. We aim to deliver the export within 72 hours of identity verification. Data corrections take effect on your account within 24 hours of confirmation.

Your Privacy Policy Questions, Answered

Below are the questions we receive most often about how betidb handles personal data, cookies, and your rights as an account holder. If your question is not covered here, contact our privacy team via live chat between 08:00 and 24:00 WIB or send an email with your registered account details.

We collect your name, email, phone number, and the wallet ID linked to your chosen payment method — DANA, OVO, GoPay, or QRIS. Device identifiers and session logs are also recorded for account security purposes.

Payment identifiers for DANA and OVO are stored in encrypted form and are never displayed in plain text. Our servers communicate with payment gateways over TLS 1.3 channels, and wallet IDs are verified against your account before every transaction is processed.

Yes. Log in, go to Account Settings, select Privacy Controls, and choose the data export option. We aim to deliver a full data package within 72 hours of verifying your identity. Exports are sent to your registered email address.

Transaction records — including GoPay and QRIS deposit and withdrawal history — are retained for five years to meet financial compliance requirements. Account profile data is deleted within 90 days of a verified account closure, unless a legal hold applies.

We share data only with the payment processors behind DANA, OVO, GoPay, and QRIS, and with fraud-detection partners. We do not sell or share your data with advertisers. Any broader disclosure depends on local law or a valid legal order.

Contact our privacy team via live chat or email with proof of the correct information. Updates to your registered name, phone number, or linked wallet are applied within 24 hours of identity verification. Some changes may require additional document checks.

We use session cookies for login continuity and analytics cookies to see which account features you use most. Non-essential cookies can be turned off through the cookie preference panel in Account Settings without affecting your ability to deposit or withdraw.

How betidb Protects Your Personal Data

How to Reach Us About Your Data

Six Ways betidb Handles Your Data Responsibly

Encryption in Transit

Cookie Controls

Withdrawal Verification

Retention Policy

Third-Party Data Sharing

Your Right to Access

Your Privacy Policy Questions, Answered

01 What personal data does betidb collect when I open an account?

02 How is my payment data protected when I use DANA or OVO?

03 Can I request a copy of all the data betidb holds about me?

04 How long does betidb keep my transaction records?

05 Does betidb share my data with third parties?

06 How do I update or correct my personal information?

07 What types of cookies does betidb use and how do I control them?

Related Pages