Reference

pon55 Privacy Policy Explained Clearly

The pon55 Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Roulette Gold or use DANA and QRIS.

Account dataWallet recordsPhone verificationPolicy access
pon55 pon55 Privacy Policy Explained Clearly
HELP WITH YOUR DATA

Account Support Beside The Cashier

A clear support path matters when a privacy question follows a wallet action. We ask you to start from the account area so we can connect your request with the correct phone verification record, payment reference or device session. The same route works if you need help understanding a Privacy Policy clause, correcting account details or checking why a data request needs more confirmation. Send the relevant account email or reference, but never include a password or one-time code.

Team online

Policy questions

Ask about the Privacy Policy through the account support path linked beside the cashier area. Include the email or phone attached to your account and describe the clause or data record you want us to explain.

Correction requests

If your phone, email or account name needs correction, send the requested change from your signed-in account. We may compare it with the phone verification step before changing the record, helping us avoid edits by another person.

Payment records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, provide the transaction reference and date. We use those details to locate the record without asking you to share a wallet password or private security code.

HOW WE HANDLE RECORDS

Privacy Controls From Login To Retention

Privacy is handled through practical account controls rather than vague promises. We separate the details needed to open an account from activity records used to match wallet and cashier events, and we…

Account collection

We collect the details needed to create and maintain your account, including contact information and phone verification data. We do not ask for a password in a support message, and you can ask us which account fields are held.

Wallet matching

DANA, OVO, GoPay and QRIS references are used to match a cashier event with the right account. Bank transfer and virtual account references serve the same purpose, while wallet credentials stay with the payment provider.

Device sessions

We may record browser, device and session details when you sign in or move from the mobile lobby to the cashier. These records help us investigate unusual access without treating your device data as a public profile.

Cookie choices

Cookies and similar storage can remember a session, protect account movement and show whether a policy page was opened. Your browser settings can restrict them, although some account and phone-check steps may then need to be repeated.

Retention period

We retain account, payment and support records only for operational, security or legal needs connected with the service. When a record is no longer needed, we remove it or use a form that no longer identifies you where practical.

Your requests

You can ask for access, correction or clarification through the account support path. We may request account or phone confirmation before responding, and access to the service remains where local law permits and applicable requirements are met.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions we expect Indonesian account holders to ask before opening an account or connecting a wallet. They explain the practical route for checking data, changing details and understanding device or payment records. If your situation is not covered, use the account support path and include only the reference needed to locate your request.

The pon55 Privacy Policy covers account details, phone verification, browser and session records, support messages, cookies and payment references. It also explains how we use records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect the person opening an account with the requested account record and reduces mistaken or unauthorised changes. We may use that check when you request a correction, ask for account data or need help with a payment reference.

Yes. Send an access request through the signed-in account support path and identify the email or phone attached to your account. We may ask for a matching confirmation before disclosing account, session or payment-related records.

Use the account support path to request a correction to your contact or account details. Explain what is wrong and what should replace it. For phone changes, we may repeat verification before updating the record.

Yes. The policy includes relevant browser, device and session records created when you sign in on mobile, open the lobby or move to the cashier. Cookies may keep a session active, and restricting them can require another sign-in.

We use DANA and QRIS references to match a cashier request with your account and its status. Similar records can apply to OVO, GoPay, bank transfer and virtual account activity. We do not ask for your wallet password.

Ask through the account support path and state whether you want clarification, correction or removal of a record. We assess the request against operational and legal needs, and access or eligibility depends on local law.