Reference

Open mainzeus Privacy Policy Clearly

mainzeus Privacy Policy explains what we collect when you create an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPolicy requests
mainzeus Open mainzeus Privacy Policy Clearly
CONTACT PATHS

Open Support For Privacy Requests

When a privacy question affects your account, we give you a direct route rather than sending you through unrelated lobby pages.

Account request Use the signed-in support path when you want to access or correct account details.
Wallet record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, tell us the…
Device question If a phone or desktop session looks unfamiliar, contact us through account support and…
DATA PRACTICES

Explore How We Handle Your Data

The Privacy Policy is designed around the points where your data is actually used: account access, wallet checks, device security and support requests.

Account collection

We collect details you enter during account creation and phone verification, then use them to provide account access, respond to requests and protect the sign-in path from misuse.

Cookie controls

Cookies and similar device storage can remember session choices and help us understand sign-in performance. You can manage browser permissions, although some account functions may then need another sign-in.

Security signals

We may record device type, browser details, sign-in time and session activity to detect unusual access. These signals support account security and are not a substitute for your phone verification.

Wallet handling

Payment references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity help us reconcile account status. We use the payment detail for the stated wallet and support purpose.

Retention periods

We keep personal data for the period needed for the purpose stated in this policy, account security, dispute handling or legal duties. When it is no longer needed, our process addresses removal or restriction.

Change requests

Ask us to access, correct, restrict or delete eligible personal data through signed-in support. We may verify your account first, and the result depends on local law and the record involved.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. We explain account data, device records, cookies, payment references and requests in plain terms. If your situation is different, use the support path after sign-in and include the account step or payment reference connected with your question.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account request to you and supports sign-in security. We use the related detail for account access, protection and support handling, subject to the purposes in this Privacy Policy.

Yes. The Privacy Policy explains that device type, browser details, session activity and sign-in timing may be recorded to identify unusual access. These signals help us protect your account on mobile or desktop.

We can use DANA and QRIS references to check account wallet status and answer a support request. The Privacy Policy limits that handling to stated operational, security and legal purposes.

Yes, where local law permits. Send an access or correction request through signed-in support, name the account field involved, and complete any account verification needed before we process it.

Use the account support path and request removal of the specific data. We assess the request against security, dispute and legal retention needs, so the outcome depends on local law and the record.

You can adjust cookie permissions in your browser settings. Some session or account functions may require another sign-in after a change, as explained in the Privacy Policy.