Reference

Open rajabom Privacy Policy Before Account Access

Our rajabom Privacy Policy explains how we handle your account details, phone verification, device signals and wallet records before you enter the lobby.

Account dataWallet recordsDevice choicesCookie controls
Browse Our Lobby Read FAQ
rajabom Open rajabom Privacy Policy Before Account Access
HELP DESK PATH

Check Privacy Help Through Account Support

A clear contact path helps when you want to ask about a data field, cookie choice or wallet record. Use the support route attached to your rajabom account and include the phone number or account reference connected to your request. We can then check whether your question concerns login, DANA or QRIS status, device access or a policy request. For your safety, we ask you to share only the details needed to locate the account, never a wallet PIN or login password.

Team online

Account contact

Send your Privacy Policy question through the account support path and include your registered phone number. We use that reference to locate the right record without asking for your password, DANA PIN or OVO security code.

Wallet status

If a QRIS, GoPay or bank transfer receipt is unclear, mention the payment rail and the account reference. Our support desk can separate a policy question from a transaction-status question before checking the relevant record.

Access concern

A phone verification prompt or unfamiliar device can be raised through the same support route. Tell us what appeared and when; we can review the account-access record while keeping sensitive sign-in details out of the conversation.

DATA PRACTICE

Explore How rajabom Handles Your Data

We keep this policy practical by linking each data category to an account task: phone verification supports account access, device records help detect unusual sign-ins, and payment references…

Account details

When you open an account, we handle the contact details and verification data needed to identify that account.

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer record can contain a reference, amount status and time.

Device signals

Your phone or desktop may provide browser, session and device signals during login.

Cookie choices

Cookies can keep a session working, remember a language or display preference and help us understand page errors.

Retention requests

We keep account and payment records for the period needed to operate services, address disputes, protect account access and meet…

Change a record

Where local law permits, you can request access, correction or another data action through support.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. They explain what rajabom may record, how you can ask for a change and what happens when access depends on local law. If your situation is specific, use the account support path with only the details needed for identification.

The rajabom Privacy Policy covers account details, phone verification, login and device signals, cookies, wallet or bank payment references, support conversations and retention. It applies when you access account services where local law permits, while DANA, OVO, GoPay, QRIS and bank providers keep their own policies.

Phone verification connects an account request to the correct contact detail and helps us respond to access or wallet-status questions. It can also help identify an unusual sign-in. We do not ask you to provide a phone password, wallet PIN or payment security code.

The Privacy Policy allows us to handle payment references, status and timing for DANA, QRIS, OVO, GoPay, virtual account and bank transfer activity. This helps match a receipt to your account. The payment provider remains responsible for its own wallet credentials and separate data practices.

Use the account support path and state whether you want access to a record, correction of a field or another available data action. Include your registered phone reference, not your password. Where local law permits, we may complete a verification step before replying.

You can raise a deletion or retention request through support. We assess the request against applicable duties, open payment questions, security needs and dispute records. Where local law permits, we remove or amend eligible material and explain why a required record must remain.

On a phone or desktop, cookies may keep your session active, remember a page setting and help us diagnose an access error. Your browser controls can restrict them. If you clear required cookies, you may need to complete login or phone verification again.

Use the support route connected with your rajabom account and describe the policy concern in plain English. Mention whether it involves a device, cookie, phone verification or payment reference. Do not send a PIN or password; support can request a safer account check.

Related Pages

rajabom Indonesia rajabom Casino Access guide About Us Account information