Reference

Your paushoki Privacy Policy

Your account, wallet, and lobby data are explained here before you open an account, including how DANA, OVO, GoPay, QRIS, Blackjack, and Sportsbook activity connect to your profile.

DANA data contextOVO account checksGoPay wallet recordsQRIS payment trailLocal-law access
paushoki Your paushoki Privacy Policy
CONTACT ROUTES

Privacy Help Through Local Channels

Privacy questions should reach the team that can check account records, not a general inbox with no account context.

Live Chat Use the chat button inside your account for privacy questions tied to login records, device changes, or game session data. Our team is available 10:00-23:00 WIB and may ask one account step before discussing personal data.
WhatsApp Send privacy requests through the WhatsApp number shown after you sign in, especially when your phone number or wallet route has changed. We compare the request with your registered number before changing data or sharing account details.
Email Use email for written requests about correction, deletion, or access to your personal data. Include your username, registered phone number, and the relevant DANA, OVO, GoPay, or QRIS reference so we can trace the record accurately.
ACCOUNT CARE

How We Handle Privacy Requests

We treat privacy as part of account operations: the same wallet, login, and support records that help you enter the lobby also help us answer data requests correctly.

Account data

We store account details you provide during sign-up, including username, phone number, contact route, and login status. This lets us confirm that the person asking about privacy is the same person who controls the account.

Wallet records

DANA, OVO, GoPay, and QRIS references are kept with transaction status, time, and account ID. We use them to answer payment privacy questions and to trace wallet activity without exposing unnecessary payment details.

Device signals

When you use mobile browser, tablet, or laptop, we may record device type, browser version, and IP signal. These details help us detect unusual sign-ins and explain account access history when you ask.

Cookie use

Cookies keep your session active, remember basic preferences, and help the login page work correctly. You can clear cookies in your browser settings, but you may need to sign in again afterward.

Retention checks

We keep records only as long as needed for account service, wallet tracing, security checks, support history, or legal reasons. When data is no longer required, we remove it from active account tools where practical.

Change requests

You can ask us to correct a phone number, contact route, or other account detail after we verify ownership. For sensitive changes, we may compare your request with recent login and wallet activity.

Privacy Questions Before You Join

These answers cover the privacy points you may want settled before opening an account or returning to the lobby. We focus on what data is collected, why it is used, how payment records are handled, and how you can reach us when something needs correction. If a request involves access or eligibility, our answer still depends on local law where you are located.

We collect the account details needed to create and protect your profile, such as username, phone number, login status, and contact route. We may also record device and IP signals when you sign in.

We use wallet references to match payment status with your account, answer transaction privacy questions, and check unusual activity. We do not need your full wallet app history to handle a payment record.

Yes. Contact us through in-account chat, WhatsApp, or email from your registered details. We may ask for one account step, such as username and phone match, before sharing or changing personal data.

Cookies help keep your session active and connect basic activity to your signed-in account. Game session records may show timing and account ID, but we use them for account service, security, and support checks.

We keep account, wallet, contact, and security records while they are needed for service, dispute handling, legal reasons, or account safety. When a record is no longer needed, we remove it where practical.

Only team roles that need the data for account service, wallet tracing, support, or security can access it. We limit what each role can see, and sensitive requests require account ownership checks.

We review the request against account status, wallet records, support history, and legal needs. Some records may need to stay for operational or legal reasons, and we explain what can be removed.