Reference

Privacy Policy for kijang500

Our Privacy Policy shows what we collect when you open an account, complete phone verification and move between the lobby and wallet area.

Account clarityWallet dataDevice controlsContact path

Explore Our Lobby Read FAQ

How wallet data is handled

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

Our Privacy Policy covers data connected with account creation, phone verification, sign-in, wallet activity and requests sent through the support path. We may record the payment rail you select, such as DANA, OVO, GoPay, QRIS, virtual account or bank transfer, together with a reference needed to

1
match a cashier status. We do not need your full wallet balance to explain every lobby page, but transaction records may be retained when they help resolve a payment question, prevent account misuse or meet a legal duty. Access depends on local law, and we apply
2
this policy where local law permits. The policy also covers cookie choices, device signals and messages you send about your personal data.

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

CONTACT ROUTES

Where privacy questions go

A clear contact route helps you act on this Privacy Policy without guessing which team to reach.

SIX DATA CONTROLS

Six controls behind your data

Privacy work is handled through practical account controls rather than vague promises. We separate sign-in checks from wallet references, limit staff access to records needed for a task and use device signals…

Account details

We may collect your phone number, account credentials, verification result and messages sent to support. These details let us provide account access and connect a request to the right record without asking you to repeat private data across separate contacts.

Cookies and devices

Cookies and device signals can keep a session working, remember a selected setting and flag unusual sign-in behaviour. You can manage browser cookie settings, though removing some cookies may require another login before the lobby or account area opens.

Account security

Phone verification comes before account access, and we may compare sign-in details with recent account activity when a session looks unusual. Never share a password or one-time code through support; those secrets are not needed for a privacy request.

Retention periods

We keep account, payment-reference and support records only for as long as needed for the stated purpose, account administration, dispute handling or a legal duty. When a retention period ends, we remove, restrict or aggregate the relevant record.

Your requests

You can ask for a copy of eligible account data, correction of an inaccurate detail or deletion assessment through the support path. We may request phone verification or another account check before acting so private records are not sent to the wrong person.

Policy changes

If this Privacy Policy changes, we will place the updated wording on this page and show the effective date. Material changes may require a fresh account acknowledgement, while continued access where local law permits does not erase your request rights.

Privacy Policy questions answered

These Privacy Policy answers focus on the account actions you are most likely to take at kijang500. They explain what happens around phone verification, wallet references, cookies, device access and personal-data requests. If your situation is not covered, use the support route beside the cashier area and describe the specific record or action you want us to check.

The kijang500 Privacy Policy covers account creation, phone verification, sign-in, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, virtual account or bank transfer. It also explains requests for access, correction, deletion assessment and policy changes.

Phone verification helps us connect an account request to the person seeking access and reduces mistaken disclosure. We may use the verification result when you ask for account data, change a detail or question a wallet reference. Account eligibility depends on local law.

Yes. The policy covers payment-rail selection and reference details needed to match a DANA or QRIS action with the correct account status. We may also handle equivalent references for OVO, GoPay, virtual account and bank transfer without asking for your secret wallet code.

You can use the support path in your account area to request access to eligible personal data. Include the phone detail linked to your account and explain the record you seek. We first check account ownership, then assess the request under applicable law.

Send a correction request through the privacy contact route and identify the inaccurate field, such as a phone detail or support record. We may ask for a phone verification step before changing it. Payment references may need to remain unchanged for dispute or legal purposes.

Retention depends on the type of record and its purpose. Account, support and payment-reference data may remain while needed for access, payment questions, dispute handling or a legal duty. After that period, we remove, restrict or aggregate it where permitted.

Yes. The Privacy Policy applies when you use the mobile lobby path, a phone browser or desktop access. Device signals and cookies may support session security across those paths. You can request details about associated device records through the account support route.

Privacy Policy for kijang500

Where privacy questions go

Six controls behind your data

Account details

Cookies and devices

Account security

Retention periods

Your requests

Policy changes

Privacy Policy questions answered

01 What does the kijang500 Privacy Policy cover?

02 Why does kijang500 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS data?

04 Can I request my personal data from kijang500?

05 How do I ask kijang500 to correct my data?

06 How long does kijang500 keep account data?

07 Does this Privacy Policy apply on mobile devices?

Related Pages