Reference

Privacy Policy For Your kayu55 Account

kayu55 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA and QRIS for wallet activity.

Account recordsWallet statusDevice controlsCookie choices

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

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

Our Privacy Policy covers the details you provide during account creation, including contact and verification records, along with technical data from the phone or computer used to sign in. We also record the status of payment requests involving DANA, OVO, GoPay, QRIS, bank transfer or a

1
virtual account so we can match activity to your account and investigate errors. We use this data for access, security, service operation and support, not for unrelated purposes. Where local law permits, we retain records for the period needed for these purposes or for a valid
2
legal request. If access or eligibility is discussed, it depends on local law. The policy applies when you browse the kayu55 site, open an account or ask us to change your personal data.

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

HELP WITH PRIVACY

Get Clear Answers About Your Data

A clear support path helps when a privacy request is more specific than a sign-in question.

Privacy request Ask us to access, correct or explain personal data held for your kayu55 account. Include your account contact detail and a short description of the request; we will use account checks before disclosing or changing records.

Wallet record If a DANA, OVO, GoPay or QRIS status appears beside the wrong account activity, send the relevant reference and date through our support route. We use the payment record to investigate without asking you to share a wallet password.

Access concern If your account opens on one device but not another, tell us the device path and sign-in stage. We can review the security event and explain what data was used, while keeping verification details limited to the request.

DATA CONTROL ROOM

How We Handle Account Privacy

Privacy controls work best when each data use has a clear reason. We separate account access, payment matching, security checks and support handling so a request can be investigated without exposing unrelated…

Data collection

We collect account details you submit, verification results needed for account access, and technical events such as sign-in time, device type and security signals. These records help us identify your account and investigate unusual access without treating every device detail as a marketing profile.

Cookie handling

Cookies can remember a session or a selected setting so the site behaves consistently after you move from login to the lobby. Ask us which cookie category applies to your browser activity and request available changes through the privacy support path.

Account security

We use account checks before discussing personal records or changing contact details. Never send a wallet password or full sign-in secret in a support message. If a new phone triggers a check, that step helps separate your request from unauthorised access.

Payment matching

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account request can create a reference, amount status and processing time record. We use those fields to match activity, resolve a stalled status and avoid attaching a payment event to the wrong account.

Record retention

We keep personal and payment-related records only for as long as needed for the stated service, security or legal purpose, subject to local requirements. A request to remove data may need an account and legal review before we confirm the outcome.

Change requests

You can ask for a copy, correction, clarification or applicable deletion of your personal data. State the exact record you mean, such as a phone detail or wallet reference. We verify ownership first, then explain the next step and any limits.

Privacy Policy Answers Before Access

These Privacy Policy answers focus on the decisions you may make before opening a kayu55 account: what is collected, why wallet records appear, how device access is handled and how to request a change. Each answer keeps the scope on personal data and gives you a practical path for asking us to check a record.

It covers account details, verification records, device and sign-in events, cookies, payment status records and support requests connected with kayu55. We use them for access, security, payment matching and service handling. If eligibility or access is discussed, it depends on local law.

Yes. The Privacy Policy includes the payment reference and status needed to match DANA or QRIS activity with your account. Similar handling applies to OVO, GoPay, bank transfer and virtual account records. We do not need your wallet password to investigate a status.

We may record device type, browser or app session details, sign-in time and security signals connected with account access. This helps us review a new-phone check or unusual login. Ask support to explain a device record, but do not send your sign-in secret.

Send a privacy request through our support route with the contact detail attached to your account and the records you want, such as account data or payment status. We first verify ownership, then explain the available copy process and any local-law restriction.

You can ask us to correct an inaccurate account detail, including a contact record, after we confirm that you control the account. Describe the field and the correct value without sharing a wallet password. We will tell you if an additional verification step applies.

We retain records for the time needed to provide account access, match payments, protect security, answer support requests or meet a valid legal requirement. The period can depend on the record and local requirements. You can ask us to explain why a record remains.

Contact us with your browser or device path and ask which cookies relate to session operation or preferences. We can explain the category and available control. Removing a functional cookie may affect sign-in continuity, so we will describe that effect before making a change.

Privacy Policy For Your kayu55 Account

Get Clear Answers About Your Data

How We Handle Account Privacy

Data collection

Cookie handling

Account security

Payment matching

Record retention

Change requests

Privacy Policy Answers Before Access

01 What does the kayu55 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS activity?

03 What device data does kayu55 collect?

04 How can I request a copy of my personal data?

05 Can I correct details on my kayu55 account?

06 How long does kayu55 keep privacy records?

07 How do I ask about cookies in the Privacy Policy?

Related Pages