Reference

Open ug808 Privacy Policy Before Account Access

Our ug808 Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Account data explainedWallet records coveredCookie choices includedContact path available

Explore Our Lobby Read FAQ

Browse Privacy Policy Rules For DANA

ug808 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy sets out how we collect, use, store and share data connected with your ug808 account. That can include your phone number, verification result, sign-in records, device details, wallet selection and support messages. When you choose DANA, OVO, GoPay or QRIS, we record the

1
payment reference and status needed to match an account action; we do not need your wallet password. We may also keep security logs when you open the lobby from a phone or desktop browser. Access or eligibility depends on local law, and our handling of a
2
request can change when a legal, fraud-prevention or payment record must be retained. Before opening an account, check this page and the account prompts so you understand which fields are required. If you stop an application, some records may remain where a legal or security reason
3
applies.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Choose A Privacy Policy Support Path

A clear contact route helps you act on the Privacy Policy without guessing where a request belongs.

DATA PRACTICES

Explore How ug808 Handles Policy Requests

Our handling process follows the account activity you can recognise: phone verification before account access, a session record for the browser or device you use, and a payment reference when a wallet…

Account collection

We collect the phone number and verification result needed to create and protect your account. Required fields are shown during the account step, so you can see what is requested.

Cookie controls

Cookies can remember a session and help us understand sign-in errors. Your browser settings provide a way to clear or restrict them, although some account steps may then need repeating.

Device records

When you move from a mobile login to the lobby, we may record device type, browser details and security events. These records help us identify unusual access without reading private wallet credentials.

Account security

Phone verification confirms the account step before access. We may pause a session or request another check when sign-in behaviour changes, helping protect your account from unauthorised entry.

Retention period

We keep account, payment and security records only for the period needed for service, dispute handling, fraud checks or legal duties. Some records can remain after an account request is closed.

Change requests

You can ask us to correct eligible data, request a copy or ask about deletion through support. We verify the account holder first and explain any record that cannot yet be removed.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the account and wallet questions we expect from you before access. They cover what we collect, how you can request a change, why a verification step may appear and what happens when you use a phone browser in Indonesia. If your situation is not listed, send the account reference through the support path rather than sharing a password.

It covers account details, phone verification, browser and device records, cookies, payment references, support messages, retention and requests to access, correct or remove eligible data.

We use your phone number to create the account, complete the required verification step and help match an access request with the correct account. We do not ask for your wallet PIN.

Yes. When you use DANA or QRIS, we may keep the payment reference, selected rail and status needed to match the account action. Wallet passwords remain outside our requested fields.

You can request correction through the account support path. Tell us which record is wrong, provide the account phone number and complete identity checks before we amend eligible data.

Send a clear deletion request through support. We confirm that you control the account, then assess which records can be removed and which must remain for legal, payment or security reasons.

Retention depends on why the record exists. Payment references may remain for dispute handling, security checks or legal duties; the Privacy Policy explains why a requested removal may be limited.

Yes, access or eligibility depends on local law. The Privacy Policy applies to data handling for supported Indonesia access, and account prompts may request checks before you continue.

Open ug808 Privacy Policy Before Account Access

Choose A Privacy Policy Support Path

Explore How ug808 Handles Policy Requests

Account collection

Cookie controls

Device records

Account security

Retention period

Change requests

Check Privacy Policy Answers Before Joining

01 What does the ug808 Privacy Policy cover?

02 Why does ug808 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS data?

04 Can I ask ug808 to correct my account data?

05 How do I request deletion under this Privacy Policy?

06 How long does ug808 keep wallet records?

07 Does access to my account depend on local law?

Related Pages