Reference

pisingyok Privacy Policy for Your Account Data

Our Privacy Policy gives you a clear view of how we handle account details, wallet records and device access before you open the lobby.

Account dataWallet recordsCookie choicesAccess requests
pisingyok pisingyok Privacy Policy for Your Account Data
CONTACT ROUTE

Where You Can Ask About Your Data

A clear contact path helps when you need to ask what our Privacy Policy means for your account. Start with the support route shown after login and include the phone number connected to your account, the affected wallet rail and any receipt reference. We can then check the correct record without asking you to send unnecessary personal details.

Team online

Account data request

Use the logged-in support route to ask which account details we hold, why they are used and whether a correction is possible. Include your verified phone number so we can locate the right account.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, share the transaction reference rather than a wallet password. We use the receipt and account step to trace status while limiting extra information.

Policy change request

If you want to update a detail, ask about cookie choices or request removal where permitted, send the request through support. We may confirm account ownership before making a change.

SECURITY PRACTICE

Account Security From Login Through Retention

We keep the Privacy Policy practical by linking each data use to an account action: phone verification, wallet matching, device access or support.

Data we collect

We may receive your account details, verified phone number, device signals, login events and transaction references. If you open Sugar Rush or Mega Fishing, the session record supports account security rather than changing the data rules.

Why we use it

We use account and transaction data to provide access, match DANA or bank transfer records, check unusual activity, answer support questions and meet duties where local law permits.

Cookie handling

Cookies can remember session settings and help pages work across your mobile path. You can adjust browser cookie controls, though restricting them may require another account step or affect saved preferences.

Login protection

Phone verification is part of account access, and we may compare device or login signals when a session looks unusual. Never send your password or wallet security code through a support request.

Retention approach

We keep records for account operation, payment matching, dispute handling, security checks or legal needs. When a record no longer serves one of those purposes, we assess it for deletion or restricted storage.

Your request path

You can ask for access, correction, clarification or a permitted deletion through the support route. We verify ownership first, explain any restriction and respond using the contact details attached to your account.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account, wallet and device questions you are most likely to have before opening an account. They also explain the practical route for checking records, changing details and contacting us when access depends on local law.

It covers account details, phone verification, device signals, cookies, login events, wallet references and support records connected with pisingyok.net. It also explains purposes, retention, security and available requests.

We use your phone number for account verification, access checks and support matching. It helps us identify the correct account when you ask about DANA, QRIS, login activity or a personal data request.

Yes. The Privacy Policy covers transaction references and status details linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We do not need your wallet password to investigate a receipt.

You can request access through the support route connected with your account. Tell us the verified phone number and request scope; we may confirm ownership before sharing records or explaining a lawful restriction.

Send a correction request through account support and identify the field that needs changing. We may ask for a verification step, then update the record when the request matches your account details.

Retention depends on why the record exists, including account operation, payment matching, security, disputes or legal duties. We assess records when those purposes end and remove or restrict them where permitted.

Yes. Contact support with your device path and the page affected, or adjust cookie controls in your mobile browser. Restricting cookies may require you to repeat a login or preference step.