Reference

kapal288 Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open a kapal288 account, sign in from a mobile browser, browse Live Roulette or Aztec Gems Deluxe, and use…

Account dataWallet recordsCookie choicesAccess requests
kapal288 kapal288 Privacy Policy for Your Account Data
HELP WITH REQUESTS

Contact Us About Privacy Policy

A clear contact path helps you ask about the Privacy Policy without exposing account details in a public message. Start from the support route connected to your kapal288 account and include the phone number or email linked to access. We may ask for an account step or verification detail before discussing personal data, including records connected with DANA, OVO, GoPay, or QRIS.

Team online

Account access questions

Use the account support route when you cannot open your profile or need to know which personal data is tied to your login. We check ownership before sharing account-specific details.

Wallet record questions

Ask us to trace a DANA, OVO, GoPay, or QRIS reference through the support path attached to your account. Include the relevant date and reference so we can locate the record.

Change or deletion requests

Send a request through account support when your name, phone number, or contact detail needs correction. We explain which records can be changed or retained under applicable rules.

HANDLING YOUR RECORDS

What We Do With Account Data

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

Data we receive

We can receive details you submit during account creation, such as your name, phone number, and login contact. We also record requests you send to support so we can answer the same account matter accurately.

Device and session signals

When you sign in through a phone browser or desktop browser, we may record device type, browser details, session time, and security signals. These help us recognise unusual access without reading unrelated device content.

Cookies and preferences

Cookies can keep a session active, remember selected settings, and help us understand which policy page route brought you to an account action. Your browser controls can limit cookies, although some access steps may then need repeating.

Account protection

Phone verification and sign-in checks help us avoid sending personal account details to the wrong person. We may compare account, device, and transaction signals before discussing wallet records or changing contact data.

Retention and removal

We retain records for the period needed for account support, transaction matching, security checks, or applicable legal duties. When you request removal, we identify eligible data and explain any record that must remain.

Policy change requests

If a detail is wrong or your circumstances change, contact us through the account support path. Tell us whether you seek correction, access, restriction, or deletion, and we will explain the next verification step.

Privacy Policy Questions For DANA Users

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We keep the wording tied to actual access steps, mobile browsing, cookies, and local payment references. If your request involves a specific account, use the support route connected to that account so we can verify ownership.

The Privacy Policy covers account details, phone verification, browser and device signals, cookies, support messages, and transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

We use your phone number to create and protect account access, complete verification, and locate support records. We may request an additional account detail before discussing personal data or changing the linked contact.

Yes. The Privacy Policy covers data created when you sign in through a phone browser, including session time, browser type, and security signals. It does not give us access to unrelated files on your device.

DANA and QRIS references can be used to match a wallet action with the correct account and check its status. We keep those records for support, reconciliation, security, or applicable legal duties.

Yes. Send a correction request through the support route linked to your account and identify the name, phone number, or contact detail that needs updating. We verify ownership before making an account change.

We keep personal data for as long as needed for the stated account, support, transaction, or security purpose, and for any applicable legal duty. A removal request receives a specific response about eligible records.

Use the account support path and describe whether you need access, correction, restriction, or deletion. Include the linked contact detail, but do not send wallet passwords or unrelated sensitive material in your message.