Reference

Privacy Policy for Your jaya23 Account

Our Privacy Policy explains how we handle the details you provide when opening a jaya23 account, signing in from a mobile browser, checking Majapahit Empire Slots, or using…

Account clarityPayment contextMobile accessYour data choices
jaya23 Privacy Policy for Your jaya23 Account
CONTACT PATHS

Privacy Help Beside Your Account Route

A clear contact path matters when a privacy question is linked to a phone check, wallet status, or sign-in session.

Account data request Use the support panel to ask which account details are connected with your profile. We may request a phone verification step before discussing private account data, so the request reaches the correct account holder rather than someone using a shared device.
Wallet status question If a DANA, OVO, GoPay, QRIS, or bank transfer reference appears incorrectly, send the payment date and reference through the cashier support path. Do not include a wallet password or full security code; we use the reference to locate the relevant record.
Device access concern When a mobile browser session, phone change, or unfamiliar sign-in raises a privacy concern, contact us through the account support panel. Tell us the approximate time and device type, and we can check the session record without asking you to share your private password.
DATA PRACTICES

What This Policy Means In Practice

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

Account creation

When you open an account, we use the details you submit to create the profile and support sign-in. Phone verification may be required before access to account records. Please keep your contact details current so a privacy request can be matched to your account.

Payment references

A wallet name or bank rail can appear beside a transaction reference, such as QRIS, DANA, or Bank Transfer BCA. We use that record to identify payment status and resolve a cashier question. We do not ask for your wallet password through support.

Cookies and sessions

Cookies and similar browser storage can remember a session choice, preserve sign-in flow, and help detect repeated failed access. On a shared phone, sign out after use and clear browser storage if you do not want the next person to see an active account session.

Account security

We use phone verification, session signals, and sign-in records to protect account access. If you change devices, a new browser session may require another check. Never send your password, wallet PIN, or one-time security code in a privacy request.

Retention period

We retain account, payment, and support records for the period needed to operate the service, investigate disputes, protect against misuse, or meet applicable legal duties. When a record is no longer needed for those purposes, we remove it or separate it from direct account identifiers.

Change requests

You can ask us to correct outdated profile details or explain how a record is used through the support panel. We may need a phone verification step before making a change. Where local law permits, we will explain any reason a requested action cannot be completed immediately.

Privacy Policy Questions About jaya23

These Privacy Policy answers focus on the account actions you are most likely to search for before opening jaya23. They explain what we collect, why payment references appear, how mobile sessions work, and which route to use when you want access, correction, or clarification about your data.

The jaya23 Privacy Policy covers data linked to account creation, phone verification, sign-in, device sessions, payment references, and support requests. It explains why we use those records, how long we retain them, and how you can ask about correction or access where local law permits.

Yes. The Privacy Policy explains how we handle transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account steps. We use those references to display status and resolve account questions, while your wallet password and private security code remain yours.

We use your phone number for account creation, sign-in support, and phone verification before certain account discussions. It can help us match a privacy request to the correct profile. We do not need your one-time security code in a support message or privacy request.

The policy can cover browser type, operating system, session time, approximate access signals, and security events connected with your account. These details help us investigate an unfamiliar mobile browser session or protect sign-in. They are not collected to ask for your private device password.

Send a request through the jaya23 support panel and include your account identifier plus the action you want, such as access or correction. We may ask for phone verification before discussing private records. Where local law permits, we will explain the next step and any applicable restriction.

We keep payment references and support messages while they are needed for account operation, security checks, dispute handling, or applicable legal duties. After that period, records are removed or separated from direct identifiers under our retention process. A request can ask us to explain the category involved.

No separate mobile policy applies. The same Privacy Policy covers access from a phone, tablet, or desktop browser. A mobile session may create browser and security records, especially after a device change. On a shared phone, sign out and clear stored session data after use.