Reference

Privacy Policy For Your layarxx1 Account

Our Privacy Policy explains how layarxx1 handles the details you provide when opening an account, verifying your phone, using the lobby or checking wallet status.

Account recordsWallet referencesCookie choicesPolicy requests
layarxx1 Privacy Policy For Your layarxx1 Account
CONTACT ROUTES

Get Policy Help Beside Your Account

A clear contact path helps you ask what we hold, why we use it or how to correct it.

Account policy request Use the account support route when you want a copy of personal data linked to your login, an explanation of its use or a correction to your name or phone record. We may verify account ownership before discussing details.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference and date shown in your receipt. We use those details to locate the relevant status without asking for your wallet password.
Cookie or device concern If a phone or browser keeps an old session, contact us through the policy support route and mention the device path you used. We can explain stored cookies, sign-in records and the steps available for clearing or correcting them.
DATA PRACTICE

What We Do With Your layarxx1 Data

We separate account details from the operational records needed to answer a wallet or access question.

Account data

We use your account details to create and maintain access, confirm the phone step and respond to account-specific requests. We do not need your wallet password to match a DANA, OVO, GoPay or QRIS reference with the correct account.

Cookies and sessions

Cookies can remember a sign-in state, language choice or device preference. Your browser controls whether cookies remain, while our support route can help explain a repeated session or a lobby access issue connected with stored browser data.

Security checks

Phone verification and sign-in signals help us distinguish an account holder from an unfamiliar access attempt. We may request a matching account step before changing personal details, discussing wallet records or responding to a request for account data.

Payment references

For deposits or withdrawals recorded through DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we retain reference data needed for status checks and receipt matching. The record is about the transaction path, not your wallet password.

Retention approach

We retain account, security and payment-reference records for as long as needed for the stated account, support and record-keeping purposes. When a record is no longer needed for those purposes, our handling process moves it toward removal or separation.

Changes and requests

You can ask us to correct inaccurate account details, explain a data use or clarify a cookie record through the policy support route. Include your account identifier and the requested change; we may verify ownership before acting.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions we expect you to have before opening an account or checking a wallet record. They explain what layarxx1 may receive, how device and payment references are handled, and which account step helps us protect your request. If your situation is not covered, use the policy support route with the smallest necessary set of details.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains correction requests, retention and policy-related contact.

Phone verification helps connect an account request with the person controlling that account. We may use the verification event when you request a data copy, ask us to change account details or need help with a wallet status record.

No. Our Privacy Policy concerns the payment reference and status needed for account records, not your DANA, OVO, GoPay or QRIS password. Do not send a wallet password to support. A receipt reference and date are usually more useful for a status check.

Cookies may keep a sign-in state, language choice or device preference. Your browser provides controls for clearing or blocking them. If an old session remains after those steps, contact policy support and identify the device path without sharing a password.

Yes. Send a correction request through the account policy route and state which detail is inaccurate, such as a phone or name record. We may ask for an account step or phone verification before changing information linked to your login.

We keep payment references, receipts and related account records for the period needed for status checks, support and record-keeping purposes. This can include DANA, OVO, GoPay, QRIS, bank transfer and virtual account references, without retaining your wallet password.

Use the policy support route beside your account and cashier paths. Describe whether you need access, correction, cookie clarification or an explanation of payment data. Include only the details needed to locate your account, and ownership checks may apply.