Reference

Open Your Privacy Choices With peta777

Your peta777 account connects lobby access, wallet checks and device sessions in one privacy flow, including DANA, OVO, GoPay and QRIS records tied to your profile.

Account data explainedDANA and QRIS contextDevice session checksSupport contact paths
peta777 Open Your Privacy Choices With peta777
HELP ROUTES

Check Privacy Help Channels Anytime

Privacy questions often need a clear route, not a generic inbox. Use our support paths when you want to correct account details, ask how a wallet…

Live chat Live chat is available daily from 09:00 to 23:00 WIB for privacy questions tied…
Email support Email us when your request needs attachments, such as a device access concern or…
Account page Your account page lets you review basic profile details and active session signs before…
ACCOUNT CARE

Browse Our Data Handling Steps

We keep the policy practical so you can see how data moves through the account flow. Each step has a purpose: opening the lobby, keeping your session active, recording wallet references, helping…

Account setup

When you join, we store the details needed to create and identify your account, such as username, contact fields and security signals. These records help us answer privacy requests without exposing your account to another person.

Payment records

DANA, OVO, GoPay and QRIS references are used to match wallet activity to your account. We keep transaction context such as timestamps and rail names, not unnecessary private notes about your payment habits.

Device checks

Mobile and desktop access can create session records, browser type, IP signals and login times. We use those details to spot unusual access, support account recovery and keep your session from dropping unexpectedly.

Cookies

Cookies help remember your session state, language preference and basic site performance signals. You can adjust browser settings on Chrome, Safari or Android WebView, though blocking all cookies may require repeated sign-ins.

Retention review

We keep records only as long as they support account operation, payment checks, support history or legal handling. When a record is no longer needed, we remove it or separate it from direct account identity where practical.

Change requests

You can ask us to update inaccurate profile details, explain a data use, or review a privacy concern. We verify account ownership first so another person cannot change or access your private record.

Get Answers About Your Privacy

These questions cover the privacy topics you are most likely to check before opening or returning to an account. We focus on what data is collected, why it is needed, how wallet references are handled, and how you can reach us when something in your record needs attention. The answers are written for Indonesia account use and should be read with the full policy on this page.

We collect the details needed to create and manage your account, including username, contact fields, login records and device signals. We also keep wallet references when you use DANA, OVO, GoPay or QRIS.

We record payment rail names, timestamps and transaction references so wallet activity can be matched to your account. This helps support answer disputes, verify status and avoid asking for more personal data than needed.

Yes, you can contact support to correct inaccurate profile details. We will first verify account ownership through your registered contact path or account identifiers before making changes to protect your private record.

Cookies keep your session active, remember basic preferences and help us understand site performance. If you block cookies in your browser, some account pages may ask you to sign in again more often.

Only team members who need the record to handle your request should access it. We use account matching and request context so support can respond without sharing private details across unrelated service channels.

Retention depends on the record type and why it is needed. Account, wallet and support records may be kept for operational, dispute-handling or legal reasons, then removed or separated from identity where practical.

Yes. Access and eligibility depend on local law and are available only where local law permits. We may use region or device signals to apply account controls connected to that requirement.