Reference

pubg77 Privacy Policy for Your Account

pubg77 Privacy Policy sets out what we collect, why we use it, and how you can request access or changes to your account data.

Clear data purposesWallet record contextPhone verificationRequest support access
pubg77 pubg77 Privacy Policy for Your Account
PRIVACY HELP

Three Ways to Ask About Your Data

A clear request path matters when a phone number, login record or wallet reference needs checking. We ask you to contact us from the account linked to the request whenever possible, because that lets us compare the request with the account step already recorded. Do not send a password or full payment credentials. For a request involving DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include only the visible reference and the approximate date.

Team online

Account privacy request

Open the account support path and state whether you want a copy, correction or deletion review. We use the signed-in account and phone verification record to confirm that the request concerns your details before we act.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the visible transaction code and date through account support. We compare it with the stored wallet event without asking for your PIN, password or full card details.

Access and law query

For questions about regional access, device records or a request made where local law permits, describe the exact screen or account step. We explain what data is relevant and whether the request depends on local law.

DATA PRACTICE

Six Privacy Controls Behind Your Login

We handle this Privacy Policy area through practical controls rather than broad promises. Account data is separated from payment references where the process allows, cookies support sign-in and page settings, and access…

Data collected

We may receive your phone number, account credentials, verification result, support messages, device details and session events. Wallet references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account may be linked to an account action.

Cookie choices

Cookies can keep a signed-in session, remember selected settings and help us identify repeated access errors. You can manage browser cookie controls, although switching them off may require another login or limit a saved account preference.

Account protection

Phone verification is checked before account access, and we use sign-in events to identify unusual changes. We do not ask you to disclose a password or wallet PIN when you contact us about Privacy Policy matters.

Payment references

We use a payment reference to reconcile an account event, receipt or wallet status, not to request unrestricted access to your DANA, OVO, GoPay or QRIS account. Keep sensitive wallet credentials outside every support message.

Retention periods

We retain account, support and transaction-related records for as long as needed for service administration, dispute handling, fraud checks or legal duties. When a record is no longer needed, we remove it or restrict its use.

Your requests

You may ask what personal data we hold, request a correction, ask about deletion or question a processing purpose. We may verify your account first, and the outcome can depend on local law and required record keeping.

Privacy Policy Answers for pubg77

These Privacy Policy questions focus on the account situations you are most likely to meet in Indonesia: opening access, checking a wallet reference, changing personal details and asking what remains stored. We keep the answers tied to actual account steps, including phone verification, browser cookies and support requests. Where local law permits, we will explain the available route clearly rather than asking for data that is not needed.

It covers account details, phone verification, sign-in events, device and browser data, cookies, support messages and payment references. It also explains how we use those records, how long they may remain, and how you can request access, correction or deletion.

No. Our Privacy Policy does not require you to send a wallet PIN or password to support. We may retain a visible payment reference, amount status or date needed to match an account event, while the wallet credential stays with your payment provider.

Phone verification helps connect account access with the person making the request and helps us investigate unusual sign-in changes. It can also be used when you ask to correct or remove data, because we need a reasonable way to check account ownership.

Yes, you can request a copy through the account support path. State that your request concerns the Privacy Policy and identify the account email or phone number. We may verify ownership first, then explain which records can be supplied under local law.

Send a correction request from the linked account and describe the field that is wrong. For a DANA, OVO, GoPay or QRIS record, include only the visible reference and date. We compare the request with our account event before changing a stored detail.

Use account support to request deletion and specify the data you want considered. We first verify the account, then assess whether operational, dispute or legal records must remain. The result depends on local law and any required retention period.

Some cookies support sign-in continuity, saved settings and diagnosis of access errors. You can adjust cookie controls in your browser, but disabling them may end a session or require phone verification and a fresh login the next time you open the account.