Reference

Open premium777 Privacy Policy Clearly

The premium777 Privacy Policy explains what we collect when you create an account, sign in from your phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice controlsPolicy requests
premium777 Open premium777 Privacy Policy Clearly
PRIVACY CONTACT

Reach Support About Your Privacy

A clear support route helps when a privacy question follows an account or wallet action.

Account access If you cannot sign in after phone verification, contact our support route with your account details and device path. We use the submitted record to check access activity without asking you to send a password or wallet PIN.
Wallet reference For a privacy question linked to DANA, OVO, GoPay or QRIS, include the transaction reference and approximate time. This gives our team a focused way to locate the related account entry and explain what we retain.
Data request Ask us to correct, access or clarify a personal-data record through the published contact route. We may request account verification first, so a change is applied to the right account rather than to another person’s record.
HANDLING DETAILS

Check Security Around Your Account Data

The way we handle account data is tied to real actions you take, not to a vague promise about privacy.

Account security

Phone verification is checked before account access, and sign-in activity can be associated with the device path used at that time. Never send us your password, one-time code or wallet PIN when asking about a record.

Mobile device signals

When you open the lobby in a mobile browser, we may process device and session signals needed to keep the session active and identify unusual access. These signals help us examine account security without reading unrelated phone content.

Cookies

Cookies and similar session tools help remember your sign-in state, language setting and selected page path. You can manage browser cookie settings, although disabling necessary cookies may interrupt account access or return you to the sign-in step.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be retained beside the related account action so we can match a receipt or status query. We do not need your wallet password or private wallet messages for that check.

Retention requests

We keep records only for the operational, security or legal purpose connected to them, then remove or anonymise them when that purpose ends where permitted. Ask through support if you need the retention reason for a particular record.

Policy changes

If this Privacy Policy changes, we place the revised wording on this page and update its date or notice details. You can ask support to explain a changed section, including how it affects account access or wallet references.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers address the searches we hear before an account is opened. Each answer stays close to the account, device and wallet actions that create a record, with the support route available when your question needs a case-specific check.

It covers account details, phone verification, sign-in and device signals, cookies, support messages and transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security controls and ways to request access or correction.

We use phone verification to confirm that the person requesting account access can complete the account step connected with that phone number. The verification status may be recorded for security checks, but you should not send a one-time code or wallet PIN to support.

Yes. When you use DANA or QRIS, we may retain a transaction reference, amount status and related account details needed to match the wallet action and answer a receipt question. The record does not require access to your private wallet messages or PIN.

Use the current support contact route and describe the account record you want to access or correct. We may ask you to complete account verification before responding, which helps prevent another person from receiving or changing your personal data.

The retention period depends on why the record was created, such as account security, wallet matching, support handling or a legal requirement. We remove or anonymise records when the relevant purpose ends where permitted. Support can explain the reason for a specific record.

You can adjust cookie controls in your mobile browser, but necessary session cookies may be required for sign-in and account access. If you clear them while using the lobby, you may need to complete the phone verification or login path again.

Yes. Account access and eligibility depend on local law, and our services are available where local law permits. If you need a region-specific privacy answer, contact support with your location and account question rather than relying on a general assumption.