Reference

keranjang88 Privacy Policy for Your Account

Our Privacy Policy explains how we handle your account details, phone verification, wallet records and mobile-browser activity when you use keranjang88.

Account dataWallet recordsMobile cookiesPrivacy requests
keranjang88 keranjang88 Privacy Policy for Your Account
CONTACT ROUTES

Where Privacy Questions Reach Us

A clear contact path matters when a wallet receipt or account record needs explanation.

Account privacy request Use the support route inside your account area to ask for a copy, correction…
Payment record check If DANA, OVO, GoPay, QRIS or a bank transfer shows the wrong status, send…
Access assistance When login or phone verification stalls, contact support through the account path and describe…
DATA PRACTICE

Dragon Tiger Data Handling In Practice

Privacy controls should remain understandable whether you browse Dragon Tiger on a phone or check account records on desktop.

Account details

We use your account identifier, contact details and phone-verification result to connect requests with the correct account and reduce mistaken…

Cookie controls

Our browser cookies can keep a session active and remember selected settings.

Security checks

We limit account changes to the signed-in path and may ask for phone verification before discussing private records or changing…

Payment records

DANA, OVO, GoPay, QRIS and bank-transfer records are used to match receipts, investigate status questions and identify the account connected…

Retention periods

We keep records only as long as needed for account operation, payment disputes, security checks or legal duties, then remove…

Changes and contact

Ask us to correct account data, explain a cookie or clarify a retention period through the support route displayed after…

Privacy Questions About QRIS and Accounts

These Privacy Policy answers cover the searches we hear most often before account access. We keep each response tied to a practical action, from checking a QRIS reference to asking for a correction, and access remains where local law permits.

It covers account details, phone verification, cookies, device activity, payment-status records, retention, security controls and the steps for asking about or changing your data.

No wallet password is needed to match a DANA or QRIS status. We use transaction references and related status details to connect the payment with your account.

We use the verification result to confirm account access and reduce mistaken changes. Where local law permits, it can also help us identify the correct account during a privacy request.

Yes. Send a request through the signed-in support route with your account identifier and request type. We may verify ownership before providing or changing private records.

Cookies can keep your session and selected settings available while you move between account and payment pages. Clearing them may sign you out and require phone verification again.

Retention depends on the purpose of the record, including account security, receipt matching, dispute handling and legal duties. Ask support for the period that applies to your request.

Contact support through your account path and provide the receipt reference, date and wallet name. We compare those details with the stored payment-status record before making a correction.