pgbet rtpPrivacy Policy

This page describes what we collect when you use pgbet rtp and how we keep that data protected. We collect personal information during account registration (name, date of birth, email, phone number, identity documents, and payment details). We use this information to verify your identity, process your deposits and withdrawals, comply with anti-fraud requirements, and provide customer support. We do not sell your data to third parties; we share information only when required by law or to process your payment transactions.

Our servers and data storage sit in jurisdictions outside your location. This means your data travels across borders during normal platform operation. We encrypt all data in transit (using TLS) and at rest (using industry-standard encryption). Access to your personal information is restricted to authorised pgbet rtp staff and our payment processors. We retain your data for the duration of your account and for a legal retention period thereafter.

This privacy policy applies to all uses of pgbet rtp—whether you access via web browser, mobile app, or third-party payment integrations. By using pgbet rtp, you agree to the practices described here.

What data we collect on pgbet rtp

We at pgbet rtp collect several categories of information when you register and use our platform. During account creation, we request your full legal name, date of birth, email address, and mobile phone number. We verify these details against official identity documents (KTP, SIM, or passport) and proof of residence (utility bill or bank statement). This is mandatory KYC (know-your-customer) verification; we cannot provide services without it.

When you deposit funds, we capture your payment method details. If you use DANA, e-wallet, or mobile banking, we record the transaction ID and timestamp. If you use a bank transfer or local payment, we log your bank account information and the unique reference number. We do not store full credit-card numbers or bank credentials; our payment processors handle those securely on their own infrastructure.

Account data
Name, date of birth, email, phone, address, identity-document images, account balance, and login history.
Transaction data
Deposits, withdrawals, game activity, settlements, and all timestamps. This includes Liga 1 wagers, live-dealer play, slot sessions, and arcade games.
Device and access data
IP address, device type, browser version, and login timestamps. We use this to detect unauthorised access and prevent fraud.
Support communications
Email, chat transcripts, and phone records if you contact pgbet rtp support. We retain these for dispute resolution and quality assurance.

We collect usage analytics: which games you access, how long you stay in each session, which payment methods you prefer. This data is aggregated and anonymised for internal reporting; we do not use individual session data for marketing or profiling without your consent.

We do not collect cookies for tracking on pgbet rtp

Our platform uses session cookies only for account authentication (to keep you logged in). We do not use third-party tracking cookies, retargeting pixels, or behavioural analytics tools. Your browser privacy settings do not affect pgbet rtp core functionality.

How we use your data on pgbet rtp

We use your data for five primary purposes. First, identity verification: we compare your submitted documents against government records to confirm your identity and age. Second, transaction processing: we pass your payment details to our payment processors (online payment, e-wallet, mobile banking, local payment, etc.) to execute deposits and withdrawals. Third, fraud prevention: we analyse transaction patterns to detect suspicious activity, such as rapid deposits followed by immediate large withdrawals from multiple accounts.

Fourth, compliance: we retain transaction records to comply with anti-money-laundering (AML) regulations in our operating jurisdictions. If authorities request account data, we may disclose it without notifying you, as legal obligation overrides our privacy commitment. Fifth, customer support: we review your account history and transaction data when you file complaints or request assistance. Support staff access only the information necessary to resolve your issue.

We do not use your data for direct marketing. We do not sell your email address to third-party advertisers. We do not profile you for predictive behavioural targeting. If we introduce optional email notifications (e.g., "upcoming Liga 1 match alerts" or "scheduled maintenance notices"), you control this via your account settings on pgbet rtp.

Third-party data sharing on pgbet rtp

We share your data with third parties only in these specific cases: (1) payment processors (online payment, e-wallet, mobile banking, local payment, online payment) receive your payment details to execute transactions; (2) identity-verification vendors receive your government documents to validate KYC; (3) fraud-detection services receive transaction data to screen for suspicious patterns; (4) legal authorities receive account data if compelled by warrant or court order.

All third-party vendors sign data-processing agreements with pgbet rtp, binding them to the same confidentiality standards we apply. We audit vendor practices annually. We do not permit vendors to use your data for their own marketing or analytics.

  • 1
    Payment processorsVendors

    e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking networks, and Indonesian banks (local payment, online payment, e-wallet, mobile banking) receive your transaction details. They do not use this for secondary purposes without explicit consent.

  • 2
    Identity verificationVendors

    Third-party KYC services receive your identity documents and personal data. They verify authenticity and return a pass/fail result; pgbet rtp then deletes their working copies.

  • 3
    Fraud and AML screeningVendors

    We share transaction patterns (not personal names) with fraud-detection services to screen for suspicious activity. These vendors flag high-risk transactions; we then investigate further if needed.

  • 4
    Legal disclosureAuthorities

    We comply with lawful requests from courts, police, or tax authorities. We do not notify you of such disclosures; legal obligation permits us to withhold notice.

Your data rights on pgbet rtp

You have the right to request a copy of all personal data we hold about you on pgbet rtp. Contact our support team with your request; we will compile your data and provide it within 30 days. You can request correction of inaccurate information (e.g., if your name is misspelled in our system). You can request deletion of your account and associated data, subject to our legal retention obligations (we must retain transaction records for seven years for AML compliance).

You do not have the right to be "forgotten" on pgbet rtp while an account dispute is ongoing or while we are legally obligated to retain your records. After your account is closed and all legal obligations expire, we purge your personal data from active systems. Backups containing your data may persist in encrypted archives for disaster recovery; these are not accessible for any operational purpose.

To exercise any of these rights, email our support team at the address listed on our website or submit a formal written request. Provide your account number and a description of your request. We respond within 30 days or provide a written explanation of any delay.

Data security practices on pgbet rtp

We encrypt all data in transit using TLS 1.2 or higher. All communication between your browser or app and pgbet rtp servers is encrypted; an eavesdropper cannot intercept your login credentials or payment details. At rest, we encrypt sensitive data (passwords, identity documents, payment information) using AES-256 encryption. Database access is restricted to authorised database administrators; application servers cannot directly access encrypted fields without decryption keys held separately.

Our servers sit in data centres with physical security controls: restricted access, surveillance, and fire suppression. We conduct annual penetration testing to identify vulnerabilities. We patch security vulnerabilities within 48 hours of discovery. We maintain an incident-response plan; if a breach occurs, we notify affected pgbet rtp members within 72 hours and provide guidance on protective steps.

Your password is hashed on our servers; we do not store it in plaintext. We require two-factor authentication (SMS verification) on all withdrawal requests, meaning a compromised password alone cannot authorise fund transfers. You can reset your password at any time; we send a confirmation link to your registered email and require SMS verification to complete the reset.

Cross-border data transfers on pgbet rtp

Our pgbet rtp infrastructure may span multiple countries. Your data may be processed or stored outside Indonesia, including in jurisdictions with different privacy laws. By using pgbet rtp, you consent to such transfers. We ensure that any processors outside your jurisdiction maintain equivalent security and confidentiality standards through contractual data-processing agreements.

If you are a member in Jakarta, Surabaya, Bandung, or Medan accessing pgbet rtp from Indonesia, your transaction data may be transferred to servers in Singapore, Malaysia, or other regional data centres. This is necessary for platform resilience and performance. We do not transfer data to jurisdictions with inadequate privacy protections.

Policy updates and contact

We may update this privacy policy at any time. Changes take effect when posted on this page. We notify active pgbet rtp members of material changes via email. Your continued use of pgbet rtp after an update constitutes acceptance of the revised policy.

For privacy questions or data-access requests, contact pgbet rtp support through our website. Include your account number and a detailed description of your request. We respond within 30 days. This privacy policy is effective as of the date posted on this page and supersedes all prior privacy statements.