Reference

kebun4d Privacy Policy: Clear Data Choices

Your kebun4d Privacy Policy explains what we collect when you open an account, use a mobile browser, or select DANA and QRIS at the cashier.

Account accessWallet recordsCookie choicesChange requests
kebun4d kebun4d Privacy Policy: Clear Data Choices
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear account path helps us locate the right record without asking you to repeat sensitive wallet details. Start with the support link after signing in, include your account identifier and the relevant date, and mention whether the question concerns DANA, OVO, GoPay, QRIS, bank transfer, or device access. If you cannot sign in, use the account-help route and provide only the minimum details requested.

Team online

Account support route

Sign in, open account support, and select a privacy question. We can connect your request to the correct account record without asking for your wallet PIN or full payment password.

Receipt and status check

Attach the payment reference and date when a DANA, OVO, GoPay, or QRIS status needs checking. We use those details to locate the transaction record and reply with the next step.

Access recovery path

If login stalls, use the account-help path from the sign-in screen. We first verify the account step before discussing stored data, helping keep a privacy request tied to the right person.

DATA PRACTICE

Six Practical Privacy Controls

Our privacy process follows the same account flow you use to reach the lobby: identity check, wallet reference, device session, and support request.

Account details

We use the details entered during account creation and phone verification to identify your account, support sign-in, and connect a privacy request with the correct account holder.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference helps us reconcile a transaction. We do not need your wallet PIN to investigate a status question.

Device sessions

Mobile and desktop browsers may send device type, operating system, IP address, and session time. We use these signals to spot unusual access and help secure your account.

Cookie controls

Cookies can keep a session active, remember selected settings, and measure page activity. You can manage browser cookie controls, though changing them may affect account access.

Retention handling

We retain account, payment, and security records only as long as needed for the stated purpose, dispute handling, account protection, or a legal duty that applies.

Correction requests

Ask us to correct inaccurate account or contact data through support. Include the affected field and account identifier; we may request phone verification before making a change.

Privacy Policy Questions Before Account Access

These answers cover the questions we hear before an account is opened or a wallet record is checked. They explain the kebun4d Privacy Policy without replacing the policy text or the legal rules that apply to your location. If your situation is not listed, use the account support route and describe the specific record or request.

It covers account details, phone verification, device sessions, cookies, wallet and bank references, retention, security handling, and requests to access or correct data when you use kebun4d.

We mention DANA and QRIS because selecting either rail creates account and transaction records such as a reference, time, amount, and status needed for reconciliation.

No. Do not send a DANA, OVO, GoPay, or other wallet PIN through support. We use the payment reference and account verification steps to investigate a status.

Sign in, open account support, and request a data access response. Include your account identifier and the record type you want checked; we may verify your phone first.

Yes, you can request a correction through account support. State the inaccurate field and your account identifier, then complete any phone verification needed before we change the record.

When you sign in through a mobile browser, we may receive device type, operating system, IP address, language, and session events for access security and troubleshooting.

Yes. Account access and eligibility depends on local law. Where local law permits, you can contact us about the Privacy Policy, stored records, or a correction request.