Reference

Privacy Policy for Your apikjitu Account

Our Privacy Policy explains how apikjitu handles the details connected with your account, wallet activity and device access.

Account clarityWallet recordsCookie choicesSecure access
apikjitu Privacy Policy for Your apikjitu Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact path helps you act on the Privacy Policy instead of searching through account screens.

Account data request Ask us to identify the personal data linked to your apikjitu account.
Wallet record check For DANA, OVO, GoPay, QRIS or bank transfer records, send the payment reference and…
Correction route If your contact detail or verification record is inaccurate, tell us which field needs…
DATA PRACTICES

Six Privacy Controls Behind Your Account

We apply the Privacy Policy to the practical moments that matter: opening an account, signing in from a new device, checking wallet status and asking for help.

Data collection

We collect details you submit for an account, including contact and verification information, plus records created by sign-in and support…

Cookie controls

Cookies and similar storage can remember session choices and help us understand whether a sign-in request comes from a familiar…

Account security

A new phone, browser change or unusual sign-in can create security signals.

Payment matching

A DANA, QRIS, OVO, GoPay or bank transfer reference lets us match a cashier event with the correct account record.

Retention timing

We retain account, security and transaction records only for the period needed for service, dispute handling, security checks or a…

Change requests

You can ask for access, correction or clarification through support.

Privacy Policy Questions for Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or sending a data request. We explain how the policy connects with account creation, mobile access, cookies, local wallets and support checks. If your situation is not covered, contact us with the account detail or transaction reference that relates to your question.

It covers account details, phone verification, sign-in records, device and browser signals, cookies, support messages and payment references. It also explains why we use each category, how retention works and how you can request access or correction where local law permits.

We collect the contact and verification details you submit, then create account and sign-in records as you use the service. Device information may help identify unusual access. We use these details for account access, security, support and the purposes described in the Privacy Policy.

Yes. A DANA or QRIS request can produce a reference, amount, status and time record linked to your account. We use that information to match the cashier event, answer a receipt question and investigate a missing status without requesting unrelated personal details.

Contact support using the account contact detail associated with your profile and ask for a data access request. Mention the categories you want, such as cookies, sign-in records or wallet references. We may verify ownership before explaining or providing the available record.

Yes. Send support the field that is inaccurate and the corrected detail, using your registered contact route. We may request phone verification or another account check before changing it. Some transaction or security records may remain unchanged when retention is required.

Cookies can retain session choices and help distinguish a continuing sign-in from a new browser request. On a mobile phone, clearing cookies may require another account step. You can manage cookie settings in your browser, while access depends on local law.

Use our support route and identify the record or category you mean, such as a bank transfer reference, phone verification record or support message. We can explain the reason for retention and the applicable handling path after checking that the request is yours.