Reference

Legal details for your rajalangit account

rajalangit Legal explains how account access, wallet checks, personal data and policy requests work before you enter the lobby.

Account accessWallet checksData choicesPolicy requests

Explore Our Lobby Read FAQ

Legal access follows local law

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

Our Legal terms apply to the rajalangit account, lobby access and related wallet actions in Indonesia. Eligibility depends on local law, so you must use the service only where local law permits and provide accurate account details when asked. We may request phone verification before account

1
access, then compare the account name and payment reference when a wallet or bank transfer is used. DANA, OVO, GoPay and QRIS are shown as payment context, not as a change to your legal duties. A cashier request can also involve virtual account, BCA, BRI, Mandiri
2
or BNI details. If a rule changes, we will place the updated wording on this Legal page. Your continued account use after an update means you have had the chance to read the revised terms.

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

POLICY CONTACT PATHS

Three ways to raise a Legal question

A clear contact route matters when a Legal question affects your account or wallet status.

DATA HANDLING PRACTICE

How we apply Legal inside rajalangit

Our Legal process is practical: we connect each request to an account step, payment reference or data choice, then limit the response to what is needed.

Account data

We use the details attached to your account to manage access, phone verification and policy requests. Keep your registered contact detail current so a Legal response can be matched to you without exposing account data to another person.

Payment references

A wallet or bank transfer check uses the transaction reference, amount context and account match needed for the request. We do not need your DANA, OVO, GoPay or QRIS PIN to investigate a cashier status.

Cookies

Cookies may keep your session, language choice and security state working between pages. You can adjust browser cookie settings, although blocking required cookies may interrupt phone verification or return you to the account access screen.

Account security

Do not share your password, verification code or wallet PIN. If you suspect another person accessed the account, contact us through the account help path and include the last safe action you remember.

Retention

We keep account and transaction records only for the operational, dispute and legal purposes connected with the service. A retention question can be sent through the data request route, where we explain what can be changed or removed.

Policy changes

When Legal wording changes, we publish the revised text on this page rather than hiding it inside a cashier screen. Check the page before opening the lobby, especially after an account, access or payment process has changed.

Answers before you open an account

These Legal answers cover the questions we expect before account creation or a wallet action. They explain local eligibility, account records, payment references, cookies and contact steps in plain language. If your situation is not covered, use the relevant path above and include enough detail for us to locate the account without sending secret credentials.

Legal covers account access, phone verification, payment references, cookies, personal data, policy changes and contact requests connected with rajalangit. It does not replace the laws that apply in your location. Eligibility depends on local law, and you should use the service only where local law permits.

Access depends on local law and your eligibility under the rules that apply to you. We may ask for phone verification before account access. If the service is not permitted where you are, do not open or use an account, even if a payment option such as QRIS is visible.

Those payment names show the wallet and QRIS context covered by our Legal terms. A payment status check can require a reference and account match, but never your wallet PIN. The same principle applies to bank transfer and virtual account requests involving BCA, BRI, Mandiri or BNI.

We need the account details required to create and protect your access, including a registered contact detail for phone verification. We may compare that account record with a payment reference when needed. Do not send passwords, one-time codes or wallet PINs through a Legal contact request.

Use the data request path and state which detail is wrong, what it should say and which registered contact identifies your account. We will assess the request under the applicable Legal terms. A correction request does not require you to disclose a password or payment PIN.

Yes. Cookies can support your session, language choice and security state across account and lobby pages. Browser settings let you block or remove them, but required cookies may be needed for phone verification. Ask through the policy contact route if you need a specific cookie explanation.

Use the account help path for login or phone verification issues, the cashier-linked route for a payment reference, and the data request route for personal-data changes. Include your registered contact detail and the visible error, while keeping passwords, codes and wallet PINs private.

Legal details for your rajalangit account

Three ways to raise a Legal question

How we apply Legal inside rajalangit

Account data

Payment references

Cookies

Account security

Retention

Policy changes

Answers before you open an account

01 What does rajalangit Legal cover?

02 Can I access rajalangit from Indonesia?

03 Why does Legal mention DANA, OVO, GoPay and QRIS?

04 What data does rajalangit need for account access?

05 How do I request a correction to my account data?

06 Can I ask what cookies rajalangit uses?

07 Where do I report a Legal or account access concern?

Related Pages