Reference

kasir168 Privacy Policy for Your Account

Your kasir168 Privacy Policy puts account, phone-verification, device, and wallet handling in one clear place.

Account recordsWallet referencesDevice cookiesPrivacy requests
kasir168 kasir168 Privacy Policy for Your Account
REQUEST HELP CLEARLY

Where To Ask About Privacy Changes

A privacy question should not get mixed up with a stalled cashier status. Sign in, open the account help route beside your cashier area, and send the request from the account concerned so we can match your identity and transaction references. If you cannot sign in, use the same support route shown on the access screen and include only the details needed to locate your record.

Team online

Account route

Send a Privacy Policy question from your signed-in account area. We can connect the request with your phone-verification record without asking you to repeat wallet credentials or share a full payment password.

Cashier context

For DANA, OVO, GoPay, or QRIS questions, include the transaction reference, date, and status shown to you. That gives our support team a focused path without requiring unnecessary personal details.

Access fallback

If account access stalls, use the support link displayed on the access screen and explain the privacy request. We may ask for phone verification before discussing account-specific records with you.

SIX DATA CONTROLS

Six Practical Controls for Your Data

Our handling process follows the same account steps you already recognise: phone verification before account access, a session on your chosen device, and payment references attached to the correct wallet status.

Account details

We use the account details you provide to create access, respond to account requests, and keep records connected to the correct person. You can ask us to correct inaccurate details through the account support route.

Phone verification

Before discussing account-specific data, we may compare your request with the phone-verification step used during access. This helps prevent another person from receiving your wallet status or account history.

Device signals

Your browser, operating system, session time, and related device signals may be recorded to recognise returning access and identify unusual sign-in patterns. You can ask what is held for your account.

Cookie choices

Cookies can keep your session active and reduce repeated account checks. Clearing cookies may require another sign-in or phone verification; send a request if you need details about a specific cookie.

Payment references

For QRIS, DANA, OVO, GoPay, bank transfer, or virtual account activity, we retain references and statuses needed to reconcile the account. We do not ask for your wallet password in a support request.

Retention requests

We keep records only for account operation, payment matching, dispute handling, or legal needs. Ask us to delete or stop using eligible data, and we will explain the result where local law permits.

Privacy Policy Questions About kasir168

These answers address the questions we expect you to ask before opening an account or sending a privacy request. They focus on account records, cookies, payment references, device access, and the steps needed to reach us. If your situation is not covered, use the account support route and refer to the Privacy Policy in your message.

It covers account details, phone verification, device and cookie signals, payment references, support requests, retention, and your available choices. It applies to account access and related services where local law permits.

Phone verification helps connect access with the correct account and protects account-specific discussions. We may use it when you ask about stored data, a wallet reference, correction, or deletion request.

No. We may retain a DANA or QRIS transaction reference, amount status, and matching details, but a support request should never include your wallet password, PIN, or one-time access code.

Yes. Send a correction request through the signed-in account support route and identify the field that appears wrong. We may complete phone verification before changing account-specific records.

Cookies can remember a session and help reduce repeated checks on the same browser or device. Removing them may sign you out, after which phone verification could be required again.

Use the support route in your account area and state which data you want removed. We will assess the request against account, payment, dispute, and legal retention needs where local law permits.

Yes, the policy page can be opened from your browser, but account access and eligibility depends on local law. You can contact support if a regional access message appears on your screen.