Reference

capital33 Privacy Policy For Your Account

capital33 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet records.

Account recordsWallet referencesCookie choicesPolicy requests
capital33 capital33 Privacy Policy For Your Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route helps you question a record, request a correction or ask how your account data is used.

Account access If you cannot sign in or complete phone verification, use the account support path shown on the access screen. Tell us the registered phone number and the issue, but do not send your password, wallet PIN or full payment credentials.
Wallet records For a DANA, OVO, GoPay or QRIS record, include the account reference, payment rail and visible status from your cashier history. We use those details to locate the record while limiting the personal data included in your message.
Privacy changes To ask for a copy, correction or deletion review, contact us through the privacy route linked in your account area. We may ask you to complete an account check before changing information, so another person cannot alter your records.
DATA PRACTICES

How capital33 Handles Your Details

Our privacy process follows the information needed for a real account journey rather than collecting every possible detail.

Account data

We use your account details to create access, complete phone verification, respond to support and show records connected with your own activity. We do not need your password in a support message, and we ask you to keep sign-in credentials private.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may include a method, amount reference, status and time. We use these fields to match a cashier request, investigate a mismatch and keep an auditable account history.

Cookies and devices

Cookies and device signals help keep a session open, remember essential settings and identify unusual sign-in behaviour. You can manage browser cookie settings, but removing necessary cookies may require another login before you reach the lobby.

Account security

We use phone verification, sign-in records and unusual-access checks to reduce unauthorised account changes. If a security check interrupts access, follow the account path rather than sharing a password, wallet PIN or one-time verification code.

Retention choices

We retain account, security and transaction records for the period needed to provide access, resolve disputes, meet legal duties and protect the service. When a record is no longer needed for those purposes, our processes address its removal or restriction.

Change requests

You can ask us to view, correct, restrict or remove eligible personal details through the privacy contact route. We verify the request against your account before acting, and access to any service remains where local law permits.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account questions you are most likely to have before opening access. We explain the records connected with local wallets, the device path, contact checks and requests to change stored details. If your situation is unusual, send a focused request through the account support route and avoid including passwords or wallet PINs.

The capital33 Privacy Policy covers account details, phone verification, device and sign-in records, cookies, support messages and payment references. It explains why we use those records, how we protect account access, how retention works and how you can request a copy or correction.

We use your phone number to create and verify the account, help restore access and connect support with the correct record. The number may also help us identify unusual sign-in activity. Keep verification codes private and send only the details requested through support.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account status. We use method, reference and status details to match a cashier request, resolve discrepancies and maintain the account record.

Cookies can keep essential session settings, remember necessary choices and support sign-in security. You can change cookie controls in your browser, but removing essential cookies may sign you out or require another verification step before account access continues.

You can request access to eligible records or ask us to correct details through the privacy contact route in your account area. We first check that the request belongs to you, then explain any limits that apply under local law.

We keep account, security and payment-reference records while they are needed for access, dispute handling, legal duties and service protection. Retention can differ by record type. After the required period, we address deletion, restriction or anonymisation through our internal process.

You may open an account and continue through the required checks where local law permits. Your access path may include phone verification and a security check before the lobby or wallet records appear. Reading the Privacy Policy does not remove local eligibility requirements.