Reference

kekar4d Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you create a kekar4d account, sign in from a phone, or use DANA, OVO, GoPay and QRIS for account activity.

Clear collection rulesWallet activity contextAccount access requests
kekar4d kekar4d Privacy Policy for Your Account
CONTACT DATA HELP

Get Privacy Policy Help Through Your Account

A privacy question should not be mixed with a stalled wallet status.

Account contact path Open the account support path and state that your request concerns the Privacy Policy.
Wallet record question For DANA, OVO, GoPay or QRIS entries, share the date, amount reference and wallet…
Access correction request If your phone, email or verification detail is outdated, ask for a correction through…
PRACTICAL PRIVACY

What We Do With Account Details

Privacy work is part of the account flow, not a separate promise hidden from you.

Collection

We collect details needed for an account step, such as your contact information, phone verification result, login events and payment…

Cookies

Cookies and similar device signals can help retain your session, remember a selected language or detect an unusual sign-in.

Account security

We use account checks around phone verification and sign-in activity.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a transaction record.

Retention

We keep records for as long as needed for the stated account purpose, dispute handling, security checks or a legal…

Your request

You can ask what personal details we hold, request a correction, question a use, or ask about deletion through the…

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the account actions you are most likely to take: opening access, checking a wallet reference, changing a phone detail, or asking how a device record is used. If your question is not listed, contact us through the account route and describe the specific record without including secret credentials.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps connect account access with the right contact detail and supports security checks. We may use its result when you request a correction or ask about an account record.

Yes. We may handle device, browser and login signals used for session continuity or unusual access checks. These signals help us assess an account event without reading unrelated content on your device.

Use the account contact path and name the records you want, such as profile details, login history or wallet references. We may ask for an account confirmation before sending or changing personal data.

You can request a correction through account support. Tell us which field is wrong and provide the current detail through the secure account route; do not include a password, PIN or one-time code.

Retention depends on the purpose of the record, security needs, dispute handling and legal requirements. We address removal when information is no longer needed for those purposes.

Yes. Account access and related data handling depend on local law and apply where local law permits. If your location or eligibility changes, contact us before submitting new account details.