Reference

Privacy Policy For Your rajakera Account

rajakera Privacy Policy sets out how we handle the account details, device signals and wallet records linked to your use of the lobby.

Account data clarityWallet record contextMobile policy access24/7 Support route
Explore Our Lobby Read FAQ
rajakera Privacy Policy For Your rajakera Account
CONTACT ROUTES

Get Policy Help Beside Account Access

A clear contact route helps when you want to ask what a record means, correct an account detail or understand a wallet reference. Open the account area on your phone, use the displayed support contact path, and include the phone number connected to your account without sending a password. Our 24/7 Support route can help with privacy requests, login identity checks and payment-status questions while access remains subject to local law.

Team online

Privacy request

Ask us to explain a data item, correct a detail or clarify why an account record appears. Use the support contact path shown after sign-in and identify your account with its registered phone number.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the payment date, amount and displayed status through support. We use those details to locate the related account record without asking for your wallet password.

Account access help

When phone verification or a privacy-page sign-in stalls, contact 24/7 Support from the account area. We may ask for account details needed to confirm your identity before discussing stored data.

DATA PRACTICE

How rajakera Handles Your Privacy Choices

Our Privacy Policy is tied to practical account actions rather than broad promises. We record only the details needed to operate sign-in, phone verification, wallet status, support replies and account protection.

Account details

When you open an account, we handle details such as your registered phone number and verification result so we can connect sign-in activity with the correct account. We use these details for access checks and related support replies.

Device signals

Your mobile browser may send session, device and security signals when you move from login to the lobby. These signals help identify unusual access and keep the privacy page, account area and verification step connected.

Cookie controls

Cookies can keep a session active, remember basic page choices and support security checks. You can adjust cookie settings in your browser, although turning them off may interrupt sign-in or require another account verification step.

Payment references

A DANA, OVO, GoPay or QRIS transaction may leave a reference, status and time in our records. Bank transfer and virtual account entries are handled for matching and support, not as a request for your wallet password.

Retention checks

We keep account, security and payment references only while they serve the stated account, support or legal purpose. When a record is no longer needed, our retention process assesses it for removal or continued storage under a valid requirement.

Change requests

To ask for a copy, correction or privacy clarification, use the contact path shown in your signed-in account area. Include the request type and registered phone number; we may verify ownership before changing or disclosing account data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions you are most likely to search before opening access. We explain the data path from phone verification through wallet status, how cookies affect a mobile browser session and where to send a correction request. If your question concerns eligibility, remember that access depends on local law and is provided where local law permits.

The rajakera Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, account protection and the route for privacy requests.

We may handle the phone number you submit, the verification result, sign-in events, device or session signals, support messages and transaction references. These records help connect you with the right account, check wallet status and respond to Privacy Policy requests without requesting your wallet password.

Open the signed-in account area on your mobile browser and use the displayed support contact path. State that you want a correction, identify the relevant detail and provide your registered phone number. We may confirm account ownership before changing the record or discussing related data.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS activity can create a reference, status and time record, while bank transfer and virtual account entries may be matched to your account. We use those details for payment checks, account protection and support.

Cookies and similar browser signals can keep your session connected while you move from login to the lobby and open the Privacy Policy page. You can adjust them in your browser, but disabling required cookies may interrupt sign-in or trigger another phone verification step.

We retain account, security, support and payment references while they serve the stated account purpose, help resolve a request or meet a valid legal requirement. Our retention process checks whether each record remains necessary before removal or continued storage.

Yes. Use the support contact route shown in your account area and select the privacy or account-data reason where available. Our 24/7 Support route can help explain a record, receive a correction request or check an unfamiliar wallet reference after identity confirmation.

Related Pages

rajakera Indonesia Mobile Legends Baccarat About Us 24/7 Support