Reference

warjackpot Privacy Policy for Your Account

warjackpot Privacy Policy shows what we collect when you create an account, verify your phone, sign in on mobile, or use DANA and QRIS.

Account dataWallet recordsCookie choicesAccess requests
warjackpot warjackpot Privacy Policy for Your Account
CONTACT ROUTES

Where to Ask About Privacy Policy

You can raise a Privacy Policy question without explaining your full account history in a public message. Use the account support path for access, correction or deletion requests, and use the cashier support path when a DANA, OVO, GoPay, QRIS or bank transfer record needs matching. Include your registered phone number only through the secure contact route so we can locate the right record.

Team online

Account support path

Ask us to correct your name, phone record or account details through the signed-in support route. We may ask for a verification step before changing data tied to account access.

Cashier support path

For a wallet status or payment receipt question, provide the transaction reference from DANA, OVO, GoPay, QRIS, bank transfer or virtual account through the protected support route.

Privacy request route

Send a request to access, amend or remove eligible personal data through account support. We check account ownership first, then explain what can be changed under local law.

HANDLING DETAILS

Cookies, Devices and Account Records

Our Privacy Policy separates the data needed to operate your account from settings that help a browser remember a session.

Account creation

When you open an account, we collect the details needed to create your profile and send a clear phone verification step before account access. We use those details to maintain the correct account record.

Device sessions

A mobile browser and a desktop browser may produce separate session signals, such as device type, browser version and sign-in time. These signals help us investigate unfamiliar access without reading private device content.

Cookie controls

Cookies can keep a session working and help us remember selected settings. Your browser controls whether some cookies remain, although changing them may require another sign-in to reach account pages.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS or a bank rail help us match a receipt to your account. We do not ask you to send a wallet password through support.

Retention checks

We retain account, support and transaction records only for the period needed for the stated service, account security, dispute handling or a legal requirement. We remove or restrict records when that period ends.

Change requests

To request a copy, correction or eligible deletion, contact us through the signed-in privacy route. We verify ownership, record the request, and explain any data that must remain for a lawful reason.

Privacy Policy Answers for Your Account

These Privacy Policy answers cover the account steps you are most likely to meet on warjackpot: phone verification, mobile sessions, cookies, wallet records and contact requests. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, keep that reference ready and use the protected account support route.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us connect the right person to the right account before access is provided. It also gives our support team a safer way to check ownership before changing account data.

Yes. The policy covers transaction references and status records used to match a DANA or QRIS payment to your account. We do not ask you to share your wallet password through support.

You can request access through the signed-in privacy route. We first verify account ownership, then provide the eligible account, support and transaction data held for the stated service purpose.

Use account support to request a correction to eligible profile or phone details. We may require another verification step, especially when the change could affect account access or payment matching.

Retention depends on the record and its purpose. We keep data for account operation, security, dispute handling or a legal requirement, then remove or restrict it when that need ends.

You can submit a removal request through the privacy contact route. We check ownership and explain whether any record must remain because of account security, payment reconciliation or local law.