Reference

juragan28 Privacy Policy for Your Account

Our juragan28 Privacy Policy shows what account, device and wallet details we collect, why we use them, and how you can ask for changes.

Account dataWallet recordsDevice choicesAccess requests

Explore Our Lobby Read FAQ

How Wallet Data Is Used With QRIS

juragan28 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the details needed to connect your account with a selected payment route and show an accurate status. For DANA, OVO and GoPay, this can include the wallet name, transaction reference, amount, time and clearing result; we do not need your wallet password to display

1
that record. QRIS activity may include the QR reference and confirmation returned by the payment service. Bank transfer and virtual account records can contain the receiving bank, such as BCA, BRI, Mandiri or BNI, plus the reference used to match your account. We use these records
2
to confirm an account step, answer a receipt question and detect repeated or mismatched entries. Access or eligibility depends on local law, and we may restrict processing when a legal request requires it. You can ask us to explain a recorded transaction through the support path
3
below.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

DATA SUPPORT

Where To Ask About Your Data

A clear support route helps when a wallet status, login record or account detail looks unfamiliar.

Account support path Open your account support area after login and identify the data record in question. Including the date, payment reference or device type helps us locate the correct Privacy Policy request.

Wallet status check For DANA, OVO, GoPay or QRIS questions, share the payment reference rather than your wallet password. We can compare the recorded status with your account without asking for private wallet credentials.

Access request Ask us to access, correct or clarify account data through the same support route. We may request an account step to confirm that the request comes from you.

SECURITY LAYERS

Account Security Beyond The Login Screen

We handle Privacy Policy requests as account matters, not as general lobby questions. Our records connect your submitted details with login activity, wallet references and device signals so we can protect the…

Collected account details

We may store your account identifier, phone verification result and messages sent through support. These details help us confirm ownership, answer a data request and keep the account record consistent.

Device and session signals

A phone or desktop browser can provide session, browser and security signals. We use them to recognise unusual access and may ask you to repeat verification before account details are shown.

Cookies and storage

Cookies and browser storage can remember a session choice or sign-in state. You can clear them in your browser settings, although doing so may remove saved preferences and require another login.

Lobby activity records

Opening areas such as Live Baccarat, Captain Bounty or Mobile Legends may create activity records linked to your account. We use those records to maintain session security and answer account queries.

Retention approach

We retain account, payment-reference and support records only for the period needed for account operations, security checks or legal duties. When a record is no longer needed, our handling process addresses its removal.

Changes and corrections

If your phone detail, account name or stored preference is inaccurate, contact us with the requested correction. We may verify the account step before changing data connected to your access.

Privacy Policy Questions From Indonesian Account Holders

These Privacy Policy answers cover the records most often connected with account access, wallet status and mobile browsing. If your question is not listed, use the account support route and describe the exact data or request you want us to check.

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

Phone verification helps us connect an account request to the correct account and reduce mistaken access. We may ask for this step before showing, correcting or changing stored account details.

No. We use payment references, selected method, amount and status to match account activity. Your DANA, OVO or GoPay password is not needed for our recorded transaction checks.

Cookies and browser storage can keep a session or preference recognised on your phone. Clearing them may sign you out, remove saved choices and trigger another account verification step.

Yes. Send an access request through the account support route and identify the account record involved. We may confirm ownership before providing data connected with your account.

Contact support with the incorrect field and the replacement detail. We will check the account step, review the connected record and apply a correction when the request can be verified.

We keep payment references and related account records for operational, security or legal needs. The retention period can differ by record type, and you may ask support what applies to your request.

juragan28 Privacy Policy for Your Account

Where To Ask About Your Data

Account Security Beyond The Login Screen

Collected account details

Device and session signals

Cookies and storage

Lobby activity records

Retention approach

Changes and corrections

Privacy Policy Questions From Indonesian Account Holders

01 What does the juragan28 Privacy Policy cover?

02 Why does juragan28 need my phone verification?

03 Does the Privacy Policy store my wallet password?

04 How does juragan28 use cookies on mobile?

05 Can I request a copy of my account data?

06 How can I correct data under this Privacy Policy?

07 How long does juragan28 keep payment records?

Related Pages