Reference

wdkilat Privacy Policy for Your Account Data

Our wdkilat Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or connect DANA and QRIS.

Account clarityWallet data contextCookie choicesRequest access

Browse Our Lobby Read FAQ

How DANA and QRIS Data Is Used

wdkilat Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy connects each data use to a clear account action. When you choose DANA, OVO, GoPay or QRIS, we may receive payment status, reference details and the account identifier needed to match the transaction. Bank transfer and virtual account steps can also create a

1
reference from BCA, BRI, Mandiri or BNI. We use device, browser and sign-in records to detect unusual access and keep the lobby session connected to your account. We do not ask for wallet credentials through ordinary support messages. If you request a data copy or correction,
2
we first check account ownership before responding. Retention depends on the reason for collection, account status and applicable legal duties. Access to wdkilat services depends on local law, and our handling of this policy applies where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Get Privacy Help Before Account Access

A clear contact path helps you resolve a privacy question without sending sensitive wallet details into the wrong place.

Account privacy request Send a request through the account contact route when you need a copy, correction or deletion assessment. We verify ownership before discussing records connected with your login.

Wallet status concern If DANA, OVO, GoPay or QRIS data appears incorrectly matched, tell us the rail and reference shown in your account. Do not send a wallet PIN or password.

Device access question Report an unfamiliar browser session with its device type and approximate sign-in time. We can review the account path and help you secure access after identity checks.

ACCOUNT SAFETY

What We Keep Around Your Login

Privacy work is part of the account path, not a separate promise hidden from your wallet screen.

Account records

We may hold your account identifier, contact details, verification status and sign-in history so we can connect your access request with the correct account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may show a reference or status. We use these markers to reconcile activity without requesting wallet passwords.

Browser and device

A mobile browser or desktop session can produce device, browser, IP and security-event records. These signals help us investigate unusual access and protect your login.

Cookies

Cookies can support session continuity, preference storage and security checks. You can manage them through browser controls, although removing them may sign you out.

Retention periods

We keep records only for the period connected to their purpose, account handling or legal duty. When a request is eligible, we assess what can be removed or restricted.

Change requests

To correct or ask about your data, contact us from the account route and describe the requested change. We may request verification before taking action.

Privacy Policy Questions About wdkilat

These Privacy Policy answers cover the account, wallet and device questions you may have before opening access. If your case involves a specific DANA, QRIS, OVO or GoPay reference, use the privacy contact route and share only the details needed to locate the record.

It covers account details, verification, wallet references, browser and device records, cookies, retention, security handling and requests to access or correct data connected with your wdkilat account.

We use device and browser signals to connect a sign-in with your account, identify unusual access and investigate security events. A mobile browser may create different session records from desktop access.

Yes. The Privacy Policy explains how DANA, QRIS, OVO, GoPay, bank transfer and virtual account references may be used to match payment status with the correct account.

Use the privacy contact route shown in your account, state that you want an account data request and provide the relevant identifier. We check ownership before releasing or discussing records.

You can request a correction through the account contact path. Describe the field that needs changing and explain the correct value; we may ask for account verification before updating it.

Retention depends on the purpose of collection, account handling and applicable legal duties. We assess deletion or restriction requests against those factors rather than removing records automatically.

Access and eligibility depend on local law. Our Privacy Policy applies where local law permits, and you can contact us if a regional rule affects your account data request.

wdkilat Privacy Policy for Your Account Data

Get Privacy Help Before Account Access

What We Keep Around Your Login

Account records

Payment references

Browser and device

Cookies

Retention periods

Change requests

Privacy Policy Questions About wdkilat

01 What does the wdkilat Privacy Policy cover?

02 Why does wdkilat need device and browser details?

03 Does the Privacy Policy cover DANA and QRIS activity?

04 How can I request my wdkilat account data?

05 Can I ask wdkilat to correct my data?

06 How long does wdkilat keep personal data?

07 Does Privacy Policy access depend on Indonesian law?

Related Pages