Reference

Open 567live With Privacy In View

567live Privacy Policy explains what we collect when you create an account, sign in on mobile, verify your phone or use DANA, OVO, GoPay and QRIS.

Account collectionWallet referencesDevice controlsPolicy access
Explore Our Lobby Read FAQ
567live Open 567live With Privacy In View
CONTACT PATHS

Ask About Privacy Through Account Support

A clear contact path matters when you want to understand a data record, correct an account detail or ask why a wallet reference appears in your history.

Privacy request Use our available account support contact path to ask what personal data is linked to your 567live account. Include your registered phone number and the request type, such as access, correction or deletion, so we can locate the right record without asking for your DANA, OVO or GoPay secret.
Wallet status question If a QRIS, bank transfer or virtual account reference looks unfamiliar, contact support from the account area and describe the date, status and reference shown. We use those details to investigate the record while keeping your wallet PIN, one-time code and full payment credentials out of the request.
Login and device help For a privacy concern after a new phone or browser sign-in, tell us which device path you used and when the change occurred. We may ask for account verification before discussing records, helping us avoid exposing personal details through an unverified support conversation.
DATA HANDLING

Switch Through Six Privacy Controls

We handle privacy as an account operation rather than a general statement. Registration creates the core account record; phone verification helps connect later sign-ins to you; device and security events help us…

Account details

We collect details you provide during account creation, including contact data needed for access and support. Check each field before submitting it, because accurate registration details help us match a privacy request with the correct account rather than another account using a similar phone number.

Phone verification

A phone verification step can connect your account to a confirmed contact route before access is completed. We record the verification result and related security event, not your private phone messages. If your number changes, contact support so the account record can be checked.

Device signals

Browser and device signals may show a new sign-in, unusual session or repeated access attempt. On a shared device, sign out after using the account and clear saved browser data if needed. These signals support account security and are not treated as a statement about your identity by themselves.

Cookies

Cookies can retain a session choice and help us understand whether a page loads correctly on mobile or desktop. You can manage browser cookie settings, although disabling some cookies may require another sign-in or prevent a policy page from displaying its saved state.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may keep a reference, amount status and processing timestamp needed for account reconciliation. We do not request your wallet PIN. Payment providers may handle separate data under their own privacy terms.

Retention requests

We retain personal data while it supports account access, security checks, support resolution or a legal requirement. You can ask what remains, request a correction or ask whether removal is available. We may retain a limited record of the request and its outcome for audit and security purposes.

Explore Privacy Policy Answers Before Access

These Privacy Policy answers cover the account steps Indonesian customers most often ask about before they open an account. We explain what is collected, why wallet references appear, how device access is handled and where to send a request. If your question concerns a specific record, use the account support path and describe the relevant sign-in or payment event without sharing private authentication details.

The 567live Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains how we use those records for access, security, reconciliation and support, with availability and eligibility handled where local law permits.

We collect details you submit during account creation, such as contact information used for access and support. We can also record verification results, session events, device signals and account-related messages. We do not need your DANA, OVO or GoPay wallet PIN.

The Privacy Policy mentions QRIS, bank transfer and virtual account activity because a payment reference, status and timestamp may need to be matched with your account. This supports reconciliation and support checks; the payment provider remains responsible for its separate handling of provider-side data.

Yes, you can contact us through the available account support path to ask what personal data is linked to you or to request a correction. Include your registered phone number and the specific change, but do not send wallet PINs, one-time codes or passwords.

We may record a new browser or device sign-in as a security event and use related signals to investigate unusual access. If you do not recognise the event, contact support promptly from your account path. We may verify your identity before discussing the record.

We keep personal data while it is needed for account access, security, payment reconciliation, support resolution or a legal requirement. When those needs end, we remove or de-identify records where practical. Some request and security records may remain to document how an issue was handled.

Use the available support contact path linked to your account and label the message as a Privacy Policy request. Explain whether you need access, correction, deletion or clarification, and mention the relevant device or payment reference. We will ask for only the checks needed to locate your record.

Related Pages

567live Indonesia Tennis Grand Slam 567live Casino Account information FAQ