Reference

Privacy Policy For Your cb100 Account

Our Privacy Policy explains how we collect, use and protect the account details you provide when you open cb100 access, verify your phone or reach the lobby from…

Clear data purposesCookie choicesAccount access requestsWallet record context
Explore Our Lobby Read FAQ
cb100 Privacy Policy For Your cb100 Account
POLICY CONTACT

Three Ways To Ask About Privacy

A clear contact route helps you resolve a Privacy Policy question without repeating your account history. We keep policy support close to the account and cashier paths, so a request about access, a wallet record or a stored device signal can be matched to the right account context. Use the route shown in our support area and include only the details needed to identify your request.

Team online

Account access request

Ask us to clarify which account details support phone verification or sign-in. Include your account identifier and the email or phone detail already attached to cb100. We use that account step to reduce mistaken disclosures and can explain the next action required for an access request.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, send the transaction reference and approximate date shown in your account. We can explain whether the record is pending, matched or retained for reconciliation. Do not send a wallet password, one-time code or full banking credentials.

Cookie preference request

Tell us which browser or mobile device you used and which cookie setting you want changed. Our support path can explain the effect on sign-in continuity and security checks. We may ask for an account step before changing a preference that affects access protection.

DATA PRACTICE

How We Handle Your Policy Rights

Our Privacy Policy is designed around the moments where account data matters most: opening access, checking a login, matching a wallet record and answering a deletion or correction request.

Account data

We use details such as your account identifier, phone verification state and sign-in history to provide account access and investigate unusual attempts. The policy does not treat every browsing action as a permanent profile. We explain the relevant data category when you ask about your own account.

Device signals

When you reach the lobby from a phone or desktop browser, device and browser signals may help us recognise a familiar session and identify suspicious access. These signals can include technical properties and login timing. They support account security and are handled under the purposes set out here.

Cookie controls

Cookies can keep a session connected, remember a selected setting and support security checks. You can manage available browser controls, although disabling certain cookies may interrupt sign-in or require another verification step. Our support route can clarify how a setting affects your account path.

Wallet records

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account can be used to match a cashier event to the correct account. We do not ask you to send wallet passwords or one-time codes. Keep your receipt reference available when requesting a status clarification.

Retention choices

We keep account, security and transaction references only while they support access, dispute handling, fraud checks or a legal requirement that applies to the service. A deletion request may have limits where a record is needed for those purposes. We will explain the reason for any retained category.

Change requests

You can ask us to correct an account detail, explain a stored category or clarify how a cookie is used. Send the request through the policy contact route with enough account context for verification. We may ask you to complete phone verification before discussing private account data.

Privacy Policy Questions About cb100

These Privacy Policy answers address the searches we expect from someone deciding whether to open an account from Indonesia. We cover account creation, mobile access, cookies, wallet references, correction requests and local eligibility in direct terms. When your question concerns a specific record, use the policy contact path and provide the smallest useful account detail.

The cb100 Privacy Policy covers account details, phone verification, login and device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use each category, how long records may remain and how to request clarification.

We use phone verification to confirm that an account access request is connected to the correct account and to reduce mistaken disclosures. A verification state may appear in our security records. If you ask about it, we first verify your account context before discussing private details.

Yes. The Privacy Policy covers payment references and status data connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. These references help us match a cashier event to your account. They do not require you to share a wallet password or one-time code.

You can contact us through the policy support route to ask which account data we hold or to request a correction. Include your account identifier and the detail needing attention. We may require phone verification before responding, and some records may remain where security or legal duties require them.

Cookies can keep your mobile browser session connected, remember a setting and support security checks while you move from sign-in to the lobby. Browser controls can restrict them, but sign-in may then require another step. The Privacy Policy explains these purposes, and support can clarify a specific setting.

We retain wallet references, login records and related account data only while they support account access, security checks, transaction clarification, dispute handling or an applicable legal requirement. The exact period can depend on the record type. Ask through policy support and we will explain the relevant retention reason.

Access depends on local law. The Privacy Policy describes how data is handled when access is available, but it does not change local eligibility rules or create access where it is unavailable. Check your local position before opening an account, and contact support if you need policy clarification.

Related Pages

cb100 Indonesia FAQ Account information About Us Turbo Spin Elite