Reference

Privacy Policy for Your ups99 Account

Our ups99 Privacy Policy shows what account details we collect, why we use them, and how you can ask about a change.

Clear data purposesCookie choicesAccount access rightsWallet record clarity
Explore Our Lobby Read FAQ
ups99 Privacy Policy for Your ups99 Account
CONTACT ROUTES

Where To Ask About Privacy

A direct account route gives you one place to raise a Privacy Policy question without sending personal details through an unrelated channel. Sign in, open the support path beside the cashier area, and include the email or phone number attached to your account plus the exact request. For a wallet question, add the DANA, OVO, GoPay or QRIS reference with sensitive digits hidden. We use the details you provide to locate the relevant record and reply through the account contact route.

Team online

Account support path

Use the support route after sign-in for access, correction or deletion requests. Include your account contact detail and describe the Privacy Policy issue clearly so we can locate the correct record without asking you to post it publicly.

Cashier record query

For a wallet record question, mention whether it concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Share the transaction reference with private digits hidden, allowing our team to check status without exposing unnecessary data.

Access clarification

If a sign-in or phone verification step blocks your privacy request, tell us the device path you used, such as mobile browser or desktop browser. We can explain the next account step while keeping access dependent on local law.

DATA CONTROLS

Six Controls Behind This Policy

Privacy is handled through practical controls rather than a single statement on a page. We separate account authentication from ordinary browsing signals, restrict wallet references to the checks they support, and use…

Account data

We may hold your name, contact detail, phone verification result and sign-in history so we can connect an account request to the right person. We use those fields for access, support and account record accuracy, not as decoration on a profile.

Device signals

Browser type, device identifiers and session signals can help us spot an unusual login or explain why a mobile browser session changed. We review these details for account protection and troubleshooting, then keep them only as long as the purpose requires.

Wallet references

A DANA, OVO, GoPay or QRIS reference can appear in account records when we match a cashier status. Bank transfer and virtual account references serve the same check. We do not need the full private credential to investigate a status.

Cookies

Cookies can preserve your sign-in session, remember a selected page setting and show us whether a page loads correctly. Your browser provides controls to remove or restrict them. Limiting cookies may require you to sign in again on the mobile path.

Retention

We keep each category for the time needed to provide account access, resolve a record question, prevent misuse or meet a legal requirement. When the purpose ends, the record is deleted, anonymised or placed beyond routine account use.

Your request

You can ask what personal data we hold, request a correction, ask about deletion or question a processing purpose through the account support route. We may verify your account contact detail first so another person cannot change your record.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening access. They cover data collection, mobile browser use, cookies, payment references, correction requests and the local-law boundary. If your situation is not covered, use the signed-in support route and identify the account step or record that needs attention.

It covers personal data connected with your account, including contact details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It also explains why we use each category, how retention works and how you can ask for access or correction.

Phone verification helps us connect an account request to the correct person before access is provided. It can also help us investigate a sign-in concern. We record the verification result and related account details for those purposes, subject to access where local law permits.

Yes. The policy covers transaction references and wallet status details linked to DANA, OVO, GoPay and QRIS. It also covers bank transfer and virtual account references. We use these records to match a status to your account and respond to a cashier query.

A mobile browser session may create sign-in, device, cookie and page-use records. We use them to keep your account session working, investigate unusual access and fix loading issues. Restricting cookies can end the session or require another sign-in, while the same policy still applies.

You can request access, correction or deletion through the account support path. We first confirm the account contact detail, then explain what can be changed. Some records may need to remain for account protection, dispute handling or a legal requirement where local law permits.

Retention depends on the purpose of the record. We keep account, support and payment references for as long as needed to provide access, check a status, prevent misuse or meet a legal requirement. After that, we delete, anonymise or remove them from routine account use.

Sign in and use the support route beside the cashier area. State that your request concerns the Privacy Policy, identify the account contact detail and describe the record or purpose involved. For DANA, OVO, GoPay or QRIS queries, include a reference with private digits hidden.

Related Pages

ups99 Indonesia playbola88 agenjp Access guide Super Sic Bo