Reference

pegasus4d Privacy Policy For Your Account

Our Privacy Policy explains how we handle the details you provide when opening a pegasus4d account, signing in from a phone, or checking DANA, OVO, GoPay and QRIS…

Account dataWallet recordsCookie choicesAccess requests
pegasus4d pegasus4d Privacy Policy For Your Account
CONTACT OUR TEAM

Where To Ask About Privacy Policy

A direct support path helps when you need to understand a record connected with your account.

Privacy request Ask us to explain, correct or remove account data where applicable. We may first confirm your account phone number before discussing records linked to your profile.
Wallet record If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the payment reference through our support route. We use the reference to locate the relevant account event.
Access help When phone verification or a sign-in alert blocks access, tell us the device and approximate time. We can direct the request without asking you to post sensitive credentials.
DATA HANDLING

What We Do With Your Account Data

We keep our Privacy Policy tied to real account actions rather than vague promises. A phone verification event, a mobile sign-in, and a QRIS payment reference each help us understand which record…

Account creation

When you open an account, we use the details supplied in the form to create your profile and support sign-in. Phone verification confirms that the access step is connected to you.

Device signals

A phone or desktop session can produce device, browser and security-event records. We use these signals to identify unusual access around the lobby, account page or payment status.

Cookie controls

Cookies can keep a session working and help us remember selected settings. You can manage cookies through your browser, although changing them may affect sign-in or page behaviour.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment event with the correct account. We use the reference for status checks, not unrelated profiling.

Retention process

We retain account, security and payment records for the period needed to run the service, investigate disputes and meet applicable duties. When a record is no longer needed, our process addresses its removal.

Change requests

You can ask for access, correction or a permitted deletion by contacting support through the site. We may request account details privately to prevent another person from changing your records.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions we hear most often from people using pegasus4d in Indonesia. They explain what may be collected, why a device or wallet reference can appear in a record, and how to contact us about a change. If your situation is not covered, send a private request through the support path shown on the site. Access and eligibility depends on local law.

It covers data connected with account creation, phone verification, sign-in, device sessions, support requests, cookies and payment status. This includes records linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification connects account access with the number supplied during registration and helps us respond to access requests. If a sign-in alert or wallet question reaches support, we may use that step to confirm the correct account.

Yes. The Privacy Policy explains that we may record device type, browser details, session timing and security events. These signals help us identify unusual access from a phone or desktop without requiring you to share your password.

Contact our support desk through the private channel shown on the site and request access to your account data. Include enough account detail for verification, but do not send passwords or wallet credentials in a public message.

You can ask us to correct inaccurate account details or clarify a payment record. Tell us which field or reference is wrong and provide the account phone number through the secure support route so we can check the source record.

We may retain DANA or QRIS references, status details and timing needed to match an account payment. The Privacy Policy limits that use to account operation, security, support and applicable legal duties.

Send a deletion request through the support route named on the site. We assess the request under applicable duties and the need to retain account, security or payment records before confirming what can be removed.