Reference

paki99 Privacy Policy For Your Account

paki99 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, browse Live Baccarat Table, or use DANA, OVO, GoPay…

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
paki99 paki99 Privacy Policy For Your Account
HELP WITH REQUESTS

Three Ways To Ask About Privacy

A clear contact route helps when you want to understand a record, correct an account detail or ask about cookie use. Start inside your signed-in account and include the email or phone linked to your profile, so we can check the request without exposing data to the wrong person. If a wallet receipt or login event is involved, keep its reference ready; our support team can compare the account record with the status shown beside the cashier.

Team online

Account support route

Use the support path connected to your account for a Privacy Policy question, access request or correction. Include your registered contact detail and a short description of the record you want us to check, without sending a wallet password or one-time code.

Payment record check

For DANA, OVO, GoPay or QRIS questions, share the payment reference and date shown on your receipt. We use those details to locate the matching status, while your wallet login credentials remain private and should never be sent to our team.

Access concern

If a phone or desktop sign-in looks unfamiliar, contact us through the account support route and describe the device, time and account step involved. We may ask for verification before discussing personal data or changing account access settings.

DATA HANDLING CHECK

Six Controls Behind Our Privacy Work

We handle Privacy Policy requests as account matters rather than broad lobby questions. Our process links the request to your registered account, checks the relevant device or wallet record and limits the…

Collected account data

We may record your name or contact detail, account settings, sign-in history and verification events. These records help us recognise your account when you move from login to the lobby, and they let us investigate access concerns without relying on a public profile.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount, time and status record. We use that trail to match a receipt with the correct account and to resolve a cashier question.

Cookies and devices

Cookies and device signals can remember a session, language choice or security event. You can review browser controls on your phone or desktop, though switching cookies off may require another sign-in before account data is shown.

Account security

We use sign-in checks, verification steps and access records to reduce the risk of an unauthorised account change. Never share your password or one-time code; if a device looks unfamiliar, contact support before changing wallet or profile details.

Retention decisions

We keep personal data only as long as it supports account operation, security checks, dispute handling or a legal duty. When a record is no longer needed for those purposes, our process allows it to be deleted or separated from active account use.

Requesting a change

To request access, correction or deletion of eligible data, contact us from the account route and identify the relevant profile detail. We may verify your identity first, then confirm the action, any limit that applies and the next step.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account and payment questions you are most likely to have before opening an account or checking a wallet record. We keep the process tied to your registered details, and access depends on local law. If your question is not listed, use the account support route with the relevant receipt, device or sign-in context.

The paki99 Privacy Policy covers account details, sign-in events, device signals, cookies, verification records and payment references. It explains why we use each category, how long records may be kept and how you can request access, correction or deletion where local law permits.

No. We use the payment reference, amount, date and status needed to match a DANA or OVO transaction with your account. Your wallet password and one-time code should remain with you. Send only the receipt details needed for a payment status check.

QRIS and GoPay transactions can create records that show which account initiated a payment, when it was made and whether the cashier status changed. We use those records for reconciliation, security and support. We do not need your wallet login credentials to check them.

Use the support route inside your signed-in account and ask for a Privacy Policy data request. Include your registered phone or email and the record category, such as cookies, sign-ins or payment references. We may verify you before sharing account data.

Yes, you can ask us to correct eligible account data through the account support route. Tell us which detail is wrong and provide the accurate version. We may request verification, and access to a correction depends on local law and the record involved.

Cookies can keep a sign-in session, remember a page setting or help us identify a security event. You can adjust cookie controls in your mobile browser. If you disable them, you may need to sign in again before account or cashier details appear.

Contact us through the account support route and provide the approximate time, device type and account step connected with the unfamiliar login. Do not send your password or one-time code. We may verify your identity before discussing the event or changing access.

Related Pages

paki99 Indonesia About Us Live Baccarat Table Access guide Esports Dota 2