Reference

Privacy Policy for Your rjm88 Account

rjm88 Privacy Policy explains what account, device and wallet details we use when you open an account, sign in and access the lobby.

Account detailsWallet statusDevice accessCookie choices
rjm88 Privacy Policy for Your rjm88 Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A direct support path helps when you want to understand a Privacy Policy request rather than guess which account screen to use.

Account data request Ask us to explain the account details connected with your rjm88 access, including the…
Wallet reference check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment reference…
Access and correction Request a copy, correction or clarification of data covered by this Privacy Policy through…
DATA HANDLING DETAILS

What We Do With Account And Device Data

We keep our Privacy Policy practical by linking each data use to a real account action.

Account creation

When you open an account, we use the details required to create and maintain that account path. Clear phone verification before account access can help us distinguish your request from an unapproved sign-in, while the Privacy Policy explains why the related record exists.

Sign-in protection

Sign-in events and basic security signals can help us identify unusual access to your account. If you move between a phone and desktop, those records may help with an access question. We do not ask you to reveal your password when raising a privacy concern.

Mobile device context

The mobile path may use device and browser context so the account page can load correctly and keep a session connected to your request. We do not present this as a separate mobile application. You can ask us what device-related record is linked to your account.

Cookies and storage

Cookies or similar storage can retain sign-in preferences and help us understand whether a requested account page is functioning. Your browser settings can control some storage choices, though changing them may affect access to the account page or require you to sign in again.

Payment records

A wallet choice such as QRIS, DANA, OVO or GoPay can produce a status or reference record needed to match the payment step with your account. Bank transfer and virtual account records are handled for the same account-led purpose and are not treated as general profile details.

Retention and requests

We retain records for the period needed for the account request, security checks, dispute handling or applicable legal duties. You can contact us to ask what remains connected to your account, request a correction or ask whether deletion is available where local law permits.

Privacy Policy Answers For rjm88 Accounts

These Privacy Policy answers focus on the questions you are most likely to have before opening an account or checking a wallet status. We keep the examples tied to the actual account path: phone verification, mobile sign-in, cookies, payment references and requests for access or correction. If your situation is different, use the support path with the smallest useful set of account details.

It covers account details, sign-in and device records, cookie-related storage, payment references and requests made through the account path. It also explains how we handle questions about correction, access and deletion where local law permits, including records linked to DANA, OVO, GoPay or QRIS.

Phone verification helps connect an account access request with the person who created the account and helps us investigate an unusual sign-in. The Privacy Policy treats related verification records as account-security data. We will not ask you to send your password when you contact support.

Yes. The Privacy Policy covers device and browser context used to support a mobile or desktop sign-in and investigate account access. You can ask us what device-related record is connected with your account. Browser settings may also affect cookies and whether a session remains active.

When you select DANA or QRIS, we may retain the payment status or reference needed to match that step with your account. OVO, GoPay, bank transfer and virtual account records follow the same account-led purpose. Send only the relevant reference when requesting a correction.

You can contact our support route and state whether you want access, correction or clarification. We may verify account ownership before responding. The available response depends on local law, and we may need to protect another person's data or retain a record required for security.

We retain records for the period needed to operate the account request, check security, resolve a payment dispute or meet applicable legal duties. The exact period can depend on the record. Ask us about a specific account or payment reference so we can assess it accurately.

Use the account help path and identify the issue as a cookie, device, account or payment-data question. Include your account contact detail and a short description, but not your password or wallet access code. We can then explain the relevant Privacy Policy choice where local law permits.