Reference

UNTUNG28 Privacy Policy Explained

UNTUNG28 Privacy Policy sets out how we collect, use and protect details linked to your account, device and wallet activity.

Account dataWallet recordsDevice controlsContact choices
UNTUNG28 UNTUNG28 Privacy Policy Explained
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact path helps you ask about a record without explaining your whole account history. Use the support route shown after login and identify the account email or phone detail connected to your request; do not send a wallet password or one-time code. We can help trace a DANA, QRIS or bank transfer reference when your question concerns stored payment data.

Team online

Account privacy request

Ask us to locate, correct or explain personal details held for your account. Include the email or phone detail used during account creation so we can check the right record.

Wallet record question

For DANA, OVO, GoPay or QRIS references, send the transaction date and visible reference only. We use those details to find the relevant record without requesting your wallet password.

Access concern

If a device or login check blocks your privacy request, tell us the device path and account identifier. We may ask for another account step before disclosing personal details.

HANDLING DETAILS

How We Manage Your Account Data

We treat account details as part of the access and payment record, not as material for unrelated use.

Data collected

We may collect your account contact details, verification responses, device information, session events and payment references. These fields help us provide access, investigate wallet status and respond to privacy requests.

Cookie use

Cookies can keep your session connected while you move from login to the lobby. Browser controls let you remove or restrict them, but a later account check may ask you to sign in again.

Account security

We use sign-in checks, device signals and verification steps before changing sensitive account details. Never share a password or one-time code when asking us about Privacy Policy rights.

Retention period

We keep records only as long as needed for account support, security review, payment reconciliation or legal duties. When a record no longer serves those purposes, our handling process can remove or separate it.

Correction request

You can ask us to correct inaccurate account details through the support path shown after login. We may compare the request with your account step before applying a change.

Third-party handling

A payment or technical service may process a reference when its task requires it, such as matching QRIS activity. We limit the shared detail to that task and address questions through our support route.

Privacy Policy Questions Answered

These Privacy Policy answers focus on the account, device and payment questions you may search before opening access. If your situation needs a record check, use the support path after login and include only the details needed to identify your account.

It covers account details, verification responses, device signals, cookies, wallet references and support records. It also explains why we use each category, how long records may remain and how to request a change.

We mention DANA and QRIS because payment references can connect a wallet event with your account. We use the reference to check status or reconcile a record, not to request your wallet password.

Yes. Send a correction request through the account support path shown after login, using the email or phone detail attached to your account. We may complete an account check before changing sensitive fields.

Cookies can maintain your session while you move between account access and the lobby. You can restrict them in browser settings, but doing so may end the session or trigger another login check.

We retain wallet references for the period needed for support, payment reconciliation, security checks or legal duties. The period can differ by record type, and we remove or separate records when those needs end.

Yes. The policy applies when you use a mobile browser, including device signals, session cookies and account steps used for access. We handle those details for the same stated account and security purposes.

You can ask through the support path shown after login. State that your request concerns Privacy Policy data and identify your account; we may verify ownership before explaining or providing eligible records.