Reference

Privacy Policy For Your Account

pegasusplay77 Privacy Policy explains how we handle the details connected with your account, including phone verification, login activity and payment records from DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesContact access
pegasusplay77 Privacy Policy For Your Account
CONTACT OUR TEAM

Where Privacy Questions Go

A direct support route helps you ask about the Privacy Policy without sending sensitive details through an unsuitable channel.

Account support Use the support route connected with your account when a Privacy Policy question concerns phone verification, login history or a device used to reach the lobby. We ask for enough account detail to locate the record, while keeping passwords and one-time codes out of the conversation.
Wallet status If your question concerns DANA, OVO, GoPay, QRIS or a bank transfer reference, include the date, rail and visible status rather than a PIN. We use those details to trace the relevant record and explain how the Privacy Policy applies to payment support.
Access request For a copy, correction or deletion request, tell us which account detail you want us to check and how we can reach you. We may verify account ownership before acting, so another person cannot change your records through a casual message.
DATA HANDLING DETAILS

Six Practical Privacy Controls

We keep the Privacy Policy connected to the account actions you actually take, from opening access on a phone to checking a payment receipt.

Account collection

When you open an account, we collect the details needed for access and phone verification, together with security events such as login time and device signals. We use these records to recognise your account and investigate an access issue, not to request your private wallet credentials.

Payment records

A DANA, OVO, GoPay or QRIS action can leave a reference, amount, selected rail and status in our account records. Virtual account and bank transfer requests may also show a bank route such as BCA, BRI, Mandiri or BNI so support can match the receipt.

Cookies

Cookies and similar browser storage can keep a session active, remember a language choice or help us understand whether a login page loaded correctly. You can manage browser storage through your device settings, though removing essential cookies may require you to verify access again.

Account security

We use phone verification, session checks and device signals to help protect account access. If a login looks unusual, we may pause a sensitive request until ownership is confirmed. Never send us your password, wallet PIN or one-time code in a support message.

Retention period

We retain account, support and payment records for as long as needed for the purpose described in this Privacy Policy, account security and required operational records. When a record is no longer needed, we remove it or separate it from direct account identification where practical.

Changes and requests

You can ask us to check, correct or remove eligible personal details by contacting account support. Tell us whether the request concerns your phone number, contact detail, cookie preference or another record. We may ask for verification before making a change or confirming what we hold.

Privacy Policy Questions For Indonesia

These Privacy Policy answers cover the account and device questions you are most likely to have before using pegasusplay77. We explain the practical route for access, payment records and data requests in plain English for Indonesian account holders. If your situation is not listed, contact us through the account support path with limited details and we will direct the request to the right team.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references. It also explains how we use those records for access checks, wallet status questions, security work, retention and requests to correct or remove eligible personal data.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay, QRIS, virtual account and bank transfer. We may use a reference to match a receipt, but you should never send a wallet PIN, banking PIN or one-time code.

We may collect your name, phone number, verification details, login timestamps, device signals and messages sent to support. The purpose is to provide account access, protect the session and answer your request. We do not need your private wallet password to handle ordinary support.

Contact account support and identify the detail you want checked or changed, such as a phone number or contact record. We may verify that you own the account before acting. This step protects your data from changes requested by someone using an unrelated device.

We keep records only for as long as needed for the purpose described in the Privacy Policy, account security and required operational records. After that period, we remove them or separate them from direct identification where practical. Support can explain the category involved in your request.

Yes. Your mobile browser settings let you clear or restrict cookies and similar storage. Essential session data may be needed to keep login working, so removing it can sign you out or require phone verification again when you return to the account.

Access depends on local law. The Privacy Policy describes how we handle data when you can use the account, but it does not change local eligibility rules. If access is not available where you are, do not try to bypass location or account checks.