Reference

kap33 Privacy Policy For Your Account

kap33 Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesAccess requests
kap33 kap33 Privacy Policy For Your Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact path helps you resolve a Privacy Policy question without sending sensitive details into the wrong channel. Start from your kap33 account support path and describe the specific record, such as a QRIS receipt, a login event or a wallet status. We may ask you to confirm account details before discussing personal data. Do not send a password, full wallet PIN or complete bank credentials. If you are in Medan or another Indonesian location, the same account-based route applies where local law permits.

Team online

Account support path

Use the support route connected to your account when you want to ask what personal data we hold or why a verification step appeared. We can use your account details to locate the relevant login, wallet or cashier record without asking you to share a password.

Payment record check

For a DANA, OVO, GoPay or QRIS question, include the transaction date, visible reference and current status rather than private wallet credentials. This gives us enough context to compare the receipt with the account ledger and explain the next step.

Change request

Ask us to correct account details through the same support route used for access questions. We may verify your identity before changing a phone number or other record, because an account step should not be altered by an unverified request.

DATA HANDLING DETAILS

Six Privacy Policy Checks We Apply

Privacy Policy work is part of the account flow, not a separate promise shown only on this page.

Account details

We use the details attached to your account to complete phone verification, protect login access and answer a data request. A mismatch between your submitted details and an account record may require an additional check before we disclose or change anything.

Wallet matching

Payment information is handled as an account and status record. DANA, OVO, GoPay and QRIS references help us identify whether a cashier action reached the correct account, while bank transfer details help us investigate a pending or disputed entry.

Cookies and devices

Cookies and device signals help keep your session connected as you move from login to the lobby on mobile or desktop. We may record browser type, IP address and security events, but you can manage some cookie storage through your browser settings.

Account security

We examine login events and device changes to help detect access that does not match your normal account pattern. If a security check interrupts access, use the account support path and complete the requested verification instead of sharing credentials in chat.

Retention period

We keep personal and payment records only for the period needed for support, account security, disputes and applicable legal duties. A request about retention can be assessed against the record type, including a QRIS receipt or a phone verification event.

Your request

You can ask about access, correction, deletion or the use of your information where local law permits. Tell us which account record concerns you, and we may request account verification before providing details or applying a change.

Privacy Policy Answers For kap33 Accounts

These Privacy Policy answers cover the questions we expect when you are deciding whether to open an account or continue using an existing one. They focus on the records created by login, phone verification, wallet activity and support requests. If your situation is not covered, contact us through the account support route with a short description and the relevant reference. We will use the available account information to identify the issue, subject to local law and required verification.

The kap33 Privacy Policy covers account details, phone verification, login and device events, cookies, payment references, support messages and retention. It explains why we use each category, how we protect access and how you can ask about correction, deletion or another permitted request.

These wallet and QRIS records help us match a cashier action with your account. We may store a reference, time, amount and status, but you should not send a wallet PIN or complete bank credentials when asking us to check a payment.

You can ask for access to the personal data connected with your account through the account support path. We may verify your phone or account details first, then assess the request against local law, security needs and information that belongs to another person.

Send a correction request through account support and identify the detail that appears wrong, such as a phone number or profile field. We may ask for verification before changing it, because an unverified change could affect login security or payment matching.

Retention depends on the type of record and the reason it is needed. A DANA, QRIS, bank transfer or virtual account reference may be kept for support, dispute handling, security checks and legal duties. You can ask us to explain the applicable period.

You can submit a deletion request through the account contact path where local law permits. We assess whether the information is still needed for account security, payment disputes, support records or legal duties, and we explain any part that must remain.

Contact account support promptly, avoid sharing your password or wallet PIN, and follow the requested verification step. We can check device and login records, help secure account access and review a related payment status when the event involves DANA, OVO, GoPay or QRIS.