Reference

prabusport Privacy Policy for Your Account

Our Privacy Policy explains how prabusport handles the details you provide when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and…

Account clarityWallet recordsCookie choicesMobile access
prabusport prabusport Privacy Policy for Your Account
PRIVACY CONTACT

Reach Support About Your Privacy Request

A clear contact path helps you ask about the data attached to your prabusport account. Send your request through the support route shown on the site and include your account identifier, the…

Account access If you cannot reach your account after phone verification, contact support with the affected login detail so we can separate an access issue from a privacy request.
Wallet records For a question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, provide the transaction reference rather than sending your full payment password.
Policy changes Ask us to correct or clarify account data through the privacy contact route. We will check your identity before changing records connected with Baccarat or another lobby activity.
DATA HANDLING

Browse How We Handle Account Data

We handle Privacy Policy requests through practical account checks rather than broad claims. Our records can connect a phone verification event, device session, wallet reference and selected lobby activity, such as Mahjong…

Data we receive

Account creation can provide your name, phone detail, sign-in record and verification status. Wallet activity may add a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference.

Device signals

When you use a phone browser or desktop browser, we may record device type, browser settings, session time and security events needed to recognise unusual account access.

Cookie controls

Cookies can keep a session active, remember selected settings and help us detect repeated sign-in attempts. You can manage cookie permissions through your browser settings, though some account steps may not work.

Account security

Phone verification is required before account access, and we may compare session details with earlier sign-ins. Never send a password or wallet security code when asking about your Privacy Policy rights.

Retention approach

We keep account, security and payment references only for the period needed for the stated purpose, account protection and legal duties. Retention can vary when local law sets a different period.

Your request route

You can ask what personal data we hold, request a correction, question a processing purpose or ask about deletion through support. We may request identity details before releasing or changing records.

Check Privacy Policy Answers for Your Account

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. They explain what we collect, how mobile sessions and cookies fit into the record, and how to contact us about a correction or data request. If your situation is not covered, use the support route with your account identifier.

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

We use phone verification before account access to connect the correct person with the account, reduce unauthorised entry and confirm ownership when you ask about private account or wallet records.

Yes. The Privacy Policy includes technical details from your mobile or desktop browser, such as device type, session timing and security events used to maintain account access and detect unusual activity.

We use payment references and wallet status details to match account activity, check a transaction question and respond to support. We do not need your wallet password for a Privacy Policy request.

Yes. Send a correction request through the support contact route with your account identifier, the detail you believe is wrong and the preferred replacement. We verify identity before changing the record.

Retention depends on the purpose of the record, account protection needs and applicable legal duties. Payment references, security events and account details can follow different periods where local law permits.

You can request access to personal data connected with your account through support. Include the phone or email used at registration, and we may complete an identity check before sharing private records.