Reference

bebtoto Privacy Policy For Your Account

The bebtoto Privacy Policy explains what we collect when you create an account, sign in, use DANA or QRIS, and contact support.

Account dataWallet recordsCookie choicesContact requests
bebtoto bebtoto Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact route matters when you want to ask about stored details, a cookie setting, or a wallet reference. Start from the account help path and include the email or phone detail connected to your account, plus the subject of your request. We use those details to locate the right record without asking you to send a full payment credential.

Team online

Privacy request

Use the account help path to ask what personal data we hold, why it is used, or whether a correction request can be processed for your bebtoto account.

Wallet reference

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, share the transaction reference only; never send a wallet PIN or full authentication secret.

Access concern

If phone verification or a sign-in check blocks your request, tell us the device path and time shown on screen so our account team can separate access issues from privacy questions.

DATA HANDLING

What We Do With Your Account Data

We keep this Privacy Policy practical by tying each record to an operating need: account access, payment reconciliation, security checks, or support.

Account details

We may use your registration details and verified phone number to create your account, confirm account ownership, and complete an access check before you reach the lobby.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records help us match deposits or withdrawals with your account status; wallet PINs are not needed for that match.

Cookies

Cookies can keep a sign-in session, remember a language or display choice, and help us understand errors. You can manage browser cookies, though some account steps may then need repeating.

Account security

Phone verification, sign-in signals, and device details can help us detect unusual access. If a check fails, contact account support rather than sharing your password or wallet credential.

Retention

We retain records only for the period needed for account operation, payment reconciliation, security, dispute handling, or a legal requirement. The applicable period can depend on the record type.

Changes and requests

You can ask us to correct relevant account details, explain a data use, or address a permitted deletion request through account help. We may verify ownership before changing or releasing records.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take: opening access, checking a wallet record, changing browser settings, or asking us to correct personal data. If your situation is not covered, use the account help path and describe the exact screen or record involved.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, support messages, retention, and requests to correct or question personal data where local law permits.

Phone verification helps confirm that you control the account before access is granted or sensitive changes are handled. It also helps us investigate unusual sign-in activity without requesting your wallet PIN.

Yes. The policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity, while payment authentication secrets should remain with you.

You can send a correction request through the account help path. Include the affected field and the account detail needed for ownership checks; we may ask for verification before making a change.

Cookies can remember your session and selected preferences, and may help us diagnose a page error. If you remove or block them, sign-in or account steps may need to be repeated.

Retention depends on the type of record and the reason it was collected, such as access, payment reconciliation, security, disputes, or a legal requirement. The applicable period may therefore differ between records.

Use the account help path and identify your request as a Privacy Policy question. Mention whether it concerns access, cookies, payment references, correction, or deletion so we can route it accurately.