Reference

Open capter4d With Privacy In View

capter4d Privacy Policy explains how we collect, use and protect the details connected to your account, wallet activity and device access.

Account clarityWallet recordsCookie choices
capter4d Open capter4d With Privacy In View
CONTACT ROUTES

Reach Us About Privacy Questions

A clear contact path helps you act on the Privacy Policy instead of guessing about a record.

Account request Use the account support path to ask what personal details are connected to your profile, why a phone verification step appeared, or how to correct a spelling or contact detail. We will ask for enough account context to identify the right record.
Payment record For a DANA, OVO, GoPay or QRIS privacy question, include the payment date, reference and account phone number. We use those details to locate the relevant record without asking you to send a full wallet password or private security code.
Access concern If an unfamiliar device or login appears, report it through account support and change your password through the account security path. Do not place a password, one-time code or complete payment credential in a privacy request.
DATA HANDLING

Explore The Privacy Controls We Use

We handle Privacy Policy requests through practical account and security processes rather than broad promises.

Collection purpose

We collect account details to create and maintain your profile, verify requested access and respond to support. Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity help us reconcile status without treating your wallet password as an account field.

Cookie choices

Cookies can remember a session, retain a language or region choice and help us see whether a page loads correctly. You can clear or restrict them in your browser settings, although removing session cookies may require you to log in again.

Account security

Phone verification, password controls and device event checks help us distinguish your access from an unfamiliar attempt. We do not ask you to place a password or one-time code in a support message about Privacy Policy.

Payment privacy

A payment record normally needs a reference, amount status and account link for reconciliation. Send only the details needed for a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, and keep wallet credentials private.

Retention timing

We retain personal data while it supports your account, a payment query, security work or an applicable legal duty. When the relevant purpose ends, we remove, aggregate or anonymise the record according to our internal retention process.

Change request

You can ask us to correct inaccurate account details, explain a data use, provide an applicable copy or remove details where the request is allowed. Include your account phone number and the specific change so we can verify and route it.

Browse Answers About This Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or using the capter4d account path. We describe the records connected to login, payments, cookies, device events and support, while keeping access wording tied to local requirements. If your question concerns a specific record, use the account support path and include only the details needed to locate it.

The capter4d Privacy Policy covers account details, phone verification, login and device events, cookies, support requests and payment references. It explains why we use each category, how retention works and how you can ask for correction, access, clarification or removal where local law permits.

We use your phone number to create and identify your account, support a verification step before account access and connect a request to the correct profile. If the number is inaccurate, use the account support path to request a correction after we verify your identity.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match status and receipts to your account. Do not send a wallet password, one-time code or complete security credential.

We use session cookies to keep account access working, preference cookies to remember selected settings and similar signals to check page performance. You can clear or restrict storage through your browser. If you remove session data, you may need to complete login again.

You can ask for an applicable copy, correction or explanation by using account support. State the specific record, such as your phone number, login detail or payment reference. We verify the requester first, then handle the request according to local law and retention duties.

Report the unfamiliar login or device event through account support, then change your password using the account security path. Include the event time and device description, but never include a password or one-time code. We use the details to check the relevant security record.

Your access to capter4d and certain data requests depend on local law and apply where local law permits. The Privacy Policy does not replace those requirements. If you need a jurisdiction-specific answer, contact us through your account support path with your location and request.