Reference

indo78 Privacy Policy for Your Account Data

indo78 sets out how we collect, use and protect your account, device and wallet details when you access our lobby from Indonesia, including in Denpasar.

Account clarityWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How Privacy Policy Covers Wallet Records

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

Our Privacy Policy applies to data you provide while opening an account, confirming your phone number, signing in, contacting support or checking a payment status. We may record account identifiers, login events, device details, cookie settings and transaction references so we can keep access orderly and

1
match a wallet update to the right account. DANA, OVO, GoPay and QRIS names may appear in payment records, while bank transfer or virtual account references can help us trace a request. We use these records for account administration, security checks and service messages, and share
2
them only with providers needed to operate those steps or when a lawful request requires it. Retention depends on the purpose and applicable rules. Your access or eligibility depends on local law, and this policy does not change that position.

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

CONTACT ROUTES

Where to Ask About Privacy Policy

A clear contact route helps you handle a data question without repeating your account story. Use the support path shown after login and include the account detail, wallet reference or device concern connected to your request. We use the same route for Privacy Policy questions, correction requests and access concerns, while account access itself remains subject to local law.

Team online

Account data request

Ask us to locate the account records connected with your phone verification step. Include your account identifier so we can check the right profile without asking you to send a wallet password.

Wallet record query

If a DANA, OVO, GoPay or QRIS reference looks incorrect, send the transaction reference through our support path. We can match the record to your account and explain the next data step.

Policy correction route

Use the account support link when a name, phone detail or contact record needs correction. We may request a verification step before changing data tied to account access.

DATA PRACTICES

Six Data Practices Behind Our Policy

We keep this Privacy Policy practical by connecting each data use to an account action you can recognise.

Phone verification

Before account access, we use the phone verification step to connect your sign-in with the correct account. This reduces duplicate records and helps us respond to a data request about your profile.

Cookie controls

Cookies can store sign-in preferences, page settings and security signals on your browser. You can manage browser cookie controls, though removing some cookies may require another account sign-in.

Mobile device signals

When you use a phone to move from login to the lobby, we may record device and connection details for security checks. We do not need access to unrelated files on your device.

Account protection

Login events, verification attempts and wallet status checks can be retained to identify unusual access. We may pause a request while confirming that the account holder is making it.

Retention periods

We keep each data type only as long as its account, security, payment or legal purpose requires. Transaction references may remain after a session ends so a payment question can be traced.

Change requests

You can ask us to correct eligible account data or explain how a record is used through the support path. We may need identity checks before releasing or changing protected details.

Privacy Policy Questions You May Search

These Privacy Policy answers focus on the account and payment details you are most likely to ask about before opening an account. We explain what we collect, why it is used, how to reach us and what local-law wording applies when you request access.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for the account verification step and account matching. It helps us connect a support request with the correct profile and detect sign-in activity that needs checking.

Yes. The policy covers payment references and status details linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. We use them to trace account-related payment questions.

Use the support path available after login and state that you are making a data access request. Include your account identifier, then complete any verification needed before we release protected details.

You can request a correction through account support when a phone, name or contact record is inaccurate. We may confirm your identity first, especially when the change affects account access.

Cookies may retain browser preferences, sign-in state and security signals when you use a mobile path. Your browser settings control many cookies, but clearing them can require another login.

Yes. Account access and eligibility depends on local law. This Privacy Policy explains data handling, but it does not expand access beyond the rules that apply to your location.

indo78 Privacy Policy for Your Account Data

Where to Ask About Privacy Policy

Account data request

Wallet record query

Policy correction route

Six Data Practices Behind Our Policy

Phone verification

Cookie controls

Mobile device signals

Account protection

Retention periods

Change requests

Privacy Policy Questions You May Search

01 What does the indo78 Privacy Policy cover?

02 Why does indo78 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request my indo78 account data?

05 Can I ask indo78 to correct my personal data?

06 How does the Privacy Policy handle cookies on mobile?

07 Does access under this Privacy Policy depend on local law?

Related Pages