Reference

aku4d Privacy Policy for Your Account

aku4d Privacy Policy explains how we collect, use and protect the details connected with your account, including records linked to DANA, OVO, GoPay and QRIS.

Account recordsWallet referencesCookie choicesRequest a change
aku4d aku4d Privacy Policy for Your Account
CONTACT ROUTES

Where To Ask About Your Records

A clear contact path helps when a Privacy Policy question concerns a login, wallet reference or device record. Use the support route available from your account area and include the account identifier shown there, rather than sending a password or full wallet credentials. We check the request against your account before discussing personal details, including requests made from Jakarta.

Team online

Account data request

Ask us to explain the personal details connected with your account. Include your registered contact and the specific record you want checked so we can avoid exposing details to the wrong person.

Wallet record check

For a DANA, OVO, GoPay or QRIS reference, send the visible transaction reference and approximate date. We use those details to locate the record without requesting your wallet PIN.

Login privacy help

If a phone or desktop session raises a privacy concern, tell us the device path and account step involved. We can separate a cookie issue from an account-security question before responding.

CONTROLLED HANDLING

Six Controls Behind Our Privacy Policy

We apply the Privacy Policy to the account journey rather than treating it as a page you read once.

Collected details

We may handle your contact details, account activity, device signals and payment references. We use each category for a stated operational purpose, such as login protection, transaction matching or responding to your request.

Cookie settings

Cookies can keep a session open and remember page preferences on your phone or desktop. You can adjust cookie controls in your browser, though disabling some cookies may require another account sign-in.

Account security

Before we discuss personal records, we compare your request with account details and relevant login signals. Never send a password, one-time code or wallet PIN through a support message.

Retention timing

We keep account and transaction references for the period needed for security, service records or legal duties. When a record no longer serves those needs, our handling process moves it toward removal or anonymisation.

Correction requests

If your contact detail is wrong, tell us which field needs correction and provide the account identifier shown after login. We may ask for an account check before changing information tied to access.

Policy contact

Questions about this Privacy Policy should use our account support route, with the relevant section named in your message. We can then address data use, cookies, retention or a record request directly.

Privacy Policy Questions Indonesian Customers Ask

These Privacy Policy answers cover the account and wallet questions we hear most often. If your situation involves a detail not listed here, use the support route with your account identifier and the section that prompted your question.

It covers account details, verification information, device signals, cookies, transaction references and requests about your records. It also explains why we use each category and when retention may end.

No. Our Privacy Policy does not require you to send a wallet PIN. We may keep a visible transaction reference for matching, but your private wallet credential should remain with your payment provider.

Use the support route from your account area and identify the records you want checked. Include your registered contact and account identifier, then complete any account check needed before disclosure.

Yes. Privacy Policy requests for correction can name the inaccurate field, such as a contact detail, and include your account identifier. We verify the request before changing information connected with access.

Cookies can maintain a signed-in session, remember preferences and show how you reached a policy page. Browser controls let you adjust them, although some account steps may then require another login.

We retain wallet and transaction references only as long as needed for security, service records or legal duties described in the Privacy Policy. The period can differ by record type and request.

Yes. Where access or eligibility is discussed, it depends on local law. Our Privacy Policy explains data handling, but it does not replace the legal requirements that apply to your location.