Reference

Privacy Policy for Your minion Account

minion Privacy Policy explains how we collect, use and protect the account details needed to move you from phone verification into the lobby.

Clear data purposesWallet activity contextCookie choicesAccount access controls
minion Privacy Policy for Your minion Account
CONTACT PATHS

Where Privacy Policy Questions Reach Our Team

A clear contact path helps when you want to ask about a Privacy Policy record, correct an account detail or understand a wallet reference. Start from the support route connected to your account so we can match the request with your verified phone and avoid sending private details through an unverified conversation. Include the account step or receipt reference that caused the question, and we will use the details available to us to check the matter. Requests remain subject to identity checks and applicable law.

Team online

Account privacy request

Use the support path connected to your minion account when you want to ask what account data we hold, why a phone verification record appears, or how to request a correction. We may ask for account checks before discussing private details.

Wallet record query

For a DANA, OVO, GoPay or QRIS reference, share the relevant receipt or status detail through the account support route. We use that reference to separate your transaction record from another account and limit unnecessary disclosure.

Access concern

If login or account access stalls, tell us which device path you used and whether the issue appeared before or after phone verification. We check sign-in signals and account status without asking you to send a password or security code.

DATA PRACTICES

How minion Handles Account Data Safely

Privacy Policy work is tied to ordinary account operations rather than broad collection for its own sake.

Account details

We collect details you provide during account opening and phone verification, such as contact and access data.

Device signals

Your phone or computer can send browser, device and sign-in signals when you access the lobby.

Cookies

Cookies and similar storage can remember session settings, support account access and show whether a page request is working.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be linked to an account action.

Security steps

Phone verification, sign-in checks and limited internal access help protect account records.

Retention and changes

We retain account and transaction records for operational or legal needs, then remove or anonymise them when retention is no…

Privacy Policy Answers for minion Accounts

These Privacy Policy answers address the account questions you are most likely to have before or after phone verification. They explain what we collect, how wallet references and device access fit into the record, and how to ask for a correction or access request. If your situation is specific, use the account-linked support path and include only the details needed to locate your request.

The minion Privacy Policy covers account opening, phone verification, sign-in activity, device signals, cookies, support requests and transaction references. It also explains how we use these records for access, account security, wallet status checks and legal duties, with access depending on local law.

We collect the details you submit for account creation and phone verification, together with sign-in, device and browser signals generated during access. We may also keep support and transaction references so we can connect a DANA, OVO, GoPay or QRIS question to your account.

The Privacy Policy allows us to use a DANA or QRIS reference to match a payment status or support request with the correct account. The relevant payment provider may separately process transaction data under its own terms, and we do not treat its records as ours.

Yes, you can send an access or correction request through the support path connected to your account. We may verify your phone or ask for a receipt reference before responding, so private account details are not disclosed to someone who cannot establish account control.

Device and cookie data help keep a login session working, remember relevant settings and identify unusual access around your account. Browser controls can limit cookies, but disabling storage may affect phone verification, sign-in continuity or the way the Privacy Policy page functions.

We keep account, support and wallet-reference records for as long as they are needed for account operations, security checks or legal duties. When a record is no longer required, we remove it or change it so it no longer identifies you where practical.

Where local law permits, you can ask us to close the account and request removal of data that we no longer need. Some records may remain for security, dispute handling or legal duties. Send the request through your account-linked support route for an account check.