Reference

rajamas Privacy Policy For Your Account

rajamas Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet recordsCookie choicesContact route

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

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

Our Privacy Policy covers details you provide during account creation, including your contact details and the phone verification needed before account access. We also record device signals, login events, lobby actions and payment references so we can keep your session connected to the right account. A

1
DANA, OVO, GoPay or QRIS reference helps us match a deposit or status check without storing your wallet password. We use this material to provide access, resolve account questions, detect unusual activity and meet requests that apply where local law permits. The policy does not change
2
the rules of your bank or wallet provider.

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

CONTACT THE TEAM

Privacy Questions Through The Account Path

A clear contact path helps you ask what we hold, why we use it or how to correct an account detail.

DATA HANDLING

How We Apply Privacy Policy Controls

We apply the Privacy Policy at the points where your account actually moves: phone verification, login, lobby access and wallet status checks.

Account data

We collect contact details and verification results when you open or enter an account.

Device signals

Browser and device signals can be linked to login events, including a mobile path into the lobby.

Cookies

Cookies can keep a session active, remember a page setting and help us understand which policy page brought you to…

Account security

Phone verification comes before account access, and support checks account details before discussing private records.

Retention

We keep account, access and payment-reference records only for the period needed for the stated service, security checks and applicable…

Change requests

You can ask us to correct an inaccurate contact detail, explain a data use or remove eligible records through account…

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions we expect before access. They cover the data connected with login, device use, cookies and payment references, along with the practical route for asking us to make a correction or provide a copy. If your question concerns a local eligibility rule, access depends on local law. For a case tied to your own account, use the support path rather than posting private details in a public message.

The rajamas Privacy Policy covers account contact details, phone verification results, login and device signals, cookie activity, lobby actions and payment references. We use these details to provide account access, check wallet status, protect sessions and respond to support requests.

Phone verification helps us confirm account ownership before access and before discussing private records. It can also help support compare a login issue with the correct profile. Never send your one-time code; we only need the account contact detail for the normal check.

No. Our Privacy Policy separates payment references from secret wallet credentials. When you use DANA, OVO, GoPay or QRIS, we may receive a reference or status needed to match the account activity, but your wallet password remains with the wallet provider.

Use the account support path and state that you want access to your account data. Include the registered contact detail and the type of record requested. We may verify ownership first, then handle the request according to the Privacy Policy and local law.

Yes, you can ask us to correct an inaccurate contact detail or account record through support. Describe the field that needs changing and identify the account. We may compare the request with phone verification before applying an update.

Cookies can keep your mobile session connected between login, the lobby and a policy page. Browser settings let you manage them, but blocking some cookies may sign you out or require repeated account steps. Device signals may still support security checks.

We retain account, access and payment-reference records for the period needed for service delivery, security checks and applicable legal duties. The period can differ by record type. You can ask support about a specific record and whether a deletion request is available.

rajamas Privacy Policy For Your Account

Privacy Questions Through The Account Path

How We Apply Privacy Policy Controls

Account data

Device signals

Cookies

Account security

Retention

Change requests

Privacy Policy Answers For Indonesia

01 What does the rajamas Privacy Policy collect?

02 Why does rajamas need phone verification?

03 Does the Privacy Policy store my DANA or QRIS password?

04 How can I request my rajamas account data?

05 Can I correct details held under the Privacy Policy?

06 How do cookies affect rajamas on mobile?

07 How long does the Privacy Policy keep account records?

Related Pages