Reference

Privacy Policy for Your mujarab jitu Account

mujarab jitu Privacy Policy shows what we collect when you create an account, verify your phone, use DANA or QRIS, and open the lobby from a mobile browser.

Account dataWallet referencesCookie choicesAccess requests
mujarab jitu Privacy Policy for Your mujarab jitu Account
PRIVACY HELP ROUTE

Where To Ask About Your Privacy Policy

A clear support route helps when you need a copy, correction or explanation of personal data. Start from the account help area linked beside the cashier path, then include the phone number attached to your account and the subject of your request. We use those details to locate the correct record without asking you to send a wallet password. If a DANA, OVO, GoPay or QRIS status is part of the question, add its reference so our support team can separate payment evidence from account data.

Team online

Account data request

Use the account help route beside the cashier path when you want to ask what personal details are connected with your login. Include your verified phone number and the requested action, such as access or correction, so we can check ownership before replying.

Wallet reference check

For a privacy question involving DANA, OVO, GoPay or QRIS, provide the payment reference and status shown in your account. We can examine the record without requesting your wallet password, full wallet credentials or unrelated messages from your payment application.

Mobile access concern

If a mobile browser keeps your session or shows an unexpected privacy setting, use the same support route and name the device type and browser path. We can explain the cookie or login record involved and tell you which account step needs confirmation.

CONTROL AND RETENTION

How We Handle Cookies And Account Safety

We keep this Privacy Policy practical by linking each data use to an account action you can recognise: phone verification, wallet matching, mobile login or support.

Phone verification

Your verified phone number helps us connect a privacy request to the right account. Before releasing account details or changing a record, we may ask you to repeat an account step so another person cannot obtain your data through a simple support message.

Cookie controls

Our mobile browser path may use cookies for session continuity and selected account settings. You can clear cookies through your browser controls, but doing so may remove the active login and require phone verification again before account access returns.

Payment separation

DANA, OVO, GoPay and QRIS references are used to match payment status with your account record. We do not need your wallet password for that match. Bank transfer and virtual account details are handled as transaction evidence linked to the relevant request.

Access protection

We check account ownership before discussing personal data, changing a phone number or explaining a withdrawal record. If a request arrives from an unfamiliar device, we may ask for an additional account confirmation rather than disclose details immediately.

Retention timing

We keep account, payment-reference and support records only for the period needed for account security, status checks and applicable legal duties. When a record no longer serves those purposes, our handling follows the deletion or restriction rules available under local law.

Change requests

You can ask us to correct inaccurate account details or explain how a record was used through the account help route. State the requested change clearly, include your verified phone number and avoid sending wallet passwords or unrelated identity documents.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the account steps most likely to raise a data question: phone verification, wallet references, cookies, device access and record requests. We keep the wording tied to mujarab jitu so you can decide what to share before opening an account. Where a legal rule affects access, our response follows the wording and limits required for your location.

It covers account details, phone verification, payment references, cookies, device access, support records and retention. It also explains how to request access or correction. When you use DANA, OVO, GoPay or QRIS, the policy describes the status data needed to match the transaction with your account.

We use your phone number to create and verify the account, protect login access and confirm that a privacy request comes from you. If you ask for account data or a correction, we may repeat the verification step before discussing records linked to that number.

The payment process uses a reference, amount status and confirmation result from DANA, OVO, GoPay or QRIS. We do not need your wallet password to match that status. Never place a wallet password in a support message, privacy request or payment receipt.

Cookies can retain a mobile browser session and remember a selected account setting. Clearing them may sign you out and require phone verification again. If a cookie behaves unexpectedly, tell us the device type and browser path through the account help route.

Yes, send an access request through the account help route beside the cashier path. Include your verified phone number and describe the records you want, such as account details, QRIS references or support messages. We will check ownership before discussing the requested data.

You can ask us to correct inaccurate account details by stating the field and the intended value through support. We may request phone verification before making a change. Payment records may need to remain unchanged where they are required for status checks or legal duties.

Account access and data handling depend on local law. Where local law permits, we can process an access, correction or deletion request according to this policy. If a legal duty requires us to retain a record, we will explain that limit when responding.