Reference

key4d Privacy Policy for Your Indonesia Account

Our Privacy Policy explains what we collect when you open a key4d account, sign in from a phone or desktop, verify your phone, and use wallet options such…

Account clarityWallet detailCookie choicesAccess requests

Browse Our Lobby Read FAQ

Open the Privacy Policy Before Account Access

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

This Privacy Policy applies to the key4d website, account journey, mobile browser path and support conversations connected with your use in Indonesia. We may process your name, phone number, verification result, sign-in events, device details, approximate location signals, wallet references and transaction records so we can

1
identify the account connected to a request. DANA, OVO, GoPay and QRIS may appear in your payment history, but we do not treat a wallet name as permission to use unrelated data. Access or eligibility depends on local law, and this policy does not change those
2
requirements. When you move from a phone to desktop, the same account records remain subject to these rules.

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

CONTACT ROUTES

Find Policy Help Through Your Account Path

A clear contact route helps you ask about a Privacy Policy matter without sending sensitive details to the wrong place. We ask you to use the support route connected with your key4d account, especially when a phone verification record, wallet reference or payment receipt needs checking. If you are in Bandung or elsewhere in Indonesia, the same request path applies.

Team online

Account request

Use the support route after signing in when you want a copy of account data, an explanation of a phone verification record, or help identifying the details linked to your account.

Receipt query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, include the receipt reference and date; we use those details to locate the relevant privacy request.

Access difficulty

If login or wallet status stalls before you can reach support, share only the contact details needed to locate your account and never send a password or full wallet PIN.

DATA HANDLING

Explore How We Handle Your Account Details

We keep our privacy process practical: collect what supports an account action, protect access records, and give you a route to question them.

Collected details

We may receive your contact details, phone verification result, login timestamps, device type, browser signals and wallet or bank references when those details are needed to operate your account.

Cookie controls

Cookies and similar browser storage can remember session state and security preferences. You can manage browser permissions, although blocking required storage may interrupt sign-in or policy-request access.

Account security

Keep your password private and sign out on shared devices. We use sign-in and device events to investigate unusual access, and we may ask for phone verification before discussing account records.

Retention period

We retain account, payment and security records only for the period needed for the stated purpose, dispute handling, fraud checks or legal duties; retention can differ by record type.

Change requests

You can ask us to correct inaccurate contact details or clarify how a record is used. Send the request through account support so we can confirm that it concerns your account.

Deletion questions

You may ask whether eligible records can be removed. We assess the request against legal, security and payment-record duties, then explain any data we must continue retaining.

Browse Answers About Privacy Policy

These Privacy Policy answers focus on the account actions you are most likely to question before opening an account or contacting support. We keep the examples close to Indonesia access, mobile devices, phone verification and local wallet records, while noting that requests depend on local law.

It covers account details, phone verification, sign-in events, device signals, cookies, support requests and payment references connected with your use of key4d through the Indonesia website.

We use your phone number to create and protect the account, complete a phone verification step, connect support requests to you and investigate unusual sign-in activity where local law permits.

Yes. The policy covers wallet names, payment references, receipts and related status details from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We may process device type, browser signals, session events and security-related access details. These records help us protect your account when you switch between a mobile browser and desktop.

Sign in and contact us through the account support route, stating that you want a copy of your personal records. We may request phone verification before releasing account-specific details.

You can request correction or deletion of eligible records through account support. We assess each request against security, payment, dispute and legal retention duties before responding.

Retention depends on the record and its purpose. Account, payment and security details may remain for dispute handling, fraud checks or legal duties, after which eligible records can be removed.

key4d Privacy Policy for Your Indonesia Account

Find Policy Help Through Your Account Path

Account request

Receipt query

Access difficulty

Explore How We Handle Your Account Details

Collected details

Cookie controls

Account security

Retention period

Change requests

Deletion questions

Browse Answers About Privacy Policy

01 What does the key4d Privacy Policy cover?

02 Why does key4d need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device data can key4d collect?

05 How can I request a copy of my data?

06 Can I ask key4d to correct or delete data?

07 How long does key4d keep Privacy Policy records?

Related Pages