Reference

emas77 Legal Rules for Your Account

emas77 Legal sets out how we handle account access, identity checks, wallet records and policy requests for Indonesia.

Account accessPrivacy requestsWallet recordsPolicy contact
emas77 emas77 Legal Rules for Your Account
POLICY HELP ROUTES

Legal Help for Wallet Status Questions

A clear support route matters when a Legal question affects your account or wallet status.

Account access Use the account support path when phone verification, sign-in details or an access decision needs a Legal explanation. Include your registered phone number so we can locate the right account record.
Wallet status For DANA, OVO, GoPay or QRIS questions, share the payment name and reference shown in your account. We can then check whether the issue concerns a wallet record or a policy condition.
Policy request Ask through the policy contact route when you need a copy, correction or clarification concerning your Legal records. We may verify account ownership before discussing private account details.
DATA HANDLING DETAILS

How emas77 Handles Legal Records

We keep our Legal process practical: identify the account, check the relevant event, and respond through the account contact route.

Data use

We use account details, phone verification results and transaction references to handle Legal requests, check ownership and explain an account decision. We do not ask for unrelated personal details during a standard policy enquiry.

Cookie choices

Cookies may help keep your account path working between pages and remember technical preferences. You can ask our policy contact route what cookie data relates to your access and request clarification about its use.

Account security

Phone verification helps us distinguish the account holder from an unauthorised requester. Keep your sign-in details private, and contact us through the account path if you notice an access or profile change you did not make.

Record retention

We retain Legal and wallet records for the period needed to handle account checks, resolve disputes and meet applicable obligations. A retention question should include your registered phone number and the record you want identified.

Correction requests

If an account detail is inaccurate, send a correction request through the policy contact route. We may ask for phone verification before changing the record, especially when the change affects wallet or access history.

Who to contact

Our account support route handles Legal questions about access, privacy, cookies, retention and wallet records. Please name the issue clearly and attach only the reference needed for us to locate it.

Legal Answers Before Account Access

These Legal answers cover the questions we expect you to ask before opening an account or sending a policy request. They explain the access condition, the records we may check, and the practical route for correcting or questioning account data.

emas77 Legal covers account access, phone verification, privacy requests, cookies, record retention and wallet references. Access depends on local law, so you should confirm eligibility for your location before continuing.

Yes. Access depends on local law, and where local law permits, you may open and use an account after completing the required account steps. We cannot replace advice from your local authority.

Phone verification helps us confirm that the person requesting access or a record change controls the account contact. It can also protect DANA, OVO, GoPay and QRIS references from unauthorised changes.

Use the policy contact route shown in your account and identify the record you need, such as an access decision or wallet reference. We may verify ownership before releasing private account details.

You can send a correction request through the account support path. State which detail is wrong and what it should say; phone verification may be required before we change an account or payment record.

Cookies may support sign-in continuity and technical preferences. For a Legal question about cookie use, contact us through the policy route and identify the device path or account page involved.

Use the account support route and include the payment rail, date and reference visible in your account. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account matters, we check the matching record.