Reference

mana777 Privacy Policy for Your Account

Our mana777 Privacy Policy explains what we collect when you open an account, sign in, browse Blackjack or check DANA and QRIS wallet status.

Account dataCookie choicesWallet recordsContact route
mana777 mana777 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Policy Help Clearly

A direct support path helps when you need to ask about the Privacy Policy, correct account details or understand a wallet record. Use the contact route shown beside your account and cashier area, and include the phone number linked to your account rather than sending a password. We use the smallest useful set of details to locate your request and explain the next step.

Team online

Account data request

Ask us to confirm the account details held for you, such as your phone number, sign-in record or verification status. We may ask for an account step before responding.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send its date and status through the available support route. Do not include your wallet PIN or full password.

Correction request

Tell us which account detail needs changing and why. We compare the request with your existing verification record before applying an amendment or explaining why local rules affect it.

HANDLING DETAILS

Six Ways We Handle Your Data

Our Privacy Policy is applied through practical account and device controls, not just a page of legal wording.

Account collection

When you create an account, we collect the details needed to identify the account and complete phone verification. You can check the submitted contact detail before moving into the lobby.

Device signals

The mobile or desktop route may provide browser, device and session signals. We use them to recognise unusual sign-ins, protect your account and troubleshoot access to the Privacy Policy page.

Cookie choices

Cookies can remember session settings and help us understand whether a page loads correctly. Your browser controls can remove or restrict them, although some account steps may then need repeating.

Payment references

A DANA, OVO, GoPay or QRIS record can connect a payment status to your account reference. Bank transfer and virtual account records are used for matching, receipts and status questions.

Security access

We use account checks before discussing private details and do not ask for your password or wallet PIN. Keep your phone verification details private when requesting help through the account route.

Retention and changes

We keep records only for the operational, security or legal reason that requires them, then remove or restrict them when appropriate. Contact us to request access, correction or deletion where local law permits.

Privacy Policy Answers for mana777

These Privacy Policy answers address the account questions you are most likely to have before opening an account or checking a wallet status. They explain the practical route for data access, corrections, cookies, payment references and account security, while recognising that some requests depend on local law.

It covers account details, phone verification, device and session signals, cookies, support requests, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and locate your account, complete the account access step and respond to private requests. We do not need your wallet PIN for this process.

Yes. Send an account data request through the available support route, using the phone number linked to your account. We may verify your identity before describing or supplying the relevant records.

State the detail that is wrong and the change you need through the contact route. We compare your request with the existing verification record before making an amendment where local law permits.

Yes. We may retain payment references, timestamps and statuses for DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity so we can match receipts and answer account questions.

Cookies and device signals can preserve a session, remember selected settings and help diagnose an account access issue. Browser controls can restrict them, but you may need to repeat some account steps.

Retention depends on why the record was created, including account security, payment matching, support history or legal need. Ask us about a specific record, and we will explain the available route.