Reference

Open rajaalam Privacy Policy Before Access

Our Privacy Policy explains how rajaalam handles your account details, phone verification, wallet records and device activity before you enter the lobby.

Account dataWallet recordsCookie choicesPolicy requests
Explore Our Lobby Read FAQ
rajaalam Open rajaalam Privacy Policy Before Access
CONTACT PATH

Check Privacy Help Beside Account Access

A clear contact path matters when you want to ask about personal data rather than a wallet balance. We direct privacy questions through the support route connected to login and the cashier area, where you can identify your account and describe the request. Include the email or phone detail linked to your account, plus a payment reference only when it is relevant. We use that context to avoid sending an answer to the wrong account.

Team online

Account questions

Ask through the support path beside login when you need to know what account details we hold, why phone verification appears, or how to request a correction. We may ask you to confirm account details before discussing private records.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, include the related receipt reference if you have one. Our support route can separate payment status records from broader account data without asking you to share a wallet password.

Policy changes

When you think a policy change affects your account, contact us from the same login path where possible. Tell us the section you are asking about and the account step involved, such as phone confirmation or cashier access.

DATA PRACTICE

Explore How Privacy Works On Mobile

The practical controls below show how we apply this Privacy Policy during ordinary account use. We separate account identity, payment references and device signals so each record has a clear purpose.

Data we receive

We may receive your account contact details, phone verification result, sign-in events, device and browser signals, support messages and payment references. For QRIS or bank transfer activity, the record helps us match a receipt or status to the correct account.

Cookies on devices

Cookies can keep a session recognised, remember selected settings and help us identify unusual sign-in activity. On a phone or desktop browser, you can adjust cookie controls through browser settings, though some account functions may then need another sign-in.

Account security

Phone verification supports the account access step, while sign-in and device events help us investigate unusual activity. Never send a password or wallet PIN through support. We may request account confirmation before discussing private records.

Payment separation

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference is used for payment matching and status checks. We do not need your wallet password to answer a receipt question, and you should not place that password in a message.

Retention approach

We retain account, support and transaction records only for the period needed for account operation, security checks, dispute handling and legal duties. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Change requests

You can ask us to correct account details, explain a data use, or clarify a retention question through the support path near login and cashier access. State the requested change clearly and use the contact detail linked to your account.

Browse Answers About Privacy Policy

These answers address the Privacy Policy questions you are most likely to have before opening an account or returning to the lobby. They focus on account identity, wallet records, cookies, device activity, retention and contact steps. If your situation is not covered, use the support route near login or cashier access and describe the exact account action involved.

The rajaalam Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It applies when you open an account, access the lobby, use DANA or QRIS, or ask us to check a wallet receipt.

Phone verification helps connect account access with the contact detail you provided and supports checks when a sign-in looks unusual. We may ask you to confirm account details before discussing private records through support. Access depends on local law.

Yes. The Privacy Policy covers payment references and status records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These details help match a receipt or cashier event to your account; they do not require your wallet password.

We may record device type, browser signals, session events and security activity connected with account access. A phone session and a desktop session can create different cookie settings. These signals help protect sign-in activity and are handled under this Privacy Policy.

Use the support contact path shown beside login and cashier access, preferably from the account connected to the request. State whether you want a correction, an explanation of data use, or a retention clarification. We may confirm your identity first.

We keep account, support and transaction records for the period needed to operate the account, investigate security events, resolve disputes and meet legal duties. The applicable retention process determines when records can be removed or no longer used.

Contact us through the support route placed near login and the cashier area, then name the Privacy Policy section or change you are asking about. Include your linked account contact detail, but never send a password, wallet PIN or full payment credential.

Related Pages

rajaalam Indonesia ShopeePay Deposit Guide FAQ Account information About Us