Reference

Privacy Policy for Your Indonesia Account

Our Privacy Policy explains what kebaya33 collects when you create an account, verify your phone, use a mobile device or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesPolicy access
kebaya33 Privacy Policy for Your Indonesia Account
PRIVACY SUPPORT

Get Privacy Help Through Account Support

A clear support route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Policy questions Use the signed-in support path to ask how the Privacy Policy applies to your phone verification, device record or account contact details. We can explain the data category involved and tell you what account step is needed before we process a request.
Wallet references If a DANA, OVO, GoPay or QRIS receipt appears beside your account, send its reference through support rather than sharing a password. We use the reference to locate the matching status and limit the request to the transaction record concerned.
Access concerns When a login or phone verification issue blocks a privacy request, tell us the device path you used, such as mobile browser or desktop browser. We can separate an access problem from a data request without asking you to publish sensitive credentials.
DATA PRACTICES

How We Protect Login and Wallet Data

We keep the Privacy Policy practical by linking each data choice to an account action you can recognise.

Account details

We use the contact details and phone verification result you provide to create, maintain and protect your account. A clear account path helps us identify the right record when you ask for a copy, correction or explanation under this Privacy Policy.

Device signals

We may record browser type, operating system, approximate access time and sign-in events from the mobile or desktop path you choose. These signals help us investigate account access and are not a request for the private contents of your device.

Cookie choices

Cookies can keep a session connected and remember selected preferences when you move from account access to the lobby. You can manage cookie settings in your browser, although changing them may affect sign-in continuity or the way policy choices are saved.

Wallet matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the reference and status needed to match an account event. We do not need your wallet password, and support should never require you to disclose it.

Retention requests

We retain records only for the period needed for account operation, dispute handling, security checks and legal duties that apply where local law permits. Ask through support which category applies, and we will explain whether a deletion or restriction request can be handled.

Correction route

If your contact detail, phone number or account record is inaccurate, send a correction request from the signed-in support path. We may ask for an account step to confirm ownership before changing data connected with Live Blackjack Grand or another account activity.

Privacy Policy Answers for kebaya33 Accounts

These Privacy Policy answers address the account questions we expect before you open access or connect an Indonesian wallet. They cover collection, cookies, payment references, corrections, retention and contact steps without moving away from the policy subject. If your question concerns a particular sign-in event or receipt, use the support path while signed in so we can check the relevant record. Access depends on local law.

It covers data linked to your account, including contact details, phone verification, sign-in events, device signals, cookie choices, support messages and payment references. It also explains how we use, retain, correct and disclose those records where local law permits.

Yes. The Privacy Policy includes the DANA, OVO, GoPay, QRIS, bank transfer and virtual account references needed to match a payment status with your account. We do not need your wallet password, and we limit support checks to the relevant record.

Device type, browser path and sign-in time help us protect account access and investigate a session that does not look familiar. They also help support distinguish a mobile browser issue from a profile or phone verification request under the Privacy Policy.

Use the signed-in support path and identify the contact detail or account record that needs correction. We may ask you to complete phone verification or another account step before changing it, so the request is connected to the correct account.

You can send a retention or deletion request through account support. We assess the request by data category because security records, payment references or dispute material may need to remain for a period required where local law permits.

Cookies can keep your session connected and save policy or browser preferences while you move between account access and the lobby. You can change cookie settings in your browser, but some sign-in continuity or saved choices may then work differently.

Contact us through the support path shown after account access and describe the policy request, such as a copy, correction, retention question or wallet reference check. Do not include a password or one-time code; we will use account verification where needed.