Reference

Read the kudalaut88 Privacy Policy

Our Privacy Policy explains how we handle the account details you provide before you enter the lobby, including phone verification and wallet status for DANA, OVO, GoPay and…

Account detailsWallet recordsCookie choicesContact path
kudalaut88 Read the kudalaut88 Privacy Policy
CONTACT ROUTES

Choose a clear Privacy Policy contact path

Questions about our Privacy Policy should reach the route that matches your concern, so we can avoid sending you between account and cashier pages. We can help with an access request, a correction to your account details or a question about a payment reference. Start from the account help area when you are signed in; if access is blocked, use the contact route shown on the site and include only the details needed to locate your request.

Team online

Account access help

Ask us to explain which account details are linked to your phone verification. Use the signed-in help area when possible, and never include your password, wallet PIN or full security code in a request.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, share the transaction date, amount and reference shown in your account. We use that limited record to trace status without requesting private wallet credentials.

Privacy request

Request a copy, correction or removal of personal data through our site contact path. We may ask you to confirm account ownership before changing records, so another person cannot redirect your account details.

DATA PRACTICES

Browse how our Privacy Policy works

Our handling process follows the account actions you can see: phone verification creates an access record, a wallet action creates a payment reference, and a browser may store a cookie choice.

Account data

We may handle the details needed to create and maintain your account, including your phone verification status and selected account settings. We use them to recognise your access path and respond to account-specific requests.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can connect a cashier event with your account. We use the reference for reconciliation and status checks, not to collect your wallet PIN.

Cookies

Cookies can remember settings that affect your session and help us understand whether an access page loads correctly. Your browser controls cookie removal, while our contact path can answer questions about a stored preference.

Account security

Phone verification and sign-in checks help us distinguish your account from an unauthorised request. If access looks unusual, we may pause a change until ownership is confirmed and will not ask for your wallet password.

Retention

We keep records only as long as they serve account security, payment reconciliation, support handling or a legal requirement. A deletion request can be limited where removing a record would weaken an unresolved security or payment check.

Request changes

You can ask to access, correct or remove personal data through the site contact route. Include the account identifier and request type, then complete any ownership check we send before we change the record.

Find answers about Privacy Policy access

These Privacy Policy answers focus on the questions you may have before opening an account or asking us to change a record. They cover the data connected with phone verification, wallet references, cookies and device access. If your situation is not listed, use the contact path in this page and keep sensitive credentials out of your message.

It covers account details, phone verification, device and browser signals, cookie choices, payment references and messages sent through support. We use these records for account access, security, payment reconciliation and request handling. Service eligibility depends on local law.

The Privacy Policy covers the transaction reference, status and account link shown during a DANA or QRIS action. We do not need your wallet PIN. For a status question, send the visible reference and date through our account contact route.

Yes. You can request access to personal data through the site contact path. Tell us the account identifier and the records you want to see. We may confirm phone ownership first, which helps prevent another person from receiving account details.

You can ask us to correct an inaccurate account detail, phone verification record or contact entry. Describe the change and provide the relevant account identifier. We may keep the earlier record where it is needed for security, payment reconciliation or a legal requirement.

Send a removal request through the contact route shown on the site. We assess each record under the Privacy Policy and local requirements. Some security, payment or support records may remain when deletion would prevent an unresolved check or required retention.

Yes. The Privacy Policy covers cookies and similar browser settings on both mobile and desktop access. Your browser can clear stored cookies or change permissions. Clearing them may remove a saved preference, so you may need to select that preference again.

Use the signed-in account help path for access or correction requests. If you cannot sign in, use the public contact route displayed on the site. Include only the minimum details needed to locate your account, and never send a password, wallet PIN or full security code.