Reference

kebaya4d Privacy Policy for Your Account

Our Privacy Policy explains how we use the account details, wallet records and device data connected with your kebaya4d access.

Account dataWallet recordsDevice choicesCookie controls
kebaya4d kebaya4d Privacy Policy for Your Account
REQUEST SUPPORT

Help With Privacy Requests and Wallet Records

You can ask us about a personal data request without explaining your concern in a public message.

Account request Use the support form after signing in and name the account detail you want accessed, corrected or removed. We may ask for phone verification before discussing private records.
Wallet record For DANA, OVO, GoPay or QRIS questions, send the transaction reference and date rather than a full wallet password. We use those details to locate the relevant payment record.
Device access If a browser or phone appears in an account security record, tell us the device type and approximate login time. This gives our support desk a focused path for checking access.
DATA HANDLING

How We Handle Account Privacy

Our handling approach follows the same practical steps you see in the account flow: collect what is needed, use it for a stated purpose and keep access limited.

Account details

We may handle your name, phone number, verification status and account activity to create access, protect the account and answer requests. Phone verification helps us avoid discussing private records with the wrong person.

Cookies and sessions

Cookies and similar session tools can keep you signed in, remember security choices and connect a device session to your account. You can manage cookie settings in your browser, though some account steps may then need repeating.

Security checks

We may record device type, browser details, login time and security events when you enter the account. These records help us identify unusual access around the lobby, wallet pages or phone verification.

Retention period

We keep account and transaction records only for as long as needed for the stated service, security and legal purposes. The period can differ by record type and may depend on local law.

Change requests

To request a correction, send the account phone number, the field to change and the reason through our support form. We may verify your account before changing a personal record.

Contact route

Questions about this Privacy Policy should go through the signed-in support path. Include a DANA, QRIS or login reference only when relevant, and never send your password or full wallet credentials.

Privacy Policy Questions Answered

These Privacy Policy answers cover the searches we hear most often before account access. We focus on the records created by phone verification, wallet activity, cookies and device sessions, so you can decide what to share and how to contact us.

It covers account details, phone verification, wallet and transaction records, cookies, device data, security events, retention and requests to access or change your personal data.

We may collect your phone number, account details, verification status, device and browser data, login events and relevant wallet records from DANA, OVO, GoPay or QRIS.

We use a DANA or QRIS reference, date and account link to match a payment record, answer a status request and protect the account. We do not need your wallet password.

Yes. Send the request through the signed-in support form, identify the record or field and complete any account check we request. The response path depends on local law.

Cookies can keep a session active, remember security choices and support account navigation. You can change browser cookie settings, but turning them off may require repeated login or verification steps.

Retention varies by record type and purpose. We keep records for service, security and legal needs, then remove or de-identify them when applicable; timing depends on local law.

Sign in, open the support form and describe the privacy concern clearly. Add your linked phone number and a relevant login or wallet reference, but never include a password.