Reference

wisma138 Privacy Policy For Your Account

Our wisma138 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
wisma138 wisma138 Privacy Policy For Your Account
CONTACT THE TEAM

Privacy Help Beside Your Account

A clear contact path matters when your privacy question arrives alongside a login or wallet issue. We keep the support route close to the cashier path so you can identify the account involved, describe the request and attach only the receipt or device detail needed for us to check it. If you are in Makassar, the same online route applies without a separate local process.

Team online

Policy request

Use the account support route to ask what data we hold, why it is used, or which records relate to your DANA, OVO, GoPay or QRIS activity.

Access concern

Tell us when a sign-in, phone check or device change appears unfamiliar. We can connect the privacy query with the account step that needs confirmation.

Wallet record

For an unmatched bank transfer or virtual account receipt, include the transaction reference rather than sending unrelated documents through the support path.

HOW DATA WORKS

Six Privacy Practices Inside wisma138

We handle privacy through practical account controls rather than broad promises. Sign-in events, phone verification and wallet records help us identify the right account when you ask for a correction or access…

Collection

We collect details needed for account creation, phone verification, sign-in protection and payment matching. A DANA or QRIS reference may be retained to resolve a cashier query.

Use

We use account data to provide access, check unusual device activity, answer privacy requests and connect a wallet status with the correct account holder.

Cookies

Cookies can remember session choices and help us understand whether a sign-in page loads correctly. You can manage browser cookie settings, though some account steps may then need repeating.

Account security

Phone verification and device checks help protect your account before access is restored after a sign-in change. Never send a password or one-time code through support.

Retention

We keep records for the period needed to complete the stated account, security or payment purpose, then assess removal or further storage under applicable legal requirements.

Your request

Ask us to access, correct or clarify personal data through the account support route. Include your registered contact detail so we can verify the request safely.

Privacy Policy Questions Answered

These answers address the privacy searches we hear most often before an account is opened or a wallet record is checked. Our support team can look at the specific account history, device path or receipt involved, while access and eligibility remain dependent on local law.

It covers data connected with your account, sign-in activity, device checks, cookies, wallet records and support requests. It also explains how we use, retain and respond to requests about those records.

We use your phone detail for account identification and verification before access. It helps us connect a privacy request with the correct account when a device or sign-in pattern changes.

Yes. The policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity when those records help match a cashier request or receipt.

Contact our account support route and request access to your personal data. Provide your registered contact detail for verification, and we will explain the records that can be supplied.

Yes. Send a correction request through support with the field you believe is wrong and the accurate replacement. We may verify your account before changing contact or payment-related records.

Cookies may retain session choices and help identify loading issues on your phone browser. You can adjust browser settings, but disabling them may require repeated sign-in or account verification steps.

Retention depends on why the record was collected, such as security, account access or payment matching, together with applicable legal requirements. Support can clarify the handling of a specific record.