Reference

slot apk hijau Privacy Policy Explained

slot apk hijau Privacy Policy shows what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account detailsWallet recordsDevice choicesCookie controls
slot apk hijau slot apk hijau Privacy Policy Explained
CONTACT YOUR WAY

Find Privacy Help Near Wallet Status

A direct support path helps you ask about personal data without explaining your whole account history.

Data access request Ask us which account details, sign-in records or wallet references we hold.
Correction request If your phone detail or account record is inaccurate, tell us what needs changing…
Privacy concern For an unexpected message, device sign-in or payment reference, contact support from the account…
DATA HANDLING

Browse How We Protect Your Account Records

We separate ordinary account use from the checks needed for security and payment reconciliation. Device signals can help us notice an unusual sign-in, while transaction references help match DANA, OVO, GoPay, QRIS…

Account collection

We collect the details needed to create and maintain your account, including contact information and verification results. Fields shown during account opening indicate what we need at that step, rather than asking for unrelated background details.

Device signals

A phone or desktop session may provide device and connection signals used to recognise a returning sign-in and investigate unusual activity. These signals support account security; they are not a substitute for your password or verification step.

Cookie choices

Cookies can keep a session working, remember a selected setting and help us understand errors on the account path. You can manage cookies through your browser, although blocking some types may affect sign-in or saved preferences.

Payment references

We may retain a rail name, amount reference, receipt detail and status history when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These records help resolve mismatched wallet or cashier entries.

Retention timing

We keep personal data only for the period needed for account operation, security checks, dispute handling or legal duties. When a record is no longer needed, we remove it or reduce its connection to your account where practical.

Your requests

You can ask for a copy, correction or deletion where local law permits. Send the request through account support, identify the relevant record, and complete our identity check so another person cannot alter or obtain your data.

Ask About Privacy Policy And Access

These Privacy Policy answers cover the questions we expect you to have before opening an account or connecting a local wallet. We explain the practical records involved, how to contact us and what may happen when a request meets a legal or security requirement. Access depends on local law.

It covers personal data handled through account opening, sign-in, device sessions, cookies, support contact and payment references. The Privacy Policy also explains how we respond to access, correction and deletion requests, subject to security duties and where local law permits.

We may collect your contact detail, account identifier, verification result, sign-in history and device signals connected with access. We use these records to maintain your account, check unusual activity and answer a request about your own data.

Yes. When you use DANA, OVO, GoPay or QRIS, we may retain the payment rail, receipt reference, status and account link needed to reconcile a transaction. Bank transfer and virtual account references can be handled for the same purpose.

Contact us through the support path inside your account and state that you want a data copy. Include the relevant phone detail or account reference. We will verify account ownership before explaining which records can be provided.

You can request correction or deletion through account support where local law permits. We may retain selected records when security checks, transaction reconciliation or a legal duty requires them, and we will explain that reason in our response.

Cookies may keep your session active, remember a setting and help identify technical errors on the account path. You can adjust them in your browser. Blocking necessary cookies may prevent sign-in or remove saved preferences from your device.

Contact account support promptly from the account area and provide the date, device if known, and affected rail such as QRIS or DANA. We may pause discussion of private records until identity is confirmed and the account history is checked.