Reference

superjago Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a superjago account, verify your phone, use the mobile lobby or move funds through DANA, OVO, GoPay and…

Account dataWallet activityDevice accessRequest steps
superjago superjago Privacy Policy for Your Account
REQUEST HELP CLEARLY

Check Your Privacy Support Route

A clear support path helps you ask about personal data without explaining the same issue twice.

Account access If phone verification blocks your account, use the account support route and state the…
Wallet records For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate…
Privacy changes To ask for access, correction or removal where available, use the privacy request route…
DATA HANDLING DETAILS

Explore How We Handle Account Data

Our handling steps follow the account journey rather than treating every record the same way. Sign-up data supports account creation, phone verification protects the login route, and wallet references help us match…

Account creation

When you open an account, we use the details you submit to create your profile and connect your chosen login route. We do not need your Fortune Fishing Game or other lobby selections to answer a request about your identity record.

Phone verification

A clear phone verification step comes before account access. We record the result and related time or device signals so we can protect the login route, investigate failed attempts and distinguish your request from activity on another profile.

Payment matching

For DANA, OVO, GoPay and QRIS, we use transaction references and status details to match a wallet event to your account. Bank transfer and virtual account records are handled in the same account-specific way.

Cookies and devices

Cookies and device signals help keep your session connected when you move from mobile login to the lobby or return on desktop. You can manage browser cookie settings, although some account functions may not work correctly after blocking them.

Security records

Login time, access device and verification events may be checked when activity appears unusual. These records help us protect account data and payment references; they are not a public profile and are not used to identify your game preferences to other accounts.

Retention requests

If you ask how long a record is kept or request a change, tell us the account field, payment reference or device record involved. We assess the request against operational and legal needs, then explain the available result through the support route.

Browse Privacy Policy Answers

These Privacy Policy answers cover the account and wallet questions we expect you to ask before opening access. Each answer points to a practical step, from checking a phone verification record to requesting a change through the account support route. If your situation is not listed, send the relevant reference instead of sharing extra personal details.

The superjago Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references and support requests. It explains why we use each category, how records help account security, and how you can ask about access, correction or removal where available.

We collect the details you submit for account creation, plus the result of the required phone verification step. We may also record login time, device signals and account actions needed to protect access. Your game selection is not required to answer an identity-data request.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. For bank transfer or virtual account activity, we use the matching reference to locate your account record. The payment provider keeps separate records under its own policy.

Use the privacy request route in your account support area and name the specific field or record. Include your account identifier, and add a payment reference only when the request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

You can ask through the account support route, and we assess removal against operational and legal needs. Some records may need to remain for security, payment matching or legal reasons. We will explain the available result, with access depending on local law.

Cookies help keep your session connected as you move from mobile login to the lobby or return on desktop. Device signals can also help identify unusual access. You can change browser settings, but blocking required cookies may interrupt phone verification or account access.

Start with the support route attached to your account and describe the Privacy Policy issue in plain terms. For wallet records, include the relevant reference and date. For login concerns, identify the verified phone route so we can locate the correct account safely.