Reference

komslot Privacy Policy For Your Account

Our Privacy Policy explains what komslot collects when you create an account, sign in, use DANA or QRIS, and contact support about wallet status.

Account recordsWallet activityCookie choicesContact rights
komslot komslot Privacy Policy For Your Account
CONTACT PATHS

Reach Support About Your Privacy Policy

A clear support route helps when your account record or wallet reference needs attention. Open the support panel after signing in, choose the privacy or account-data subject, and include the phone number linked to your account without sending a password or one-time code. If sign-in stalls, use the contact route shown beside the cashier area so our team can match the case safely.

Team online

Account data request

Ask for a copy, correction, or deletion of account data through the signed-in support panel. We may ask you to confirm the phone number attached to the account before handling the request.

Wallet record check

For a DANA, OVO, GoPay, or QRIS reference, send the transaction date and visible reference only. Never include your wallet PIN, password, or one-time code in a support message.

Sign-in assistance

If you cannot reach the account support panel, follow the contact route beside the cashier path. We use account details already supplied to locate the case and avoid asking for unnecessary personal data.

HANDLING YOUR RECORDS

Explore How komslot Handles Privacy

We treat the Privacy Policy as an operating process, not a page kept apart from the account. Phone verification supports sign-in checks, device records help identify unusual access, and payment references help…

Data collected

We may record your account name, phone verification result, sign-in events, device signals, support messages, and payment references. The purpose is to provide account access, protect records, and answer privacy requests.

Cookie controls

Cookies can support sign-in continuity, page settings, and security checks on your phone or computer browser. Use the cookie controls shown on the site to adjust optional choices without changing required account functions.

Account security

Before changing account data, we may compare your phone verification and recent sign-in details. This step helps prevent another person from changing your record through a copied payment reference or shared device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity may create references used for matching and status checks. We do not need your wallet PIN or one-time code to investigate a receipt.

Retention requests

We keep records only for the operational, safety, dispute, or legal period that applies to them. You can ask what remains stored or request deletion, although some transaction records may need to remain.

Policy changes

When this Privacy Policy changes, we place the updated wording on the policy page and show the effective date. Check it before opening an account or changing wallet details, especially when local rules change.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the account, device, cookie, wallet, and contact questions you may have before opening access. We keep each response tied to a practical step, from phone verification to a request sent through the signed-in support panel.

The Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

Phone verification helps connect the correct person to an account and supports requests to change or remove data. We may use it again when a privacy request or unusual sign-in needs confirmation.

Yes. It covers references created when you use DANA, QRIS, OVO, GoPay, bank transfer, or a virtual account. We use those references for matching, receipt checks, status enquiries, and account support.

Sign in, open the support panel, select the account-data or privacy subject, and request a copy. Include the phone number linked to your account; do not send a password, wallet PIN, or one-time code.

You can request a correction or deletion through the same support route. We first confirm the account, then assess the request against operational, dispute, safety, and legal record-keeping needs.

Cookies may support sign-in continuity, settings, and security checks in your mobile browser. Use the cookie controls on the site to adjust optional cookies while required account functions remain active.

Use the signed-in support panel and choose the privacy or account-data subject. If you cannot sign in, use the contact route beside the cashier area; availability and handling depend on local law.