Reference

Privacy Policy For Your penaklukjitu Account

penaklukjitu Privacy Policy explains how we collect, use and protect details connected with your account, wallet status and lobby access.

Account dataWallet recordsCookie choicesContact requests
penaklukjitu Privacy Policy For Your penaklukjitu Account
CONTACT PATHS

Privacy Questions Meet Account Support

A clear contact path matters when a Privacy Policy question concerns your own account rather than a general page. We ask you to use the support route connected to your account so we can match the request with the correct phone verification record and wallet reference. Include the subject of your request, the account detail you want checked and, when relevant, a DANA, OVO, GoPay or QRIS receipt reference. We will use only the details needed to identify the issue and respond.

Team online

Account support route

Use the signed-in account path for a Privacy Policy request. It lets us connect your question with the correct phone verification record without asking you to send a wallet password or full payment credentials.

Cashier status check

If your question concerns DANA, OVO, GoPay or QRIS data, include the transaction reference shown in your cashier record. We can check the status while limiting the request to the payment detail needed for reconciliation.

Access correction request

For an incorrect name, phone detail or account record, tell us which field needs attention and why. We may ask for an account step that confirms control before changing personal data.

HANDLING YOUR DATA

Six Privacy Controls Inside Our Process

We handle this policy area through practical controls rather than broad promises. Account records are separated from payment references where the workflow allows, device activity is checked for unusual sign-in patterns and…

Account details

We use the account details you provide to create access, confirm a phone number and respond to a Privacy Policy request. We do not ask for more personal detail than the account step or support question requires.

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference helps us match a cashier event with your account. We use that reference for status checks and reconciliation, not as a substitute for your wallet credentials.

Cookies and sessions

Cookies can keep your sign-in session and selected settings available while you move from the account page to the lobby. You can adjust browser storage controls, although limiting cookies may require another sign-in.

Device security

We may examine device and sign-in signals to spot unusual access, protect your account and trigger phone verification when needed. These checks support account security without giving us access to private files on your phone or computer.

Retention choices

We retain account, support and transaction records only for the operational or legal purpose connected with them. A request to remove data is assessed against those purposes, and we explain where a record must be kept.

Policy requests

You can ask what personal data is linked to your account, request a correction or ask about deletion through the support path. Include the relevant account step so we can verify control before discussing private records.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers focus on the account and wallet questions you are most likely to search before opening access. We explain what we collect, why payment references appear, how cookies affect your device and how to request a change. If your case involves a specific account record, use the signed-in support path so we can assess it against the applicable local rules.

The penaklukjitu Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains how we use those records for access, security, cashier reconciliation and policy requests where local law permits.

No. Our Privacy Policy distinguishes a payment reference from a wallet password. DANA and QRIS references may help us match a cashier event with your account, but you should not send us a wallet password, PIN or private authentication code.

Phone verification helps connect an account request to the person controlling that account and can support an access check after unusual sign-in activity. Under the Privacy Policy, we use the verification result for account security and do not treat it as permission to inspect private device files.

Cookies can keep your session active and preserve selected settings as you move between account pages and the lobby. You can restrict browser storage, but the Privacy Policy notes that doing so may sign you out or require another verification step before access continues.

Yes. Use the account support path to ask what data is linked to your account or to identify an incorrect field. The Privacy Policy allows us to request an account confirmation before discussing private records or changing details such as a phone number.

Retention depends on why the record exists and on applicable legal requirements. The Privacy Policy covers transaction references from DANA, OVO, GoPay, QRIS, virtual accounts and bank transfers, and we explain the outcome if you request deletion of an eligible record.

Start with the support route connected to your signed-in account and state whether your request concerns access, correction, deletion, cookies or a payment reference. Where local law permits, we will assess the request after confirming the account detail needed to protect your privacy.