Reference

Privacy Policy For Clearer Access

Our Privacy Policy explains how kso303 handles your account details, wallet records and device signals when you open the lobby in Indonesia.

Account dataWallet recordsDevice controlsLocal-law access
kso303 Privacy Policy For Clearer Access
REQUEST A RESPONSE

Get Help With Data Requests

A clear support route helps when your Privacy Policy question concerns account access, a wallet reference or a device record.

Account access If phone verification blocks your account, tell us the registered phone number and device type through the account help route. We can check the access record, explain the next step and keep the request tied to your own account.
Wallet status For DANA, OVO, GoPay or QRIS questions, provide the payment reference and approximate time shown in your receipt. We check the status record and explain whether the request is pending, matched or cancelled without requesting your wallet password.
Privacy request To ask for a copy, correction or deletion assessment, write through our support path with your account phone number and the specific data request. We may ask for an account step to confirm that the request comes from you.
CONTROL YOUR RECORD

Keep Account Data Under Control

We separate account, payment and device records so a Privacy Policy request can be handled against the right source.

Account details

We use your account phone number and related registration details to create access, complete phone verification and connect your account activity to the correct wallet status. Keep these details current so a data request can be matched accurately.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us trace a cashier event. We use the reference, amount status and timing for reconciliation, support checks and dispute handling, not your wallet password.

Cookies and devices

Cookies can retain sign-in preferences and help us recognise a session, while device signals can flag an unfamiliar access attempt. You can clear browser cookies, but doing so may require phone verification again before account access.

Account security

We use phone verification and session checks to reduce account takeover risk. If you change device or browser, we may ask you to repeat an account step. Never share a verification code with another person or send it in a support message.

Retention period

We retain account, payment and security records only as long as needed for account operations, dispute handling, lawful requests or internal protection. When a record no longer serves one of these purposes, we assess it for removal or anonymisation.

Changes and contact

You can ask us to correct account details, provide a copy of linked records or assess deletion through the support path. Include the phone number and subject of your request; we may verify ownership before changing or releasing data.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. If your situation involves a specific receipt, device or phone verification event, use the support path so we can check the matching record.

It covers account details, phone verification, payment references, cookies, device signals, support requests, retention and security checks connected with your use of kso303. It also explains how to ask for a copy, correction or deletion assessment where local law permits.

We use your phone number to create the account record, complete phone verification and help confirm ownership when access changes. If you request a Privacy Policy action, the same account step may be needed before we release, correct or remove linked data.

No. We use payment references and status details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account reconciliation. We do not ask for your wallet password. Keep payment receipts available if you need us to trace a cashier event.

Cookies can keep session preferences and help connect your browser session with the right account record. Device signals can also flag an unfamiliar login. Clearing cookies may sign you out and trigger phone verification again before you regain account access.

Yes. Send a correction request through the support path with your account phone number and the exact detail that needs changing. We may verify ownership first, then check the source record and tell you whether the correction has been applied.

We keep payment and security records for the period needed for reconciliation, dispute handling, account protection or lawful requests. This can include DANA, OVO, GoPay, QRIS, bank transfer and virtual account references. We assess older records for removal or anonymisation.

You can ask us to assess deletion through the support route. Include your phone number and the records you want considered. Where local law permits, we review the request against account security, dispute handling and other operational duties before confirming the outcome.