Reference

Privacy Policy for dki4d Account Data

Our dki4d Privacy Policy shows what we collect when you open an account, verify your phone, sign in from a mobile device, or use DANA, OVO, GoPay and…

Clear data purposesWallet record detailsAccount request pathLocal law wording

Explore Our Lobby Read FAQ

How DANA And QRIS Records Are Used

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

Our Privacy Policy covers information you provide during account creation, including your phone number and the details needed for phone verification before account access. We also receive technical records such as device type, sign-in time, IP address and security events so we can identify unusual access.

1
Payment records may show the selected rail, reference number, amount status and confirmation time for DANA, OVO, GoPay, QRIS, bank transfer or a virtual account; we do not describe wallet details beyond what is needed to match a transaction. We use these records to provide account
2
support, check payment status, maintain security and meet applicable legal requests. We limit internal access to staff or service partners who need the record for that purpose. Retention depends on the record and legal need. Where local law permits, you can request access, correction or removal
3
through our support path, subject to identity checks and records we must retain.

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

REQUEST SUPPORT

Where To Send A Privacy Request

A clear request route helps you control your account data without searching through unrelated pages.

DATA CONTROLS

Inside dki4d Data Controls

We handle privacy as an account process rather than a hidden setting. Phone verification connects a request to the right account, while device and sign-in records help us investigate access events.

Collection purpose

We collect account details, phone verification results, device signals and payment references for stated purposes such as sign-in support, transaction matching, security checks and handling your privacy request.

Cookie choices

Our cookies can preserve a signed-in session and help detect unusual access. You can change cookie permissions in your browser settings, but blocking required cookies may interrupt account verification or request submission.

Account security

Never send a password or one-time code in a privacy message. We may confirm your registered phone number and recent account details before giving access to personal records or changing them.

Retention timing

Retention varies by record type. A payment reference, security event or request history may remain while needed for reconciliation, fraud checks, dispute handling or a legal duty, then follow our deletion process.

Correction requests

If your phone number or account detail is wrong, submit a correction through account help with the exact field and reason. We check the request before updating information connected to your account.

Removal requests

You may ask us to remove personal data where local law permits. We first confirm identity, explain any record that must remain, and tell you which part of the request can be completed.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the practical searches people make before opening an account or sending a data request. We keep the wording tied to dki4d account steps, Indonesian payment references, device records and the support route, so you can understand what to prepare and what may happen next.

It covers account details, phone verification, device and sign-in records, cookies, payment references and privacy requests. It also explains why we use each category, who may handle it for an account purpose, how retention works and how you can ask for access or correction.

We use your phone number to create and identify the account, complete phone verification before access and respond to account requests. If the number is incorrect, submit a correction through account help; we may confirm identity before changing the record.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, including selected rail, reference details and status. These records help us match a payment question without asking you for a wallet password or one-time code.

We may record device type, browser details, IP address, sign-in time and security events linked to account access. This helps us investigate unusual sign-ins and support a request from a mobile browser or desktop browser without reading unrelated files on your device.

Sign in, open the account help area and choose the privacy or data request path. If sign-in is unavailable, use the support link at dki4d.vip. State the request type and registered phone number, then complete any identity check we require.

You can request correction or removal through account help where local law permits. Tell us which record is affected and why. We verify the request, explain any information that must remain for security or legal duties, and confirm the next step.

There is no single period for every record. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may remain while needed for reconciliation, dispute handling, security checks or legal duties. The retention period depends on the record and applicable requirements.

Privacy Policy for dki4d Account Data

Where To Send A Privacy Request

Inside dki4d Data Controls

Collection purpose

Cookie choices

Account security

Retention timing

Correction requests

Removal requests

Privacy Policy Answers For Your Account

01 What does the dki4d Privacy Policy cover?

02 Why does dki4d collect my phone number?

03 Does the Privacy Policy cover DANA and QRIS?

04 What device data can dki4d see?

05 How do I request my personal data?

06 Can I ask dki4d to correct or remove data?

07 How long does dki4d keep payment records?

Related Pages