Reference

Open ino777 Privacy Policy Before Account Access

ino777 Privacy Policy explains which account details we collect, why cookies appear, and how we handle payment references from DANA, OVO, GoPay and QRIS.

Account dataCookie choicesWallet referencesAccess requests
ino777 Open ino777 Privacy Policy Before Account Access
ASK OUR DESK

Contact Support About Privacy Policy

A clear support path helps when you want to question a record rather than troubleshoot a lobby screen. From your account area, send a Privacy Policy request with the email or phone detail linked to your account. We can direct questions about cookie use, wallet references, device activity and access eligibility to the right handling route. Include a receipt reference when your question concerns DANA, OVO, GoPay or QRIS.

Team online

Account request

Use the account support route and identify the phone or email attached to your profile. We use that step to separate your request from another account before discussing stored details.

Payment question

For a DANA, OVO, GoPay or QRIS query, include the payment reference and date, not a wallet password or personal access code. We use those details to locate the record.

Access concern

If a privacy question affects account access, tell us your device type and location context. We can explain the policy route while eligibility remains dependent on local law.

DATA HANDLING

Switch Through ino777 Privacy Controls

We keep Privacy Policy handling practical: collect only what an account step needs, protect sign-in activity, and record the action taken on a data request.

Collection

We may collect your contact detail, verification input, login time, device signal and support history when those records support account access or a Privacy Policy request.

Cookies

Session cookies help keep a phone or desktop sign-in connected. We can explain their purpose when you ask, including whether a cookie supports access, preferences or security checks.

Account security

We review unusual sign-in signals and verification steps before discussing account data. Never send a password in a support message; identify the account through its linked contact detail.

Payment records

A wallet or bank reference can help us match a payment question, but it does not give us access to your DANA, OVO, GoPay or bank credentials.

Retention

We retain records for the stated account, security or legal purpose, then assess whether they are still needed. Ask support to explain the retention reason for a specific record.

Change requests

You can request correction, clarification or access to your personal record through the account support route. We may ask for matching details before releasing or changing anything.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before account access. They explain data collection, cookies, payment references, correction requests and local eligibility in plain English. If your situation is different, use the support route with the contact detail linked to your ino777 account, and we will assess the request against the current policy wording.

It covers account details, verification records, login and device events, cookies, support messages, payment references, retention, data requests and disclosures connected with your account.

Yes. The policy explains how we may use transaction markers or receipt references from DANA, OVO, GoPay and QRIS to match a payment question without requesting your wallet password.

Depending on your account steps, we may receive contact details, verification input, login events, device signals, support correspondence and payment references needed for account administration.

A mobile browser may store session cookies that keep sign-in connected or remember a preference. Ask support about a specific cookie and we will explain its purpose and handling.

You can ask for access, clarification or correction through the account support route. Include your linked phone or email so we can verify the request before discussing your record.

We keep records for the stated account, security or legal purpose and review whether they remain needed. Support can explain the retention reason for a particular record.

The policy explains data handling, while account eligibility and access depend on local law. We can clarify the data used in an access step without changing that legal condition.