Reference

emas36 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an emas36 account, verify your phone and move between the lobby and cashier.

Account dataCookie choicesPayment recordsPolicy requests
emas36 emas36 Privacy Policy For Your Account
ASK OUR ACCOUNT TEAM

Reach Support About Privacy Questions

A clear support route helps when you want to understand a data field, correct an account detail or ask why a wallet status appears in your records.

Account data request Ask us to identify the account details connected with your phone verification or sign-in record. Use the account help route beside the cashier path, and include enough detail for us to distinguish your request from another account.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact support through account help before sending another transaction. We can check the recorded status and explain what information is retained for matching and security.
Correction or removal You can ask us to correct inaccurate personal details or explain whether a record can be removed. We may first confirm your phone verification so a change request does not expose or alter another account.
HOW WE HANDLE RECORDS

Browse How We Handle Your Data

Our handling process is tied to practical account events rather than broad collection for its own sake.

Account creation

When you open an account, we use the details you submit to create your profile and support the phone verification step before access. Please provide accurate information so a later correction request can be handled against the right record.

Device and session signals

A browser or mobile device can produce sign-in, session and security signals. These details help us investigate access to your account, including a switch from a mobile lobby to a desktop session, without treating device data as your identity alone.

Cookie controls

Cookies may remember selected settings and support the account session. You can manage browser cookie controls on your device, although changing them may affect how the Privacy Policy prompt, login state or page preferences appear.

Payment matching

A cashier record can contain a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We use that reference to check status and connect the transaction with the correct account, not to request your wallet password.

Retention periods

We retain account, security and transaction records only as long as needed for the stated service, dispute handling, security checks or applicable legal duties. You can ask what remains connected to your account and why a record is still held.

Policy change requests

For a copy, correction, clarification or concern about this Privacy Policy, use account support and identify the email or phone detail on file. We may verify ownership before discussing personal data or applying a requested change.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the questions you may have before opening an emas36 account or returning from a mobile device. They explain the account step, local wallet references, cookies, retention and the route for asking us to change or clarify personal data. If your situation is not covered, contact support through the account help path and we will direct the request to the right record.

The emas36 Privacy Policy covers account creation, phone verification, sign-in and device signals, cookies, payment references and support requests. It explains why we use each category, when it may be retained and how you can ask for access, correction or clarification.

We collect the details you submit for account creation, the result of your phone verification and records needed to maintain account access. Browser or mobile session signals may also be recorded for security. The policy explains each purpose before you proceed.

Yes. The Privacy Policy covers references created when you use DANA, OVO, GoPay or QRIS, along with bank transfer and virtual account records. These references help us match a cashier action, check status and resolve a payment question.

Use the account help route beside the cashier path and identify the phone or email connected with your account. Ask for a copy, correction or explanation. We may confirm ownership through the account step before discussing personal records.

Cookies can remember a session, policy choice or page setting in your browser. You can adjust cookie controls in your browser or mobile-device settings. Some changes may affect login state or how the Privacy Policy prompt is displayed.

We keep account, security and payment records for the period needed for service operation, dispute handling, security checks or legal duties. The exact period can depend on the record. Ask support which data remains connected to your account and why.

Access or eligibility depends on local law. If you are connecting from Indonesia, read the current Privacy Policy and the access notice shown for your account. We can explain how a location-related question affects your data request, but we cannot change local requirements.