Reference

Terms & Conditions For Your Account

At pahlawan jitu, our Terms & Conditions explain how you open, use and maintain an account before entering the lobby.

Account stepsWallet checksPolicy accessLocal law
pahlawan jitu Terms & Conditions For Your Account
HELP WITH TERMS

Get Policy Help Before Account Access

A clear support route matters when a Terms & Conditions question affects your account or wallet status.

Account policy path Use the support route inside your account when you need a clause explained, a verification step checked or an access decision clarified. Include the policy heading and your account contact detail so we can respond to the right request without asking you to repeat the full history.
Wallet status question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the payment reference and time shown on your receipt. We use those details to check whether the Terms & Conditions point concerns identity matching, an instruction step or a pending status.
Policy change request If you believe a clause or account detail needs correction, tell us which wording is affected and what should be changed. We will assess the request against the account record and the current Terms & Conditions, while access remains subject to local law.
RECORDS AND ACCESS

How We Apply These Account Rules

The policy works alongside practical account controls rather than replacing them. We check the details you submit at registration, record changes made through the account path and use payment references to investigate…

Account data

We use the name, phone detail and other account information you submit to create access, complete phone verification and connect a payment request to the correct account. Your Terms & Conditions require those details to stay accurate, and you should tell us when a material detail changes.

Cookies on your device

Cookies may keep the policy page, sign-in state or account path working as you move between screens. If you clear cookies, the device may ask you to sign in again or repeat a verification step. Your browser settings control cookie removal on desktop and mobile.

Account security

You are responsible for protecting the phone, password and verification messages connected to your account. Do not send a one-time code through support. If access looks unfamiliar, use the account support path and mention the time and device involved so we can check the record.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we retain the reference needed to match a status check with your account. A receipt can help us investigate, but payment confirmation does not remove the identity and policy checks in these Terms & Conditions.

Retention questions

Ask us how long a particular account or payment record is kept by naming the record and the policy section connected to it. We assess retention requests against account security, transaction checks and legal duties, then explain the available action through the same support route.

Correction or access

To request a correction, copy of relevant account data or an explanation of an access restriction, send the request through account support. State your account contact detail and the exact change sought. We may verify ownership before discussing records or changing account information.

Terms & Conditions Questions Answered

These Terms & Conditions questions focus on the account decisions you are most likely to face before opening access or checking a wallet status. We explain the account step, local eligibility wording, data requests and payment references in plain English. If your situation is different, use the account support path with the exact clause or transaction detail so our team can examine the relevant record.

They cover account creation, phone verification, account security, lobby access, payment instructions, policy changes, data requests and account closure. They also explain how we handle DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks when a transaction needs to match your account.

Yes. Account access and eligibility depends on local law. We may ask for account or payment verification before enabling access, and you should read the current policy wording for your location. Where local law permits, the account path shows the steps available to you.

You first submit accurate account details, then complete phone verification before account access. Keep the phone connected to your account available during that step. If the code does not arrive or your details need correction, use account support rather than sending a code to anyone.

Those local wallet rails may be available where local law permits and where the account checks pass. Follow the instruction shown for the selected rail, keep the receipt reference and make sure the wallet identity matches the account details requested by the Terms & Conditions.

Use the account support path and name the exact detail that is wrong, such as a phone contact or account name. We may verify ownership before making a change. Include the relevant policy heading, but do not send your password or a one-time verification code.

Cookies can help keep the policy page and sign-in path working on your device. Clearing them may sign you out or require another verification step. Your browser controls cookie settings. If a cookie affects account access, tell support which device and browser you used.

Contact us through the account support path with your account contact detail, the date of the restriction and the clause you want reviewed. We may verify ownership and examine security or payment records. We will explain the available response, subject to local law and the current Terms & Conditions.