Reference

Privacy Policy For Your ina168 Account

Your DANA, OVO, GoPay and QRIS choices need clear handling from the first phone check to the lobby, including when you connect from Medan.

Clear data purposesPhone check explainedWallet details protectedIndonesia access terms

Browse Our Lobby Read FAQ

How Our Privacy Policy Handles Wallet Data

ina168 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect account details you submit, such as your phone number, selected account credentials and verification results, so we can identify your account and respond when a wallet status needs checking. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we receive

1
transaction references, status results and receipt details needed to match activity to your account; we do not need your wallet password. We also record device type, browser signals, login time and security events to detect unusual access. Cookies help keep your session active and remember selected
2
settings. We retain records for the period needed for account security, payment reconciliation, support handling and legal duties. Access depends on local law, and where local law permits we explain any regional restriction before account use. You can ask us to clarify, correct or delete eligible
3
data through the account help route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WHEN NEEDED

Privacy Help Around DANA And QRIS

A clear contact route matters when a Privacy Policy question appears beside a receipt or wallet status. We direct your request through the account help path so the right account record can be found without asking you to send a wallet password. Include your registered phone number, the relevant transaction reference and the change you want us to check. We can then separate a login concern from a payment-status concern and explain the next step for your ina168 account.

Team online

Account data request

Use the account help path to ask what personal data is linked to your phone verification, why a field is needed, or which record you want corrected. We may ask for account checks before discussing private details.

Wallet receipt check

For DANA, OVO, GoPay or QRIS questions, provide the receipt reference and approximate time shown in your account. We use those details to trace status without requesting your wallet password or secret security code.

Access clarification

If a Privacy Policy question concerns regional access, tell us the account route and device you used. We explain the applicable step where local law permits and keep the request tied to your account record.

SECURITY PRACTICE

Cookies, Security And Account Records

Privacy work continues after your first account check. We separate sign-in events from wallet references, limit internal handling to the purpose being addressed, and use device signals to spot an unfamiliar login.

Data collected

We handle the account fields you provide, phone verification results, device signals, login events and payment references. These records help connect your account to the correct wallet status without storing your wallet password.

Cookie controls

Cookies support sign-in continuity, security checks and selected settings on your browser. If you clear them or change device settings, we may ask for phone verification again before showing account details.

Account security

Unusual device or login activity can trigger an additional account check. We use the event details to protect access and to distinguish a genuine request from an attempt to reach another account.

Retention period

We keep account, receipt and request records only as long as needed for security, reconciliation, support handling and legal duties. When a record no longer serves those purposes, it can enter our removal process.

Correction requests

You can ask us to correct inaccurate account details through the account help route. Include the field that needs attention and the phone verification path connected to your account so we can check the right record.

Who to contact

Send Privacy Policy questions through account help, especially when they involve DANA, QRIS, a login event or a deletion request. We may verify account ownership before sharing or changing personal data.

Privacy Policy Questions About ina168

These Privacy Policy answers cover the account steps most likely to matter before you open an account. We keep the wording practical: what data is collected, how wallet references are used, what happens on a new device, and how you can contact us when a record needs attention. Where access is discussed, it depends on local law.

The ina168 Privacy Policy covers account details, phone verification, device signals, login events, cookies, wallet references and support requests. It explains why we use each category, how retention works, and how you can ask for correction, deletion or clarification through account help.

Phone verification helps us connect you to the correct account before we discuss private records or change account details. It can also appear again after cookies are cleared, a device changes, or a security event needs checking before account access continues.

No. Our Privacy Policy distinguishes wallet status and receipt references from secret wallet credentials. When you use DANA, OVO, GoPay or QRIS, we use the transaction reference and result needed to match activity, while your wallet password remains outside our account records.

Use the account help route and state which field is inaccurate or which eligible record you want removed. Add your registered phone number and the relevant account path. We may complete an ownership check before correcting or deleting private data.

A new device can create a security event containing the device type, login time and related access signals. Our Privacy Policy allows us to request phone verification before showing account details, while cookies may need to be created again for the session.

We retain account, receipt and support records for the time needed for security, payment reconciliation, request handling and legal duties. The period can differ by record type. You can ask through account help which purpose applies to a particular record.

Send the question through account help and include the region, account step and device route involved. We explain eligibility where local law permits, and we avoid asking for wallet passwords when checking a DANA, QRIS or other payment reference.

Privacy Policy For Your ina168 Account

Privacy Help Around DANA And QRIS

Account data request

Wallet receipt check

Access clarification

Cookies, Security And Account Records

Data collected

Cookie controls

Account security

Retention period

Correction requests

Who to contact

Privacy Policy Questions About ina168

01 What does the ina168 Privacy Policy cover?

02 Why does Privacy Policy mention phone verification?

03 Does ina168 store my DANA or QRIS password?

04 How can I request a change to my personal data?

05 What happens to my data on a new mobile device?

06 How long does ina168 keep account and payment records?

07 Where can I ask about Privacy Policy access rules?

Related Pages