Reference

kodok4d Privacy Policy for Your Account

Our Privacy Policy explains how kodok4d collects, uses and protects the details connected with your account, including phone verification, login activity and wallet records.

Account clarityWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How Privacy Applies to Indonesian Accounts

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

This Privacy Policy covers the information we receive when you create an account, complete phone verification, sign in, contact support or use wallet actions. We may record your account identifier, device and browser details, login timestamps, requested payment rail and transaction status so we can protect

1
access and match DANA, OVO, GoPay, QRIS, bank transfer or virtual account records to the correct account. We use this information for account security, service operation, payment reconciliation and required legal requests, not for unrelated purposes. If you browse from Yogyakarta or another Indonesian location, the
2
same policy applies to the data connected with your account. Access and eligibility depends on local law; where local law permits, we provide the services described here. We may update this page when our data practices change, with the revised date shown on the policy page.

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

PRIVACY HELP PATH

Where to Ask About Your Privacy Policy

A clear contact route helps you question a data record without explaining the same issue repeatedly.

DATA HANDLING PRACTICE

What We Do With Your Account Data

We separate account security, payment matching and customer support records so each request receives the relevant context.

Collected account details

We collect details you provide for account access, such as your phone number and account identifier, plus device, browser and login data needed to detect unusual access and keep the account path functioning.

Wallet and transaction records

When you select DANA, OVO, GoPay, QRIS, bank transfer or virtual account, we retain the rail, reference and status required to match the transaction with your account.

Cookies on mobile

Cookies and similar browser storage help remember session status and security choices. If you clear them on your phone, you may need to sign in and complete account checks again.

Account security controls

Phone verification, sign-in timestamps and device signals help us investigate access concerns. We do not ask you to share a password through a support message or send sensitive details unnecessarily.

Retention and deletion

We keep records while they serve account security, payment reconciliation, support handling or legal requirements. When a record is no longer needed for those purposes, we assess it for deletion or de-identification.

Changes and access requests

You can ask what account data we hold, request a correction or question a record through account help. We verify the request before making changes so another person cannot alter your details.

Privacy Policy Answers for kodok4d

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data connected with phone verification, wallet records, cookies, device access and correction requests. If your situation is different, use the account help route and include only the details needed to identify your request.

The Privacy Policy covers account details, phone verification, device and login records, cookies, support messages, and payment status connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps confirm that the account access request belongs to you and supports security checks. We retain the verification result and related account details only for the purposes described in the Privacy Policy.

Yes. We may record the selected payment rail, transaction reference and status so DANA, OVO, GoPay or QRIS activity can be matched with your account and investigated when a receipt is unclear.

Cookies can retain session and security preferences in your browser. Clearing them may sign you out or prompt another verification step; the Privacy Policy explains this browser data use and its purpose.

You can contact account help to ask what data is held or request a correction. We first confirm your identity, then assess the request against security, payment and legal record needs.

We retain information while it supports account security, payment reconciliation, support handling or legal requirements. The retention period can differ by record type, and we remove or de-identify data when appropriate.

Yes, access depends on local law. Where local law permits, we apply the policy to the account data described here; contact account help if you need clarification about your request.

kodok4d Privacy Policy for Your Account

Where to Ask About Your Privacy Policy

What We Do With Your Account Data

Collected account details

Wallet and transaction records

Cookies on mobile

Account security controls

Retention and deletion

Changes and access requests

Privacy Policy Answers for kodok4d

01 What does the kodok4d Privacy Policy cover?

02 Why does kodok4d need phone verification?

03 Does the Privacy Policy include wallet data?

04 How do cookies affect my kodok4d account?

05 Can I request a copy or correction of my data?

06 How long does kodok4d keep personal data?

07 Does access under this Privacy Policy depend on location?

Related Pages