Reference

raja khodam 89 Privacy Policy, Made Clear

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS for account funding.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
raja khodam 89 raja khodam 89 Privacy Policy, Made Clear
HELP WITH DATA

Get Policy Help Through Your Account

A clear contact path matters when a Privacy Policy question affects your account or wallet record. Start with the account help route and include the email or phone detail tied to your profile, plus the specific request you want us to handle. We may ask for an account step or payment reference so we can locate the correct record without exposing another person’s data. Our support path covers access, correction, cookie choices, retention questions, and payment-record concerns.

Team online

Account data request

Use the account help path to ask for a copy of personal data linked with your profile. Include your registered contact detail and the request type, so we can distinguish your account from another profile before responding.

Wallet record check

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record looks incorrect, send its reference through account support. We use the reference to locate the payment event without asking you to share a wallet password.

Cookie preference help

For questions about cookies or device sessions, contact us through the same support route and name the browser or phone you used. We can explain the relevant setting and help separate cookie data from account records.

HANDLING YOUR DATA

What We Do With Account Data

Privacy work is part of each account step, from phone verification before access to a wallet-status check after a payment request.

Collection at account opening

When you create an account, we collect the contact details and verification result needed for access. A clear phone verification step helps us confirm that the account request belongs to you before account data is connected with lobby activity.

Payment record separation

A DANA, OVO, GoPay, or QRIS reference helps us match a payment status, while bank transfer and virtual account details support reconciliation. We do not need your wallet password for this check, and payment records remain tied to the relevant account event.

Cookies and device signals

Cookies may keep a sign-in session working and help us understand whether a request comes from a phone, tablet, or computer. Browser type, operating system, and session time can support security checks, while your browser settings provide controls for cookie storage.

Account security controls

We use sign-in checks, phone verification, session controls, and payment-reference matching to reduce mistaken access. If your device changes or a login looks unusual, support may ask for account details before discussing personal data or wallet status.

Retention and removal

We keep personal data for as long as it serves account support, security, payment reconciliation, dispute handling, or legal duties. When a retention reason ends, we remove or separate the record according to our internal handling process and applicable local requirements.

Requests to change data

You can ask us to access, correct, or remove personal data through account support. Tell us which field or record needs attention, such as a phone detail or QRIS reference, and we may verify account ownership before making a change.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before account opening. They cover what we collect, how payment references are used, how cookies work on a mobile device, and how you can request a change. If your question involves eligibility or access from Indonesia, that decision depends on local law and your circumstances.

The Privacy Policy covers account details, phone verification, sign-in sessions, device signals, cookie use, lobby activity, support messages, and payment references. It applies when you create or access an account and when DANA, OVO, GoPay, QRIS, bank transfer, or virtual account status is checked.

We may collect your registered contact details, verification result, device and browser signals, session times, support messages, and records connected with account actions. Payment references can show whether a DANA or QRIS event matches your account, but we do not request your wallet password.

Use the account help path and ask for a personal data access request. Include the phone or email attached to your account and describe the records you need, such as verification details, cookie questions, or a GoPay payment reference. We may verify ownership first.

Yes, where local law permits, you can request a correction or removal through account support. Identify the specific field or record, such as a phone number or bank transfer reference. We may retain data needed for security, dispute handling, payment reconciliation, or legal duties.

Cookies can maintain a sign-in session and support security checks when you use a phone or tablet. We may also record browser and operating-system details. Your browser settings control cookie storage, and support can explain which cookie concern relates to a session rather than your account profile.

Yes. The Privacy Policy includes payment references and status records for DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity connected with your account. We use those details to match an event, answer a support request, and investigate a disputed status.

Yes, access and eligibility depend on local law. Our Privacy Policy still explains how personal data is handled when you visit the site, open an account, or contact support. If you need a policy answer for your region, use the account help route with your location context.

Related Pages

raja khodam 89 Indonesia raja khodam 89 Casino About Us Account information Flores Fortune Reels