Reference

Privacy Policy for Your kijang178 Account

Our Privacy Policy explains how we collect, use and protect the details you provide when opening a kijang178 account, signing in and checking wallet activity.

Account dataCookie choicesWallet recordsAccess requests
kijang178 Privacy Policy for Your kijang178 Account
PRIVATE HELP PATH

Contact kijang178 About Privacy Policy Questions

A clear support path helps you deal with a privacy question without explaining your whole account history in public. Use the account support route when you need to ask about a data field, a cookie choice, a phone verification record or a wallet reference. Tell us the account contact and the specific request, but do not send a password or full payment credentials. We may ask for an account step that confirms you are the person making the request. Your request remains connected to Privacy Policy handling, not to a general lobby enquiry.

Team online

Account access

If you cannot reach your account, contact the support route and identify the account contact you used. We can explain which verification detail is needed before discussing stored data, without asking you to reveal your password or a complete DANA, OVO, GoPay or QRIS credential.

Wallet references

For a Privacy Policy question about a payment record, mention the rail used and the approximate account activity, such as QRIS or bank transfer. We use that context to locate the relevant reference while keeping the request focused on data handling rather than exposing unrelated account activity.

Change requests

When you ask us to correct contact data or clarify retention, state the exact change you want. We may verify your phone before acting. A precise request helps us respond about the affected record and avoid changing information that is required to keep the account access trail accurate.

DATA HANDLING

What We Keep Secure Inside Your Account

Privacy Policy handling starts when you enter an account contact and continues through sign-in, phone verification and wallet status checks.

Collected details

We may hold your account contact, phone verification result, sign-in events, device information and messages connected with support. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use can be linked to the account activity they describe.

Cookie controls

Cookies can support sign-in continuity, security checks and remembered settings on your browser. If you clear them or change browser controls, you may need to repeat an account step. Privacy Policy questions about cookie use can be sent with the device and browser you use.

Account security

Phone verification helps us confirm account access before we discuss private records. Keep your password private and sign out on shared devices. If a sign-in looks unfamiliar, contact support with the account contact and device path so we can examine the access event.

Retention reasons

We retain some records for account security, payment matching, dispute handling and legal duties. Retention can differ by record type, so a request to remove one field may not remove every related transaction or verification record. We can explain the reason for a retained record.

Correction requests

You can ask us to correct an inaccurate name, phone detail or contact record by describing the field and the right value. We may request phone verification or another account check before making a change, helping us prevent one person from altering another person's private details.

Policy contact

For a Privacy Policy request, use the support route and include the account contact, request type and relevant device or wallet context. We will focus on the record you identify. Never include a password, full card detail or a complete wallet security code in your message.

Privacy Policy Answers for kijang178 Accounts

These Privacy Policy answers address the account questions you are most likely to have before opening access from Indonesia. They explain the data connected with sign-in, device use, cookies, wallet references and support requests. If your situation is different, send us the account contact and a focused question through the support path. Eligibility and access remain dependent on local law, and we may need to confirm your identity before discussing private records.

The kijang178 Privacy Policy covers account contact details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, when retention may apply and how you can request access, correction or clarification about a record.

Phone verification helps us confirm that the person asking about an account or Privacy Policy record is connected with that account. It also supports account security during sign-in. We will not ask you to provide your password when handling a privacy request.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS when those details help match account activity. Bank transfer and virtual account references may also be retained for reconciliation, support and dispute handling.

You can request a correction to an inaccurate account contact, phone detail or related record. Describe the field and the correct value through support. We may complete a phone verification step before changing it, and some transaction records may need to remain unchanged.

Send a focused request through the account support route using the contact attached to your account. Name the data category you want, such as cookies, sign-in events or QRIS references. We may verify your account first, then explain the available record and any retention limits.

Yes. Tell us that your request concerns cookies and include the mobile browser or device path involved. Clearing cookies can end a remembered session or require another sign-in step. Our Privacy Policy explains how cookies support access continuity and security checks.

No. Account access and eligibility depend on local law. The Privacy Policy explains our data handling, but it does not change the rules applying in your location. If you are unsure, ask support about the relevant access question without sending sensitive payment or password details.