Reference

Privacy Policy For Your mantap 21 Account

Our Privacy Policy explains how we collect, use and protect details linked to your mantap 21 account, including phone verification, login activity and DANA or QRIS payment records.

Account clarityWallet recordsPolicy access
mantap 21 Privacy Policy For Your mantap 21 Account
CONTACT ROUTE

Get Privacy Policy Help From Support

A clear support path helps when you want to ask about personal data rather than a game or wallet status.

Policy questions Send support a focused question about the Privacy Policy, such as what account detail…
Data correction If your contact detail or account record needs correction, ask us through the account…
Receipt checks For a privacy question tied to a wallet record, provide the date, amount shown…
HANDLING DETAILS

How We Handle Your Account Data

Our Privacy Policy is applied to the practical steps you take on the site, not only to a form of words.

Account details

We may collect your phone number, contact details and verification status when you open or use an account. These details help us identify your account, complete the requested access step and respond to a Privacy Policy request. We do not need your password in a support message.

Device signals

When you use a phone or desktop browser, we may receive technical signals such as browser type, device settings, approximate connection details and sign-in time. We use these signals to maintain the session, investigate unusual access and understand which policy notice was shown.

Cookies

Cookies can remember a session, support essential page functions and retain a preference related to policy notices. You can manage browser cookie settings, although blocking required cookies may affect login or the display of account pages. The Privacy Policy explains this use in context.

Payment references

We may retain a reference for DANA, QRIS, GoPay, OVO, bank transfer or virtual account activity rather than the full credentials held by your payment provider. A receipt reference and timestamp can help us answer a data request or check why an account record appears.

Account security

Phone verification before account access helps connect a request to the correct account. We may ask for additional confirmation when you request a data change, access a sensitive record or report an unfamiliar login. Never place a one-time code or password in a support message.

Retention requests

We keep records only for the period needed for the stated account, security, support or legal purpose, subject to local requirements. Ask support about deletion, correction or access for a specific record; we will explain any identity check, limitation or remaining retention need.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and data questions we hear before access begins. They explain what to prepare, how payment references fit into a request and how to reach us without exposing sensitive credentials. If your situation is not covered, contact support with the smallest useful set of details and remember that access depends on local law.

The mantap 21 Privacy Policy explains how we handle account details, phone verification, device signals, cookies, support messages and payment references. It also describes security checks, retention and requests for access or correction, with availability handled where local law permits.

We may collect contact and phone details, verification status, sign-in timestamps, device signals and information you provide to support. We may also hold references for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity connected with your account.

Contact account support and state that your request concerns the Privacy Policy and a copy of your account data. Include your registered contact detail and the relevant period or record. We may confirm ownership before responding, and local law can affect the response.

Yes, you can ask us to correct an inaccurate account detail by using the support path. Describe the old and requested new value without sending a password or one-time code. We may require phone verification or another account step before making the change.

It covers the account-linked references we receive for QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity. These can include a reference, status and timestamp. We do not ask you to send full wallet credentials when you request a policy check.

Cookies can support the login session, essential page functions and policy preferences on your phone or desktop browser. You can adjust browser settings, but blocking required cookies may affect account access. The Privacy Policy explains which cookie use supports the requested page function.

Retention depends on the record, its account or security purpose and applicable local requirements. We may keep a payment reference or support history when it remains needed for that purpose. Ask support about a specific item, and we will explain the available request path.