Reference

ungu508 Privacy Policy For Your Account Data

Our Privacy Policy explains what data we collect when you create an account, verify your phone, open the mobile lobby, or use DANA and QRIS.

Clear data purposesWallet activity contextPhone verification details
ungu508 ungu508 Privacy Policy For Your Account Data
CONTACT PATHS

Get Privacy Help Without Guesswork

A direct support path helps you ask about the Privacy Policy, account records, or a wallet reference without posting personal details in a public channel. Start from the support route while signed in, describe the account step involved, and include only the reference needed for us to locate it. We can then check whether your request concerns login, phone verification, DANA status, or another privacy matter.

Team online

Policy questions

Send your Privacy Policy question through our support chat from the signed-in account path. We use the account context to discuss data access, correction requests, or the purpose of a device record.

Wallet references

If QRIS, OVO, or GoPay activity appears unfamiliar, share the relevant transaction reference through support rather than your wallet password. We check the account-side record and explain what data was used.

Login assistance

When phone verification or a mobile session blocks account access, contact support with your account identifier and device path. We avoid asking for wallet credentials while checking the privacy-related access record.

DATA CONTROL

What You Can Control In Your Privacy Policy

Your Privacy Policy choices are connected to practical account actions, not hidden behind broad wording.

Account data

We may hold your account identifier, phone verification result, login events, and support history.

Device signals

A mobile browser can provide session, device, language, and network signals used to keep a login consistent and detect unusual…

Cookies

Cookies and similar storage can remember a session, protect account steps, and measure page use.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, we keep matching details such as status and reference.

Account security

Phone verification, session checks, and restricted staff access help protect your account record.

Changes and requests

Ask us to correct, access, or clarify your data through the signed-in support path.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account steps you are most likely to take: phone verification, mobile access, wallet payments, and support contact. If your situation involves a local rule, our response depends on local law. Use the signed-in support path when your question includes private account or transaction details.

The ungu508 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use the phone verification result to connect account access to the correct person, protect login sessions, and handle recovery questions. We do not need your wallet password to check a payment reference.

Yes. It explains that we may receive a QRIS, DANA, OVO, or GoPay reference, status, amount, and timing so we can match the transaction request to your account and respond to support questions.

A mobile browser may provide session, device, language, and network signals. We use these details to maintain the correct login, identify unusual access, and protect the account path from the phone check to the lobby.

We keep each record for the account purpose, support need, service operation, or legal period that applies. The exact period can vary, and any local requirement depends on local law.

You can ask for access, correction, or clarification through the signed-in support route. We first confirm account ownership, then explain what can be changed and whether a required record must remain.

Open support chat from your signed-in account and describe the privacy concern. Include an account identifier or payment reference only when needed, and never send a wallet password or private security code.