Reference

kilau4d Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your kilau4d account, including phone verification, login activity and wallet records.

Clear data purposesWallet record handlingAccount contact path
kilau4d kilau4d Privacy Policy for Your Account
CONTACT ROUTES

Ask About Privacy Through Account Support

A direct contact route helps when you want to understand a data entry, correct an account detail or ask why a wallet reference appears in your records. Use the account support path and include the phone number linked to your profile, without sending a password or one-time code. If your question follows a DANA, OVO, GoPay or QRIS receipt check, include its reference so we can locate the relevant record.

Team online

Account data questions

Send your privacy question through the account support path and identify the phone number on your profile. We use that step to match the request with the correct account before discussing records.

Wallet record checks

For a DANA, OVO, GoPay or QRIS entry, share the payment reference and date, while keeping passwords and one-time codes private. We can then check the stored transaction context.

Correction requests

If your contact detail or account record needs correction, tell us which field is wrong and why. We may ask for an account check before changing information linked to access.

DATA PRACTICES

How We Handle Your Kilau4d Records

Our handling process follows the account actions you take, from phone verification through payment status checks and later support contact.

Account details

We may hold your phone number, account identifiers and verification status so we can provide access and distinguish your profile from another account. We do not need your password in a support request.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce reference numbers, amounts and status markers. We use these details to reconcile an account action and answer receipt questions.

Device signals

When you sign in from a phone browser, we may record device and connection signals linked to security checks. These signals help identify unusual access without requiring a separate mobile application.

Cookies

Cookies can keep a sign-in flow consistent, remember limited preferences and help us understand whether an account page loaded correctly. You can manage browser cookie settings, though some account steps may then work differently.

Retention period

We retain account, payment and support records for as long as needed for account operation, dispute handling, security checks or legal duties. When a record is no longer needed, our handling process removes or restricts it.

Security requests

To request access, correction or clarification, contact support from the account route and describe the record involved. We may verify account ownership before responding, and you can ask why that check is required.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we expect from someone checking kilau4d before opening an account. They focus on account records, wallet references, cookies, device access and requests for changes. If your question concerns eligibility or access from Indonesia, the relevant condition depends on local law; our support route can help identify the record or process involved.

It covers account details, phone verification, sign-in signals, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to identify the account, complete the required verification step and help protect account access. Keep it current so a legitimate correction request can be matched.

Yes. The Privacy Policy explains that QRIS, DANA, OVO and GoPay can create reference and status records. We use those details to match a payment event with your account.

Use the account support path, name the field that needs correction and provide enough context to locate it. We may verify account ownership before changing a phone or payment-related record.

Cookies can support sign-in continuity, limited preferences and page diagnostics in your phone browser. Browser settings can restrict them, although some account or privacy-request steps may not behave normally.

We keep account, payment and support records for operational needs, security checks, disputes or legal duties. Once a record is no longer needed, we remove it or restrict further handling.

Access and eligibility depend on local law. The Privacy Policy explains our data handling when you use an account where local law permits, including requests made from Bandung or Medan.