Reference

Privacy Policy for DANA and QRIS

Our rajalangit Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account recordsWallet detailsDevice signalsCookie choices
Explore Our Lobby Read FAQ
rajalangit Privacy Policy for DANA and QRIS
CONTACT ROUTES

Support For Privacy Requests

A clear contact path helps you question a record without repeating your account story.

Account help route Use the support path beside your account area for a Privacy Policy request.
Wallet status query For a privacy question connected to QRIS, bank transfer or a virtual account, send…
Correction request If your phone, name or account detail needs correction, tell us which field is…
SIX DATA CONTROLS

Account Security And Device Data

We keep privacy decisions close to the actions you take: creating an account, checking a wallet, opening a mobile lobby or contacting support.

Phone verification

Before account access is completed, we use the phone verification result connected with your registration. This helps us distinguish your request from an unknown sign-in. We do not ask you to send a wallet PIN when we check DANA, OVO, GoPay or QRIS status.

Device signals

When you sign in on a mobile browser, we may record device type, browser details and security events linked to that session. These signals help us investigate unusual access to your account; they are not a substitute for your password or phone verification.

Cookie choices

Cookies can remember a session, language setting or privacy choice on the device you use for the lobby. You can manage cookies through your browser controls. Turning some off may require you to sign in again or repeat a preference when returning.

Payment separation

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain transaction references and status details needed for account matching. We do not treat those references as permission to collect your wallet PIN or unrelated wallet activity.

Retention checks

We keep account, verification and payment records for as long as needed for the stated account, security, dispute or legal purpose. When a record is no longer needed for that purpose, our handling process moves it toward deletion or secure restriction.

Your request

You can ask what account data we hold, request a correction, ask about deletion or question a cookie choice through support. We may verify your identity using the registered phone before responding, so a third party cannot obtain or alter your records.

Privacy Policy Questions For rajalangit

These Privacy Policy answers focus on the searches we hear around account access, local wallets and mobile use. We explain what to send, what we may verify and how a request connects to your account record. If your question is not covered, use the account support route and mention the exact screen or payment reference involved.

It covers data linked to your account, phone verification, sign-in device, cookies, support requests and payment references. It explains how we handle DANA, OVO, GoPay, QRIS, bank transfer and virtual account records when those details are needed to match account activity.

No. Our Privacy Policy separates wallet status and transaction references from your wallet credential. When you ask about DANA, OVO, GoPay or QRIS activity, send the receipt reference or displayed status instead of a PIN, password or one-time security code.

Use the support path connected to your account and ask for an account data access request. Include your registered phone number and the relevant account area. We may complete phone verification before sharing records, which helps protect your data from an unrelated requester.

Yes. Tell support which field is incorrect and provide the replacement detail. Phone, identity or access-related changes may require fresh verification. Payment references such as a QRIS receipt are checked against the account record rather than edited to match an unsupported version.

When you sign in from a phone or tablet, we may use device type, browser details and security events to protect the session. The Privacy Policy also explains cookies that remember a session or choice; browser controls let you remove or restrict them.

We retain account, verification and payment references only for the period needed for account operation, security, disputes or legal duties. Once a record no longer serves that purpose, our process moves it toward deletion or secure restriction, subject to applicable requirements.

Our Privacy Policy is written for account activity connected with Indonesia. Access or eligibility depends on local law, and our services are available where local law permits. If you are unsure about your location or request, contact support before opening or using an account.

Related Pages

rajalangit Indonesia Account information No Commission Baccarat About Us World Cup Over Under