Reference

duniahoki Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a duniahoki account, sign in from an Android phone or desktop, and use wallet routes such as DANA…

Account recordsWallet referencesCookie choicesAccess requests
duniahoki duniahoki Privacy Policy for Your Account
CONTACT ROUTES

Three Ways To Ask About Your Data

A clear contact route helps when you want to ask about the duniahoki Privacy Policy, correct an account detail or check why a wallet reference is connected to your profile. Start from the support contact shown after sign-in, and include the phone number on your account plus the relevant payment reference. We use those details to locate the right record without asking you to send a full wallet password or login secret.

Team online

Account support

Use the signed-in support route for a Privacy Policy question, phone-number correction or request to see the account data linked with your profile. We may ask you to complete the same phone verification used before account access so we do not disclose records to another person.

Cashier status

For a DANA, OVO, GoPay or QRIS reference, send the transaction identifier shown in your account rather than wallet credentials. Our support path can compare the recorded status with your account history and explain which payment detail we hold for that specific request.

Privacy request

Ask for a correction, access copy or deletion assessment through the available account contact path. Tell us the request type and the phone number attached to your profile; we verify ownership first, then respond according to the Privacy Policy and local legal requirements.

HANDLING PRACTICE

How We Handle Account And Device Records

Privacy controls work best when they match the way you actually use an account. Our handling practice separates sign-in details, payment references, device signals and support messages so…

Data collected

We collect details you provide during account creation and phone verification, plus technical signals from the browser or device used…

Cookie controls

Cookies and similar session tools help keep you signed in, remember selected settings and detect unusual access.

Account security

Phone verification before account access helps us connect a request to the right account.

Payment records

For DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity, we keep the references and status needed to reconcile…

Retention period

We keep account, security, support and payment records only as long as needed for the stated purpose, account questions, dispute…

Change requests

You can ask us to correct profile details, explain a stored record or assess deletion through the account support path.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account steps and local wallet references you are most likely to ask about before opening an account. We keep each answer tied to the records we actually use, including browser sessions, phone verification, payment status and support requests. If your situation is not listed, contact us through the signed-in account route and include only the details needed to identify your request.

It covers data collected during account creation, phone verification, sign-in, wallet status checks, browser sessions and support contact. It also explains cookies, account security, retention and your route for correction or access requests. Access or eligibility depends on local law and applies where local law permits.

We may hold your name, phone number, login details, verification result, device signals, IP address, browser session and account activity. We use these records to connect you with the correct account, protect access and answer support requests without requesting your wallet PIN.

We use payment references and status results for DANA, OVO, GoPay and QRIS, not your wallet PIN or password. A virtual account or bank transfer may also create a reference connected with your account, including context from BCA, BRI, Mandiri or BNI.

Use the signed-in account support route and ask for an access copy under the Privacy Policy. Include the phone number attached to your profile and describe the records you need. We verify account ownership before releasing data and handle the request under applicable local requirements.

Yes, you can request a correction through account support. State which profile detail is inaccurate and provide the phone number linked to the account. We may repeat phone verification before making a change, especially where the detail affects sign-in, payment matching or account security.

Cookies help maintain a browser session, remember settings and identify unusual access. You can adjust permissions in your Android browser, but blocking essential cookies may interrupt sign-in or remove session preferences. The Privacy Policy still explains the records handled when you use the service.

We retain payment references, support messages, account details and security records for the time needed for their stated purpose, dispute checks or legal duties. After that period, we remove the record or separate it from direct identification, subject to applicable local requirements.