Reference

mejawd Privacy Policy, Clearly Explained

Our Privacy Policy explains what mejawd collects when you open an account, browse Andar Bahar or Rocket Crash, and use the lobby from an Indonesian phone.

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

Open the Privacy Policy Before Account Access

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

This Privacy Policy covers details you submit during account creation, including contact data used for phone verification before account access. We also record technical signals such as device type, browser path, login time and pages opened, so we can keep a session connected to the right

1
account. Payment records can include the rail you select, such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, together with status and reference details needed for account reconciliation. Browsing Queen of Bounty, Super Bingo or Royal Fishing may create activity records linked to your
2
account. We use these records for access, support, payment checks, policy administration and required legal requests. Where local law permits, you may use the available account path; eligibility depends on local law. We do not ask for unrelated details as part of this policy process.

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

CONTACT ROUTES

Browse mejawd Support For Privacy Requests

A clear contact route helps when you want to ask about a record, correct an account detail or understand a cookie choice.

Account privacy request Use the support route attached to your account and state whether you want access, correction or removal guidance. We may ask for the verified phone detail before discussing account records.

Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference and date. We use those details to trace the correct account entry.

Cookie and device help Tell us the device path, such as Android browser or desktop browser, and describe the cookie prompt or login issue. That keeps the privacy reply focused on your session.

DATA PRACTICE

Explore How We Handle Your Records

Our policy work follows the same account path you use: sign in, verify the requested detail, then ask about a specific record.

Account collection

When you create an account, we collect the contact details needed for the account step and phone verification. We use them to connect access requests with the correct account record.

Device signals

A mobile or desktop session can provide browser, device and login details. These signals help us distinguish an account session from an unfamiliar access attempt and support a precise privacy reply.

Cookie choices

Cookies can remember session settings and help us understand which policy page brought your request forward. You can raise a cookie question through support if a choice is unclear.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are retained with status details for reconciliation. A receipt reference helps us locate the matching record.

Account protection

Before sharing account-specific data, we may compare the request with your verified phone or account detail. This step reduces the chance of exposing records to the wrong person.

Retention and changes

We keep records only for the operational, dispute and legal purposes that apply to them. Ask support to access or correct a detail, and we will explain the available next step.

Check Privacy Policy Answers Before Joining

These Privacy Policy questions cover the account and wallet situations you are most likely to face before opening an account. Each answer points back to a concrete action, from checking the phone detail on file to sending a payment reference through the support route. Account access depends on local law, and we handle requests within the limits that apply.

It covers account details, phone verification, device signals, cookies, lobby activity records and payment references. This includes activity connected with Andar Bahar, Rocket Crash and the wallet rails shown in the policy.

We use the phone detail for the account step and verification before account access. It also helps us match a privacy request to the right account instead of revealing records to another person.

Yes. It covers DANA, OVO, GoPay and QRIS references, plus bank transfer and virtual account status details. These records help us reconcile a receipt with the account that made the request.

You can send an access request through the account support route. Include the verified phone or account detail, and we will explain what can be provided under the applicable policy and local law.

Contact support with the account detail that needs correction and explain the change clearly. For a wallet entry, add the DANA, OVO, GoPay or QRIS reference so we can check the matching record.

Cookies may keep your session settings and connect a policy visit with the device path you used. If an Android or desktop browser shows an unclear choice, ask support about that cookie record.

Retention depends on the record type and the operational, dispute or legal purpose attached to it. Ask through support for the applicable handling of your account, device or payment record.

mejawd Privacy Policy, Clearly Explained

Browse mejawd Support For Privacy Requests

Explore How We Handle Your Records

Account collection

Device signals

Cookie choices

Payment records

Account protection

Retention and changes

Check Privacy Policy Answers Before Joining

01 What does the mejawd Privacy Policy cover?

02 Why does mejawd need my phone number?

03 Does the Privacy Policy include DANA and QRIS data?

04 Can I ask mejawd to show my stored data?

05 How do I correct an error in my account record?

06 How does mejawd use cookies on my phone?

07 How long does mejawd keep Privacy Policy records?

Related Pages