Reference

emas168 Privacy Policy for Your Account

emas168 Privacy Policy explains what we collect when you open an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet status checksMobile browser accessPhone verification

Explore Our Lobby Read FAQ

Know What DANA Data We Receive

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

Our Privacy Policy describes the account details needed to create and protect your emas168 access, such as your contact details, phone verification result, sign-in records and device signals used to detect unusual access. When you choose DANA, OVO, GoPay or QRIS, we receive payment status and

1
reference details needed to match your account activity; we do not ask for a wallet password. Bank transfer and virtual account references may also appear in your payment record. We use this data to confirm actions, answer account questions and investigate mismatched receipts. We retain records
2
only for the operational, security or legal period that applies to the request. Where access or eligibility is discussed, it depends on local law. You can ask us what data is held, why it is used, or whether a correction is needed through the contact paths
3
below.

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

PRIVACY HELP PATHS

Reach Us About Privacy Questions

A direct support path helps you ask about the Privacy Policy without guessing which account screen to use.

Account help Use the account help path beside your login area to ask what personal data is connected to your profile, why phone verification appears, or how to request a correction.

Wallet receipt For DANA, OVO, GoPay or QRIS questions, send the receipt reference and account contact detail. We use those details to check payment status without requesting your wallet password.

Access request If you need a copy, change or removal request, state the exact account step involved, such as login, phone verification or cashier history, so our team can route it accurately.

CONTROLLED DATA PRACTICE

How Your Account Data Stays Controlled

We keep this policy practical by linking each data category to an account action you can recognise.

Account details

We use contact details and phone verification results to create access, confirm account requests and send replies about your privacy question. You can ask us to correct inaccurate account data.

Cookies

Cookies can remember session choices and help the mobile browser return you to the correct account path. You can clear browser cookies, although doing so may require another sign-in.

Security signals

Device and sign-in signals help us identify unusual account access. If a check interrupts your route to the lobby, contact account help and describe the device path you used.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help match a receipt to your account. We use payment status details, not your wallet password.

Retention periods

We keep personal data for the period needed for account operation, security checks, dispute handling or applicable legal duties. A request can ask which retention reason applies to your record.

Change requests

Send a correction, access or deletion request through account help with your connected contact detail. We may ask for phone verification before changing information tied to account access.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the account actions most likely to raise a question before you open access. We address mobile sign-in, wallet records, cookies, data requests and local eligibility so you can decide what to provide before using emas168.

It covers data collected during account creation, phone verification, sign-in, mobile browsing, payment status checks, cookie use, security review and requests to access or change your personal data.

Yes. The Privacy Policy explains that DANA and QRIS references may be used to match payment status with your account. We do not need your wallet password to check a receipt.

Phone verification helps confirm that an account access request comes from you and supports security checks. We record the verification result and use it for the stated account protection purpose.

You can ask through account help for the personal data connected to your profile. Include your account contact detail and specify whether you want login, payment, cookie or verification records.

Send a correction request through the privacy contact path with the inaccurate field and the correct value. We may ask for phone verification before changing information that controls account access.

Cookies may retain session choices and help your mobile browser return to the correct account route. Clearing them removes that stored session context and can require you to sign in again.

Yes. Account access and eligibility depends on local law. Before providing personal data or using the account route, check whether access is available where you are located.

emas168 Privacy Policy for Your Account

Reach Us About Privacy Questions

How Your Account Data Stays Controlled

Account details

Cookies

Security signals

Payment records

Retention periods

Change requests

Privacy Policy Answers Before Account Access

01 What does the emas168 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 Why does emas168 ask for phone verification?

04 Can I request a copy of my account data?

05 How do I correct data in my Privacy Policy record?

06 How are cookies handled on a mobile browser?

07 Does account access depend on local law?

Related Pages