Reference

mantra62 Privacy Policy For Your Account

Your account details, wallet choices and device settings receive a clear explanation here, so you can decide what to share before opening the lobby.

Account dataWallet contextCookie choicesSecurity requests
Explore Our Lobby Read FAQ
mantra62 mantra62 Privacy Policy For Your Account
CONTACT OPTIONS

Three Ways To Ask About Privacy

A direct question should not require you to search through unrelated pages. Our privacy support path begins inside your signed-in account, where you can identify the account email or phone detail connected to your request. Include a payment reference when your question concerns DANA, OVO, GoPay or QRIS, and we can separate wallet status from personal-data questions. We answer requests through the contact route shown in the account area and may ask for an account step to confirm identity.

Team online

Account contact route

Open the support contact shown after login and state whether your request concerns access, correction, deletion or a wallet reference. We use the account detail already connected to your request to reduce mistaken changes and may ask you to confirm one account step.

Payment privacy check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the relevant reference without sending a wallet password. We use that reference to locate the transaction record and explain which payment details are retained for account matching.

Login access request

If a privacy request starts with a stalled login, tell us the device path you used, such as mobile browser or desktop browser. We can separate an access problem from a data request while protecting the account from an unverified change.

HANDLING DETAILS

Six Practical Privacy Controls We Apply

We handle this policy area through specific account and transaction steps rather than a single broad permission. Account creation, phone verification and sign-in events create records that help us maintain access.

Account creation

When you open an account, we use the details you submit to create your profile and provide access to the account area. Phone verification may be required before access, and the submitted contact detail remains connected to account messages and security checks.

Phone verification

A phone verification step helps us confirm that an access request belongs to you rather than someone using a copied sign-in detail. We record the verification result and related time or device signal so an account change can be investigated.

Wallet references

DANA, OVO, GoPay and QRIS can provide a reference or status needed to match a payment with your account. Bank transfer and virtual account records serve the same reconciliation purpose; we do not ask for your wallet password.

Device signals

A mobile browser or desktop browser can send technical signals such as browser type, session time and access pattern. We use these signals to protect sign-in activity and investigate unusual account behaviour, not to read private content on your device.

Cookie choices

Cookies can keep a selected setting, support an active session or help us understand which policy page is being opened. Your browser controls can restrict cookies, although changing them may affect sign-in continuity or the way account pages load.

Retention and changes

We keep records for as long as they serve account access, payment reconciliation, security or legal needs. To request a correction, copy or deletion where available, contact us through the account route and describe the exact detail you want changed.

Privacy Policy Answers For mantra62

These Privacy Policy answers focus on the questions you may have before creating an account or sending a wallet payment. We keep each answer tied to a concrete account, device or payment step, so you know what to prepare when contacting us. If a local rule affects access, eligibility or a request, the relevant condition depends on local law and where local law permits.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references and requests about stored data. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match activity with your account.

We use your phone detail to create or maintain account access and to support a verification step before certain account actions. The verification result helps us distinguish your request from an unverified login attempt or a request made by another person.

No. Payment handling may use a reference, amount, status or matching detail supplied for the transaction, but we do not ask for your DANA, OVO, GoPay or QRIS wallet password. Bank transfer and virtual account matching follows the same account-reconciliation purpose.

Use the support contact displayed inside your account, identify the exact record involved and state whether you want access or correction. We may ask you to complete phone verification or another account step before discussing details or applying a change.

On a mobile browser, cookies can keep your selected setting, maintain a session and show which policy page was opened. Browser controls can restrict them, but sign-in continuity or account-page loading may change. We do not treat cookies as access to private device content.

Retention depends on why the record exists. Account, security and payment-reconciliation records may remain while they support access, investigation or legal needs. You can ask us which category applies to a detail and request a change where local law permits.

Yes. Use the contact route shown for account support and explain that the request concerns privacy as well as login access. Include your account identifier and device path, but never send a wallet password. We may verify ownership before discussing stored information.

Related Pages

mantra62 Indonesia Sugar Rush Dragon Tiger FAQ Register