Reference

sukaliga Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a sukaliga account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet detailsCookie choicesSecurity requests
sukaliga sukaliga Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help For Login And Receipts

A clear contact path helps when you want to ask about Privacy Policy data or a wallet record.

Account access Use our account support path when you need to ask what contact details, sign-in records or verification data we hold. Include your registered phone number in the secure request, but never include your password or a complete wallet credential.
Wallet receipt For a Privacy Policy question linked to DANA, OVO, GoPay or QRIS, attach the transaction reference rather than a full account screenshot. We use the reference to locate the record and limit the personal data shown during the check.
Data request Ask us to access, correct or delete eligible account data through the same support route. State the exact request and the phone or email connected with your account so we can verify identity before replying.
CONTROL AND RETENTION

Inside Our Data Handling Process

We keep Privacy Policy controls close to the account steps you actually use. A phone check can confirm account ownership, device signals can flag an unfamiliar session, and cookie settings can affect…

Data collection

We collect account details you enter, messages you send for support, technical session data and payment references needed to identify a DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction.

Cookie controls

Cookies can remember sign-in preferences and help us understand whether a session is working. You can adjust cookie settings in your browser, although refusing some cookies may require you to repeat an account step.

Account security

We use phone verification before account access and examine sign-in signals such as device and browser details. These checks help us separate your normal session from an unfamiliar attempt without storing your password in readable form.

Payment records

A wallet or bank reference lets us match a receipt to the correct account without asking you to share a complete card or wallet credential. We retain the minimum transaction context needed for reconciliation and account questions.

Retention timing

We remove or anonymise personal data when it is no longer needed for account service, security review, dispute handling or a legal duty. Some records may remain longer where a documented legal or fraud-prevention reason applies.

Change requests

You can ask us to access, correct or remove eligible personal data. We may request account verification, explain any necessary retention, and confirm the result through the contact route tied to your account.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account and payment questions you are most likely to ask before opening sukaliga. They explain the practical path for access, correction, cookies, wallet records and contact requests without asking you to share unnecessary credentials. If a situation is not covered, contact us with the smallest useful set of account details and we will assess the request under applicable rules.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can ask to access or correct eligible data.

We use your phone number to create and verify the account, confirm that a request comes from you and help investigate an unfamiliar sign-in. The number can also connect a DANA, OVO, GoPay or QRIS receipt to the correct account when a status needs checking.

Yes. The Privacy Policy covers transaction references linked with QRIS, DANA, OVO, GoPay, bank transfer and virtual account steps. We use those references for reconciliation and support, not to request your password or a complete wallet credential.

Send a request through the account support path and state whether you want access, correction or removal of eligible data. Include the phone or email tied to the account, but omit passwords and full payment credentials. We verify identity before discussing personal records.

Cookies can retain sign-in preferences, support session continuity and help us identify technical failures. You can change cookie settings in your browser. If you block required cookies, you may need to repeat verification or other account steps during a later visit.

We retain personal data only while it supports account operation, security checks, payment reconciliation, dispute handling or a legal duty. When a record is no longer needed, we remove or anonymise it unless a documented legal or security reason requires longer retention.

Account access and eligibility depends on local law. Before opening an account, check that access is permitted in your location. If you have a Privacy Policy question about regional handling, contact support without sending sensitive credentials or unnecessary payment screenshots.