Reference

ug300 Privacy Policy for Your Account Data

Our ug300 Privacy Policy explains what account data we collect, why we use it, and how you can ask about it before opening an account.

Clear data purposesWallet record contextRequest access or changesCookie choicesAccount security steps

Browse Our Lobby Read FAQ

How Wallet Data Sits Under This Policy

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

This Privacy Policy applies when you create an account, sign in, browse the lobby, contact support or use a payment route. We may receive details you submit, such as your name, phone number, login credentials and verification responses, along with device, browser and session data needed

1
to keep access working. When you select DANA, OVO, GoPay or QRIS, we record the payment reference, amount status and related account event rather than using those details for unrelated purposes. Bank transfer and virtual account records are handled in the same account context. We use
2
data to provide access, confirm account actions, investigate payment status and respond to privacy requests. We disclose it only where needed for service operations, legal duties or payment processing. Retention depends on the record and applicable law. Account access depends on local law, and you can
3
ask support for the current policy wording that applies to your request.

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

HELP DESK ROUTE

Where To Send A Privacy Request

A clear support route helps you ask about a record without repeating your account history.

Account access Sign in through your usual mobile browser or desktop path, then send the request from the account support area so we can match it to your ug300 profile.

Wallet status For DANA, OVO, GoPay, QRIS or bank transfer records, include the visible reference and status so our support route can separate a payment query from a data request.

Privacy changes Ask us to correct, access or clarify your stored data through the same support path. We will explain any identity check needed before making an account change.

ACCOUNT SAFEGUARDS

Six Controls Behind Your Account Data

We keep this policy practical by linking each data use to an account action you recognise, from phone verification to a QRIS status check.

Data collection

We collect details you provide during account creation and support contact, plus device and session signals needed to sign you in and display the correct account state.

Cookie choices

Cookies can keep your session active and remember selected settings in a mobile browser. You can adjust browser cookie controls, though some account steps may then need repeating.

Account security

Phone verification before account access helps us connect a request to the correct person. Never send a password or one-time code inside a support message.

Payment records

A DANA, OVO, GoPay or QRIS event may remain linked to your account reference and status so we can trace a disputed or incomplete cashier action.

Retention

We retain records for the period needed for account operation, dispute handling, security checks or legal duties. You can ask support which basis applies to a record.

Your request

You may ask us to access, correct or clarify personal data through the account support route. We may verify your identity before sharing or changing it.

Privacy Policy Answers For ug300 Accounts

These Privacy Policy answers focus on the questions you may have before creating an account or sending a data request. We keep the examples close to real account actions, including phone verification, browser cookies and local wallet references.

It covers account details, phone verification, device and session data, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to support account identification and the verification step before access. This helps us respond to the correct account when you ask about data or wallet status.

Yes. The policy covers the account reference, payment status and related event for QRIS, DANA, OVO and GoPay. It does not treat a wallet record as permission for unrelated use.

Sign in where possible and use the support path attached to your account. State that you want access to your personal data, and include only the account details needed to locate your request.

Yes. Send a correction request through account support and identify the inaccurate field. We may ask for phone verification or another account check before changing a record.

Cookies can preserve a session and selected settings in your mobile browser. If you block or clear them, login or account steps may need to be completed again.

The policy is provided for your account questions, while service access and eligibility depend on local law. If you are in Indonesia, ask support which request route applies to your account.

ug300 Privacy Policy for Your Account Data

Where To Send A Privacy Request

Six Controls Behind Your Account Data

Data collection

Cookie choices

Account security

Payment records

Retention

Your request

Privacy Policy Answers For ug300 Accounts

01 What does the ug300 Privacy Policy cover?

02 Why does ug300 need my phone number?

03 Does the Privacy Policy cover QRIS and wallet records?

04 How can I request a copy of my data?

05 Can I ask ug300 to correct account data?

06 How do cookies affect my mobile access?

07 Does access to this Privacy Policy depend on local law?

Related Pages