Reference

Privacy Policy for Your redmiqq Account

Your phone verification, login record and selected wallet details are covered by the redmiqq Privacy Policy, so you can understand what we collect before opening an account.

Phone verificationWallet detailsPolicy requests
redmiqq Privacy Policy for Your redmiqq Account
REQUEST PATHS

Get Privacy Help Through Your Account

A clear account route helps you ask about personal data without sending sensitive details through random channels.

Account help Open the help area after login and identify the Privacy Policy request you need answered. Include your account phone number only through the secure account path, so we can locate the correct record without asking you to post private details publicly.
Wallet matching For DANA, OVO, GoPay or QRIS questions, share the transaction reference and time shown on your receipt. We use that pairing to check the relevant record, while avoiding requests for wallet passwords, one-time codes or unrelated account content.
Correction request If your name, phone detail or payment reference appears inaccurate, tell us which field needs attention through account support. We can explain the verification step, record the request and confirm what can be changed under applicable local requirements.
DATA HANDLING PRACTICE

How We Handle Login And Wallet Data

Privacy work is tied to practical account steps rather than broad promises. We use phone verification before account access, review device and login signals when protecting an account, and connect payment references…

Account access

Phone verification is used before account access so we can connect a login to the intended account. We may record verification status and related timestamps, then use them to answer access questions or investigate an unusual sign-in.

Device signals

A mobile browser or desktop session can create technical records such as device type, browser version, IP address and login time. These details help us protect account access and diagnose a session that stops before the lobby opens.

Cookies

Cookies and similar storage can remember a session choice, preserve security checks and measure which account page loaded correctly. You can clear or restrict them in browser settings, although some Privacy Policy request steps may then need another sign-in.

Wallet records

For QRIS, DANA, OVO, GoPay and bank transfer activity, we keep transaction references and status details needed for reconciliation. We do not ask for your wallet password, and we use the record to resolve the linked account question.

Retention

We retain account, security and payment records for the period needed for the stated service purpose or applicable legal requirement. When a retention period ends, records are deleted, anonymised or otherwise handled under the Privacy Policy process.

Your request

You can ask what eligible data we hold, request a correction or ask about deletion through the account help path. We may verify your identity first, and access or fulfilment depends on local law and the record involved.

Privacy Policy Questions For redmiqq Accounts

These Privacy Policy answers focus on the account details you are most likely to question before using redmiqq in Indonesia. They cover phone checks, mobile browsing, local wallets, correction requests and deletion. Where local law permits, we explain the practical route for making a request rather than leaving you to guess which account screen to use.

The redmiqq Privacy Policy covers account, phone verification, device, cookie, security and payment-reference data. It explains why we use each category, how retention works, what support can access, and how you can ask for a copy, correction or deletion where local law permits.

No. For DANA and QRIS activity, we use a transaction reference, time, amount and status to match the account record. We do not need your wallet password or one-time code to answer a Privacy Policy request or check a payment status.

Phone verification connects your sign-in to the intended account and helps us respond to access problems. We may retain verification status and timestamps for security and support. The Privacy Policy explains how that data is used, with eligibility depending on local law.

Yes, use the account help area and identify the field that appears wrong, such as a phone detail or payment reference. We may confirm your identity before changing it, then explain the result under the Privacy Policy and applicable local requirements.

The Privacy Policy covers cookies and browser storage used for session continuity, security checks and page operation. On your phone, you can clear or restrict storage in browser settings. Clearing it may require another login and can remove saved session choices.

We retain each record for the stated operational purpose or for an applicable legal period, depending on its category. Account, security and payment references may therefore have different periods. The Privacy Policy request path can explain the category relevant to your question.

Sign in, open account help and choose the data or Privacy Policy request path. Describe whether you want access, correction or deletion, and include only the reference needed to locate your record. We verify the request before responding, where local law permits.