Reference

Open kuota4d Privacy Policy Before Account Access

The kuota4d Privacy Policy explains what we collect when you create an account, verify your phone and use the mobile lobby, including records connected with DANA, OVO, GoPay…

Account dataWallet recordsCookie choicesAccess requests
kuota4d Open kuota4d Privacy Policy Before Account Access
CONTACT PATHS

Ask About Privacy Beside Your Account

A clear contact path matters when you want to understand a record rather than guess at its meaning.

Account data request Ask us which account details we hold and how they were obtained.
Wallet record question For DANA, OVO, GoPay or QRIS records, share the payment reference and status shown…
Correction or deletion Tell us which personal detail needs correction or removal and explain the account step…
DATA HANDLING

Browse kuota4d Privacy Controls Clearly

We handle privacy as an account process, not as a vague promise. The controls below explain why certain records appear after phone verification, how the mobile browser stores a session cookie, and…

Collected account details

We may use your phone number, login details and verification result to identify the account you asked us to protect. We collect only the details needed for account access, payment matching and privacy-request handling.

Cookie behaviour

Our mobile browser session may use cookies to keep login state and remember security checks. You can review cookie controls in your browser settings, though removing them may require phone verification again.

Wallet references

A DANA, OVO, GoPay or QRIS payment reference helps us connect a receipt to the correct account. We use the reference and status for matching, not as a request for your wallet password.

Account security

Phone verification is checked before account access and before we discuss sensitive records. This step helps us avoid disclosing account details to someone who cannot match the registered account path.

Retention approach

We retain account, security and payment-reference records only for the period needed for stated account, dispute or legal purposes. When that need ends, records are deleted or separated from direct account identifiers.

Requesting changes

You can ask about access, correction or deletion through our account support route. Include a precise request, and we explain what we can change, what must remain and how local law affects the result.

Find Privacy Answers Before You Join

These Privacy Policy answers cover the questions we expect before account creation. We focus on the records you may recognise from phone verification, mobile cookies and local wallet references, so you can choose the next account step with a clear view of the request process.

It covers account details, phone verification, login cookies, payment references and privacy requests connected with our services. It also explains retention, security checks and the limits created by local law.

Yes. The Privacy Policy explains how we handle DANA and QRIS references, including status and matching details. We do not need your wallet password to investigate a receipt linked to your account.

Phone verification helps us confirm that a privacy request or account-access question comes from the correct account holder. We use the result as a security check before discussing sensitive records.

Use the support route beside your account area and ask for an account-data access request. Identify the registered account through that protected path, and we will explain the records available under local law.

Yes. State which detail is inaccurate and provide the account step where it appears, such as phone verification or wallet matching. We check the request and confirm the correction available under local law.

We retain records for the account, security, dispute or legal purpose that requires them. After that need ends, we delete the records or remove direct identifiers, subject to applicable local requirements.

Yes. Access, correction and deletion rights depend on local law. Where local law permits, you can request additional details through support, and we will explain any exception that affects your request.