pjsk Platform Privacy Notice and Data Handling Summary
This page describes what we collect when you use pjsk and how we keep that data protected.
We at pjsk set this notice to explain our common data practices for account handling, payment processing and table/live-stream analytics. Our summary covers the data types we hold, retention principles and how we share data with service providers where local law permits.
We at pjsk recognise that customers in Jakarta, Surabaya and Bandung may ask about local payment options and data flows. Our teams record which Indonesian payment rails are used so we can reconcile settlements with DANA, e-wallet, mobile banking and local payment gateways.
Our pjsk data details
We collect data to operate accounts, verify identity when required, process deposits and withdrawals, and run live-dealer studio logistics. Our records focus on transactional and operational needs and not on profiling beyond session analytics.
- We collect account identifiers — name, email address, phone number and account history.
- We collect verification documents only for identity checks where law requires; our verification workflow records document type and verification outcome.
- We record payment metadata — payment method, transaction ID, and reconciliation notes for DANA, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment and e-wallet transactions.
- We log connection and device data — IP addresses, device model, browser agent, and timestamps for session integrity and fraud detection.
- We store live table session details — table identifier, dealer language, camera stream labels and session duration for studio quality reviews.
Data and payments in regional context
Our reconciliations align to Indonesian payment schedules and public event calendars such as Liga 1 and Piala AFF to improve settlement accuracy during high-traffic periods like Idul Fitri and Idul Adha.
We use cookies and similar technologies for authentication, session continuity and analytics. Our cookies include essential session cookies for login persistence and non-essential cookies for anonymised performance metrics.
We retain data according to operational needs and legal requirements. Our retention schedule varies by data type: transactional records are kept for reconciliation and compliance; ephemeral analytics are retained for a shorter interval.
Our pjsk policy on sharing, rights and protection
We share data only with service providers who perform functions on our behalf. Our third-party processors include payment gateways, identity verification vendors and cloud infrastructure providers. Our contracts with vendors require data protection measures and limit use to agreed services.
We may store or process data on servers outside your jurisdiction where permitted. Our infrastructure choices aim to keep latency low for live-dealer tables and to maintain secure backups; our servers may be located in jurisdictions with robust privacy safeguards.
Our obligations and your rights
We respond to access, correction and data export requests where local law permits. Our support team processes requests submitted through the contact route below and confirms identity before releasing personal data.
- We provide access to personal data we hold about an account on request, subject to verification.
- We correct inaccurate account details when you provide evidence to support the change.
- We erase data when deletion requests meet legal and operational conditions, balancing fraud prevention and regulatory requirements.
We retain logs of sharing and disclosures in case of audits. Our disclosure policy allows transfers to comply with lawful requests and to protect the security of accounts and live-dealer operations.
Contact and changes
We update this notice from time to time to reflect changes in our services or legal obligations. Our updated policy will appear here and we will record the effective date.
We handle enquiries and requests via our support centre; for account or data queries use ContactOur team may request identity confirmation before acting.
We recommend checking this notice during major local holidays or events such as Idul Fitri, Imlek or Nyepi when volume and payment flows change. Our support pages link to city-specific guidance for Jakarta and Medan help where available.
We at pjsk commit to maintaining operational safeguards, limiting data access internally and reviewing processor agreements regularly. Our approach aims to keep payment reconciliations clear for DANA and e-wallet flows and to protect session logs for live-dealer quality control.
We welcome questions about this notice and will provide clarification where local law permits. Our contact route is the primary channel for data requests and operational queries.