Reference

psg77 Privacy Policy for Your Wallet Data

Your account details, DANA status, QRIS records and device settings stay covered by one clear Privacy Policy.

Clear data purposesWallet record controlsMobile cookie choicesDirect request path
psg77 psg77 Privacy Policy for Your Wallet Data
HELP WITH REQUESTS

Get A Clear Policy Contact Route

A privacy question should not be mixed with a game or cashier query. We route requests through the support contact shown inside your signed-in account, where you can identify the relevant phone number, wallet reference or device session. If you are in Bandung and cannot sign in, use the contact route displayed on the access page and include only the details needed to locate your request.

Team online

Account access

Use the support link shown before login when phone verification blocks your account. We ask for enough account detail to locate the record, while avoiding requests for your wallet password or full payment credentials.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy request, send the payment reference visible on your receipt. We use that reference to find the matching record without asking you to disclose a wallet PIN.

Data changes

The signed-in support route lets you ask for a correction, access copy or deletion check. We may verify phone ownership first so a data request cannot be submitted against another account.

CONTROLLED DATA USE

Keep Control Of Account Data

We handle Privacy Policy requests as account tasks, not as general lobby messages. Our process links the request to your verified account, checks the relevant device or payment reference, and records the…

Account details

We use your phone number and verification result to create, secure and locate your account. Profile fields are not treated as a reason to collect unrelated personal details from your device or wallet.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are matched through references, amounts and status data. We do not ask for wallet passwords, card PINs or private wallet login codes.

Cookies and sessions

On mobile and desktop browsers, cookies can remember your consent choice and session state. You can clear them through browser settings, although clearing session cookies may sign you out before a policy request is sent.

Account security

Phone verification, session checks and device signals help us identify unusual sign-in activity. If a login looks unfamiliar, we may pause a request until account ownership is confirmed through the support route.

Retention periods

We retain account, payment and support records only while they serve the stated purpose or a period required where local law permits. When the period ends, records are removed or separated from direct account identifiers.

Your requests

You can ask to see, correct or delete personal data through account support. Include the request type and matching account detail; we will explain any identity check or legal reason that affects the outcome.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. Each response points you toward the relevant account step, browser control or support route, with access depending on local law.

It covers account details, phone verification, device sessions, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create and locate the account, complete the required verification step and check ownership when you request access, correction or deletion of personal data.

Yes. The Privacy Policy includes DANA and QRIS reference data, status and receipt details used to match a transaction. It does not require your wallet password or private PIN.

Our mobile pages may store cookies for consent and session continuity. You can clear them in your browser settings, but doing so may end the session and require phone verification again.

Yes. Send an access or correction request through the support route inside your account, or the pre-login contact path if you cannot sign in. We may confirm account ownership first.

We keep payment references and status records only for the stated matching, security or support purpose, or for a period required where local law permits. Unneeded records are removed or separated.

The policy page can be read from supported regions, but account access and eligibility depend on local law. If a regional rule affects your request, support will explain the applicable step.