Reference

bujangan 138 Privacy Policy

Your account data, wallet records and device details receive a clear explanation in the bujangan 138 Privacy Policy.

Account dataWallet recordsCookie choicesContact requests
bujangan 138 bujangan 138 Privacy Policy
CONTACT PATHS

Privacy Help Near Your Account Route

A clear contact path helps you ask about the Privacy Policy without sending the same request through several account screens.

Data question Ask how your account details, phone verification record or device identifier is collected and…
Wallet receipt If a DANA, OVO, GoPay or QRIS reference is attached to your account, provide…
Access correction Request a correction when your name, phone detail or account record is inaccurate.
DATA PRACTICES

Inside Our Privacy Controls

We keep the Privacy Policy practical by linking each data practice to an account action you can recognise.

Account security

Phone verification is connected to account access, while login events and device signals help us detect unusual activity. We do not ask you to disclose a password when you submit a Privacy Policy question.

Cookie choices

Cookies can remember session settings and device preferences while you move from login to the lobby. Your browser controls can remove or restrict them, though some account steps may then need repeating.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match payment status with the correct account. They are not used as a reason to request wallet passwords.

Retention period

We retain account, security and transaction records only while they support account operation, dispute checks, fraud prevention or legal duties. When a record is no longer needed, our process assesses removal or limitation.

Data request

You can ask what personal data is linked to your account, request a correction, or ask about handling purposes through our site contact route. We may verify ownership before releasing account-specific details.

Device behaviour

Mobile and desktop sessions may create different cookie or security records because browsers store settings differently. We use those signals for account continuity and protection, not to read unrelated device content.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account steps you are most likely to question before opening access. They cover phone verification, wallet references, cookies, device records, correction requests and local eligibility. If your situation is not covered, contact us through the support route shown on the site and describe the specific record you want us to check.

It covers personal data collected during account creation, phone verification, login, cookie use, device security checks and wallet activity. It also explains retention, correction requests and how to contact us about your records.

We use your phone number for account identification and the verification step before account access. It helps connect the right security record to your account and supports correction checks when you contact us.

Yes. The Privacy Policy covers transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help match payment status without asking for your wallet password.

Use the contact route shown on our site and state whether you want a data copy or correction. Include your account identifier, never a password, and be ready to confirm account ownership.

Yes. It explains that cookies can retain session and device preferences when you move through login and the lobby. Your mobile browser can restrict or clear them, although some account steps may repeat.

We keep account, security and transaction records while they are needed for operation, dispute checks, fraud prevention or legal duties. We then assess whether the data should be removed or its use limited.

Account access and eligibility depend on local law. Where local law permits, you can review the Privacy Policy before creating an account and contact us if you need clarification about data handling.