Reference

EMAS27 Privacy Policy for Your Account

EMAS27 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Clear data purposesWallet activity explainedAccount contact path
EMAS27 EMAS27 Privacy Policy for Your Account
CONTACT PATHS

Privacy Questions Beside Your Account

A direct support route helps you ask about the Privacy Policy without explaining your concern repeatedly. Keep your account identifier and the relevant payment reference ready, but never send a wallet password or full security code. We can use the account support path to locate a request, check its status and explain what information is needed.

Team online

Account support

Use the support link connected to your EMAS27 account when you want to ask what data we hold, why it is needed or how the Privacy Policy applies to your login.

Wallet status help

For DANA, OVO, GoPay, QRIS, virtual account or bank transfer questions, include the transaction reference so we can separate payment matching from unrelated account details.

Change request

Ask us to correct an account detail through the same support path. We may request phone verification before changing personal data or discussing records linked to your account.

DATA HANDLING

What We Do With Your EMAS27 Data

We keep our privacy practice close to the account actions you recognise: signing in, confirming a phone, checking a wallet reference and contacting support.

Account details

We use your name, phone details and account credentials to create access, confirm ownership and respond to requests.

Device and session signals

Your browser, device type, login time and session signals can help us detect unusual access.

Cookies and storage

Essential cookies can keep sign-in and page choices working, while limited measurement data helps us identify broken paths.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us match account activity.

Security controls

We may compare phone verification, login history and device signals when an account action looks unusual.

Retention and requests

We keep records for the period needed to operate the account, resolve disputes and meet legal duties.

Privacy Policy Answers for EMAS27

These Privacy Policy answers address the account and payment questions we expect you to raise before opening an account. They explain the practical steps for data requests, wallet references, cookies and account security, while the full policy wording remains the reference for your situation.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains how we use those records to operate and protect your account.

We collect the details needed to create your account, confirm your phone and manage sign-in. We may also record device, session and support details connected with your account activity.

Yes. The Privacy Policy covers the payment references linked to DANA, OVO, GoPay and QRIS, plus virtual account and bank transfer records used to match activity with your account.

Use the account support path and state whether you want access or correction. Include your account identifier, avoid sending passwords, and complete phone verification if we need to confirm ownership.

You can send a deletion request through account support. We assess it against account operation, dispute handling and legal duties, so some records may need to remain for a required period.

Essential cookies may support sign-in and saved choices on your mobile browser. Other storage can help us understand broken page paths, and you can manage cookie settings through your device browser.

Some account actions and service availability depend on local law. We apply the Privacy Policy where local law permits and may ask for account or location details when a legal condition requires it.