Reference

jaminjp Privacy Policy for Your Account Data

Our Privacy Policy explains how jaminjp handles your account details, phone verification, device access and wallet records when you use the lobby.

Clear data purposesWallet record handlingPhone verification contextCookie choices
jaminjp jaminjp Privacy Policy for Your Account Data
PRIVACY HELP PATH

Get Help With a Privacy Request

A clear contact path helps when you need to ask about account data rather than a wallet balance.

Account data Ask which personal details are connected to your account, why they are used and which records are needed for phone verification or account security. We may confirm your identity before sharing account-specific details.
Wallet records If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the relevant date, status and account reference through our support route. We use those details to locate the matching record without asking for your wallet password.
Privacy changes You can ask us to correct inaccurate details, explain a cookie choice or discuss deletion of eligible records. Requests remain subject to account security checks, payment reconciliation needs and duties that apply where local law permits.
DATA CONTROL POINTS

Six Ways We Handle Your Privacy

Privacy work is part of the account flow, not a separate promise hidden from your daily use.

Account purpose

We use your account details to provide access, maintain sign-in state, confirm phone ownership and connect activity to the right account. We do not present game or wallet activity as a reason to collect unrelated personal details.

Phone verification

Before account access, phone verification helps us confirm that the requested sign-in belongs to you. Keep your verification details private, and contact support if a code arrives without an action from you.

Device signals

Browser and device signals may be used to identify unusual login patterns, protect sessions and investigate access concerns. They help with security decisions and are not a substitute for your password or verification code.

Cookie choices

Necessary cookies help keep your session active and remember essential access settings. Browser controls can limit optional cookies, although changing them may affect saved preferences or the way account pages load.

Record retention

We retain account, security and wallet-reference records for as long as needed for the stated purpose, reconciliation, dispute handling or applicable legal duties. Eligible deletion requests do not remove records we must keep.

Request contact

Use the account support route to ask about access, correction, deletion or the reason a record is held. Include a clear request, and we may verify your account before discussing personal details.

Privacy Policy Questions for jaminjp

These Privacy Policy answers cover the account questions you are most likely to have before opening access or changing an existing account. We keep the wording practical: what is collected, how wallet references are used, what happens on a mobile device and how you can contact us. Eligibility depends on local law and applies where local law permits.

The jaminjp Privacy Policy covers account details, phone verification, device and browser signals, cookies, security records and wallet references. It explains why we use each category, how long records may remain and how you can request access, correction or deletion where applicable.

Phone verification helps us connect account access to the person requesting it and reduce unauthorised sign-ins. We may use the verification event as a security record, but you should never share a code with another person or send it through an unrequested message.

Yes. The Privacy Policy covers references and status details linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those details to match an account event, check a status and handle a dispute, not to request your wallet password.

Use the support route connected to your jaminjp account and ask for an account-data request. Include the account phone number or another locating detail, then complete any identity check we require before we discuss private records or provide a copy.

You can ask us to correct inaccurate account details or delete eligible records through the account support route. We may retain security, payment-reconciliation, dispute or legally required records, so a deletion request does not automatically remove every stored reference.

On a mobile browser, necessary cookies help maintain your login session and essential account settings. You can adjust optional cookie controls in the browser, but blocking necessary cookies may interrupt account access or require you to verify the phone again.

Contact us through the support path available from your account and state that your request concerns the Privacy Policy. Describe the record or access issue without sending passwords or wallet codes; we will use account verification before discussing personal data.