Reference

ino777 Privacy Policy for Your Account

Your account details, wallet references and device access stay tied to a clear Privacy Policy, so you can understand what happens when you open the lobby from Indonesia.

Account data explainedCookie choicesIndonesia access

Browse Our Lobby Read FAQ

What this Privacy Policy covers in Indonesia

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

This Privacy Policy describes the account details we receive when you create access, verify your phone, sign in, contact support or request an account change. It also covers technical details such as device type, browser signals, login time and security events used to protect your session.

1
Payment references may show that you used DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, but we use those references to match account activity rather than present unnecessary wallet credentials. Cookies help remember preferences and measure page function. We keep records for the period
2
needed for security, support, dispute handling and applicable legal duties. If you access ino777 from Semarang or another Indonesian location, availability and eligibility depend on local law. We may update this page when our data practices change, with the current wording available through the policy link.

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

CONTACT ROUTE

Where to ask about your account data

A direct support route helps when you need to check, correct or remove information connected with your account. Start from the support contact shown in your account area and include the registered phone detail, the subject of your request and any relevant transaction reference. We use those details to locate the right record without asking you to send a wallet password or full security credential.

Team online

Data request

Use the account support contact to ask what personal details we hold, why they are used and which records relate to your phone verification or login history.

Correction path

If your contact detail is outdated, tell us through the listed support route. We may ask for an account step to confirm that the request comes from you.

Wallet context

For a DANA, OVO, GoPay or QRIS reference, include the visible transaction reference only. Do not send a wallet PIN, login password or complete payment credential.

DATA PRACTICE

How we handle cookies and account records

We separate the information needed to operate an account from optional signals that help pages load with your saved preferences.

Account details

We use your registration and phone-verification details to identify the correct account, respond to account requests and connect activity with the access path you opened.

Device signals

When you sign in on a mobile browser or desktop, we may record device and session signals to detect unusual access. These signals support security checks, not a separate public profile.

Cookies

Required cookies help maintain a signed-in session and remember selected settings. You can manage browser cookie controls, though disabling required cookies may interrupt login or policy-page functions.

Payment references

A DANA, QRIS, bank transfer or virtual account reference may be retained with account records so we can trace a status question without storing your wallet PIN.

Retention period

We retain account, support and security records only as long as needed for service administration, dispute checks, fraud prevention and legal duties, then remove or restrict them.

Change requests

To request access, correction or deletion, contact us through the support path shown in your account area. We verify the request before changing records or disclosing details.

Privacy Policy questions about ino777 accounts

These Privacy Policy answers cover the searches we expect when you are deciding whether to open an account or continue using one. We address the data connected with login, cookies, payment references, device access and support requests. Where a request affects account availability or eligibility, the outcome depends on local law and the verification details we can safely confirm.

It covers registration details, phone verification, login and device signals, cookies, support messages, security records and payment references linked to DANA, OVO, GoPay, QRIS or bank transfers.

Device and session signals help us recognise unusual sign-ins and protect your account. We may record browser type, access time and security events when you use a mobile or desktop path.

No. Our Privacy Policy treats DANA, OVO, GoPay and QRIS details as payment context or references. Do not send a wallet PIN, password or complete security credential through support.

Use the support contact displayed inside your account area and ask for an access request. Include your registered phone detail, then complete any identity check needed to protect the record.

Yes. Send a correction request through the listed account support route and explain which contact or registration detail is wrong. We may verify your account before applying the change.

We keep account, support, payment-reference and security records for the time needed for administration, dispute handling, fraud prevention and legal duties. Some records may then be removed or restricted.

Access and eligibility depend on local law. The Privacy Policy applies to data handled during an allowed account journey, including phone verification, login security and any support request.

ino777 Privacy Policy for Your Account

Where to ask about your account data

Data request

Correction path

Wallet context

How we handle cookies and account records

Account details

Device signals

Cookies

Payment references

Retention period

Change requests

Privacy Policy questions about ino777 accounts

01 What does the ino777 Privacy Policy cover?

02 Why does Privacy Policy mention my device?

03 Does ino777 store my DANA or QRIS PIN?

04 How can I request my account data?

05 Can I ask ino777 to correct my details?

06 How long does the Privacy Policy allow data retention?

07 Can I use ino777 where local law permits?

Related Pages