Reference

panen77 Privacy Policy For Your Account

Your DANA, OVO, GoPay and QRIS records stay tied to the account steps that create them, so our Privacy Policy can explain what we collect and why.

Account dataCookie choicesPayment recordsAccess requests
panen77 panen77 Privacy Policy For Your Account
CONTACT ROUTES

Where To Ask About Your Data

A clear contact route helps when a Privacy Policy question concerns your account rather than a general explanation.

Account privacy request Use the account support path to ask what personal data is linked to your profile, why a field is needed, or how to request a correction under this Privacy Policy.
Payment record question For DANA, OVO, GoPay or QRIS records, provide the transaction reference and approximate date. We use that detail to locate the record without asking you to send a wallet password.
Access concern If a new device, phone verification step or sign-in event looks unfamiliar, contact us through the account route and describe the event so we can check access activity.
HANDLING DETAILS

How We Apply This Privacy Policy

Our handling steps follow the actions you take, from phone verification to a wallet status check. We separate account identification from payment references where practical, review unusual sign-in signals, and keep policy…

Account data

We may use your phone number, contact details, verification result and account activity to create access, confirm that a request comes from you, and respond to a Privacy Policy question.

Device signals

A mobile browser can provide device, browser and sign-in timing signals. We use them to recognise unusual access patterns, investigate account security concerns and keep the sign-in path connected to your profile.

Cookie controls

Cookies can remember session choices and help us understand which policy page brought you to an account action. You can manage browser cookie settings, though some sign-in functions may then need to be repeated.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes may return references and status results. We use those records for matching, receipt checks and account support, not for wallet passwords.

Retention timing

We retain account, security and transaction records only as long as needed for the stated service, dispute checks, security work or legal duties. Retention can vary by record type and local requirements.

Policy changes

When this Privacy Policy changes, we place the revised wording on the policy page and show the effective date. You can contact us through your account route to ask what changed or request a data correction.

Privacy Policy Answers For panen77

These Privacy Policy answers focus on the account, device and payment questions you are most likely to have before opening an account. If your situation is not covered, use the account support route and refer to the exact section or payment reference involved.

It covers data linked to account creation, phone verification, sign-in, device signals, cookies, lobby activity and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account routes.

Phone verification helps connect an account request to the correct contact detail and supports access checks. We use the result for account handling and security, subject to this Privacy Policy and local requirements.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay references or status results received during an account transaction. Do not send us a wallet password; a transaction reference is enough for checking.

You can request a correction through the signed-in account support path. Include the affected field and the contact detail attached to your profile, so we can confirm the request and respond where local law permits.

Cookies can keep a sign-in session active, remember page choices and show which policy route you opened. Browser settings can remove or restrict them, although some account steps may need to be repeated.

Retention depends on the record and the reason it is held. We keep account, security and payment references for service needs, dispute checks or legal duties, then remove or restrict them when appropriate.

Use the support route connected to your account and ask for a data access request under the Privacy Policy. Add your registered contact detail, and we will verify the request before responding.