Reference

kapital4d Privacy Policy for Your Account

Our Privacy Policy explains how we handle the details connected with your kapital4d account, including phone verification, wallet records and device access.

Account clarityWallet recordsCookie choicesSecurity requests
kapital4d kapital4d Privacy Policy for Your Account
CONTACT FOR PRIVACY

Get Help With Your Data Request

A clear contact route helps when your Privacy Policy question concerns a phone number, wallet reference or sign-in event. Start from your account support path and describe the exact record you want us to check. If you are in Jakarta or elsewhere in Indonesia, include the account identifier, approximate date and affected device without sending a password or wallet PIN. We use those details to locate the request, confirm that it comes from you and respond through the available support channel.

Team online

Account support path

Open the support route from your account when you need a Privacy Policy answer. Tell us whether the request concerns phone verification, a login event, a DANA reference or another account record so we can direct it to the right handling step.

Wallet record query

For an OVO, GoPay, QRIS, bank transfer or virtual account query, provide the transaction reference and date rather than a secret credential. We can compare the account record with the status shown in the cashier path without asking for your wallet PIN.

Access concern

If a phone or browser no longer opens your account, tell us what changed and when. We may ask for account verification before discussing personal data, because a Privacy Policy request must not expose your records to another person.

DATA HANDLING DETAILS

What We Keep, Protect and Change

Privacy Policy choices are easier to use when each data purpose is visible. We separate account details from device signals, payment references and support messages, then restrict account…

Account details

We handle the details needed to create and maintain your account, including contact data and phone verification status.

Device signals

When you use a mobile browser or desktop browser, we may record device and session signals such as browser type…

Cookie controls

Cookies can keep your account path working between sign-in and the lobby and can help us detect repeated security failures.

Payment references

A DANA, OVO, GoPay or QRIS record may be linked to your account as a reference for status checking.

Account security

Phone verification and sign-in checks help us confirm that a Privacy Policy request belongs to you.

Change requests

You can ask us to correct account details or explain how a record is used through the support path.

Privacy Policy Answers for kapital4d

These Privacy Policy answers focus on the account questions you are most likely to ask before opening or using a kapital4d account in Indonesia. They explain what we collect, why wallet references appear, how cookies work and how to ask us to change a record. Access depends on local law.

It covers account details, phone verification, support messages, device and session signals, cookies, security events and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains the purposes, access controls and request path we apply to those records.

Do not send us your wallet PIN, password or full payment credential. Our records may contain a transaction reference or status connected with DANA, OVO, GoPay or QRIS, but those references are used to match account activity and investigate a status without requesting your secret credentials.

We use phone verification to connect account access with the correct account and to reduce the chance that a data request is made by another person. The verification status can also support sign-in checks. If you ask about it, we may confirm ownership first.

Yes, contact us through the account support path and state whether you want a copy, correction or explanation of a particular record. Include the account identifier and useful dates, but not a password or wallet PIN. Where local law permits, we assess the request after verification.

Retention depends on the type of record and the reason it exists. We may keep account, payment-reference, security and support records while needed for account protection, dispute handling or legal duties. When those needs end, handling follows the applicable retention process and local law.

Cookies can maintain a sign-in session and help us identify security events, while browser settings can limit some cookie activity. Required cookies may be needed for the account path to work. You can ask support how a cookie-related record is used or request clarification.

You can send a deletion request through the account support path with enough detail for ownership checks. We assess it against security, unresolved payment questions, dispute handling and legal duties. Some records may need to remain for those reasons, and we explain the outcome through the available channel.