Reference

Privacy Policy for Your Account Data

Our Privacy Policy explains how sbo 138 slot handles the account, device and wallet data you provide when you open an account or use the lobby.

Clear data purposesWallet activity contextAccount access requestsCookie choices
sbo 138 slot Privacy Policy for Your Account Data
HELP WITH PRIVACY

Wallet Receipts and Privacy Requests

A clear support route helps you ask about personal data without explaining your whole account history.

Privacy request Use support chat to ask what account data we hold or why a specific…
Wallet reference For a DANA, OVO, GoPay or QRIS question, provide the transaction reference rather than…
Login assistance If phone verification or a device login creates a privacy concern, tell us the…
SIX DATA CONTROLS

How We Handle Your Account Records

Our approach starts with using each data type for a stated account purpose rather than collecting unrelated details.

Account collection

When you open an account, we collect the contact and verification details needed to create that account and respond to…

Device signals

A mobile or desktop login can create device and session records, including access time and basic browser details.

Cookie settings

Cookies can remember a session and your selected preferences so the privacy controls do not reset during a visit.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create references, amounts and status entries linked to your…

Security records

We retain sign-in, verification and support records when they help protect your account or resolve a dispute.

Changes and retention

You can request access, correction or deletion of eligible account data through support chat.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take before opening an account or while checking a wallet status. We explain the data connected to sbo 138 slot, the effect of a mobile login, the role of phone verification and the support path for requests. Where access or a request is limited, the outcome depends on local law.

It covers account details, phone verification, login and device records, cookies, support conversations and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains our purposes, retention approach, security handling and ways to request access or correction.

We collect the contact and verification details needed to create and protect your account, together with login events and relevant device signals. Phone verification occurs before account access. We only ask for wallet references when a payment status or receipt needs matching to your account.

Yes. The Privacy Policy covers transaction references, status entries and related account records for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use these details for reconciliation and support, and we do not ask for your wallet password.

Contact us through support chat and identify your account with the registered phone number. State whether you want access, correction or deletion, and mention the relevant login or payment reference if needed. We may verify the request before responding, and the outcome depends on local law.

A mobile login can create a session record with access time, browser or device details and security events. We use this data to investigate unfamiliar access and maintain your session. We do not read unrelated phone content, and clearing cookies may require another login.

We keep account, support, security and payment-reference records for as long as they serve account assistance, dispute handling, payment matching or legal duties. After the relevant purpose and required period end, we remove or anonymise the record where local law permits.

Start with our support chat and describe the concern plainly, such as an unfamiliar login, a cookie choice, a phone verification issue or a DANA receipt. Include only the account details needed to locate the record; never send a password or wallet security code.