Live / App
pka333 collects only the information needed to run your account, process payments through bKash, Nagad, or Bank Transfer, and keep your session secure. This policy explains exactly what we collect, why we keep it, and what choices you have — access depends on your local law and eligible regions.
When you open an account with us, we collect the details you enter during registration — your name, contact information, and the credentials you choose. Once your account is active and you add funds via bKash, Nagad, or Bank Transfer, we record those transaction details: the method used, the amount, and the timestamp. We do not store your mobile wallet PIN or bank login credentials at any point. We also collect session data automatically — device type, browser version, pages visited, and time on site. This helps us keep the account flow working correctly across your phone and any other device you use. We use cookies to hold your session state so you are not logged out mid-visit. All data is held only as long as your account is active or as required by the applicable rules in your region. When you close your account, we follow a defined retention schedule before removal. If your local law sets a longer minimum retention period, that period applies. We do not sell your personal data to third parties. Data shared with payment processors — such as those handling bKash or Nagad transactions — is limited strictly to what those processors need to complete your request.
Transaction timestamps and amounts for bKash deposits are logged against your account wallet. We share only the minimum data required by the payment processor to complete the transfer.
Nagad payment entries follow the same record structure as bKash. Your mobile number is tied to your wallet entry but is not shared beyond the transaction processing step.
Bank Transfer details are held in your payment history tab. Reference numbers and amounts are visible there so you can cross-check against your own bank statement.
We log device type and session duration to keep your account stable across switches between mobile and browser. This data is not used for advertising profiling.
This policy covers activity on pka333 and any mobile browser session connected to your account. It does not extend to third-party services that open in a separate window or tab — for example, a payment provider's own page or an external identity check portal. Each of those services carries its own terms. Eligibility to use any part of this platform depends on your local law and the regions where access is permitted.
Data collected when you log in, navigate the lobby, or update account settings falls fully within this policy. This includes device identifiers and session tokens stored to keep you logged in.
Deposits and withdrawals processed through bKash, Nagad, Rocket, or Bank Transfer are covered here for the data we hold on our side. The payment provider's own data handling sits outside our policy.
Pages you visit on pka333, cookies we set, and analytics we collect about your browsing path on this domain are all within scope and described in this document.
Links to external sites, wallet portals, or identity verification pages leave our scope the moment you exit pka333. We recommend you read those providers' own policies before proceeding.
You have concrete options when it comes to the personal data we hold. Your account settings page shows the profile details we currently have on record — name, contact information, and linked payment methods including any bKash or Nagad number you have verified. If any of those details are incorrect, you can update them directly from the settings screen without contacting support, as long as the change does not affect a payment method that has an outstanding transaction under review. For payment history specifically, the transaction log in your account wallet shows every deposit and withdrawal record with date, method, and amount. If a record looks wrong, the fastest route is to raise it through our support contact — details are in the Support section below. We aim to acknowledge data queries within a reasonable time, though we do not state a fixed response window because actual handling depends on the nature and volume of the request. If you want your account closed and data removed, submit that request through the same support route and we will follow the retention schedule that applies in your region.
Open account settings to see the name, contact details and verified payment methods we hold. Changes to non-pending fields can be made directly from that screen.
Your wallet history tab lists every bKash, Nagad, Rocket and Bank Transfer entry. Cross-reference these against your own records and flag any mismatch to support.
Send data-related queries through our published support route. Include your account ID so we can pull the correct record set without delay.
Submit a closure and data removal request via support. We follow a regional retention schedule before permanent deletion, consistent with applicable local requirements.
If you have a question about this policy, a data correction request, or a concern about how a payment record has been stored, use the contact routes we publish on pka333. Please include your account ID in any message so we can locate your record without asking for unnecessary back-and-forth. Availability of support depends on your region and local conditions.
The chat widget on pka333 is the fastest way to raise a privacy or data question. Start there with your account ID ready.
For written records of your request, use the email address published in the Contact section of our site. Email is suitable for account closure and data removal requests.
The Help section on pka333 lists common data and account questions with step-by-step guidance. Check there first before opening a new support ticket.
Account and payment data is held on servers with access controls that limit who can read or modify records. We use HTTPS for all connections between your device and pka333, so data in transit — including the moment you enter your bKash or Nagad number — is encrypted. Internally, access to payment records is restricted to the roles that need it to process your request. We review these access controls on an ongoing basis rather than on a fixed public schedule.
We keep your account data while your account remains open and for the minimum period required by applicable regional rules after closure. We do not hold data longer than necessary.
We use session cookies to keep you logged in and functional cookies to remember your account preferences. You can manage cookie settings in your browser, though some site functions depend on them.
We do not store your bKash PIN, Nagad PIN or bank login. Payment processor integrations receive only the minimum data required to complete the transaction you initiate.
When we update this policy in a material way, we will post a notice on pka333 and, where practical, send a notification to your registered contact. Continued account use after a notice constitutes acceptance.
These are the questions we hear most often about how we handle personal data, payment records and account access. If your question is not covered here, reach us through the support routes listed above.
No. We never store your mobile wallet PIN or bank login credentials. When you initiate a deposit through bKash or Nagad, the transaction is handled on the payment provider's side. We only receive and record the confirmation that the transfer was completed.
Your account settings page shows the profile and payment method details we hold. Your wallet history tab shows all transaction records. If you need a fuller picture of what data we retain, submit a request through our support contact route with your account ID included.
Open account settings and edit the relevant field directly. If the field is locked — for example, a payment method tied to a pending transaction — contact support with your account ID and the correction you need. We will review and update the record.
Access is restricted to team members whose role requires it to process your account or transaction requests. We do not give general staff access to payment records. Data shared with payment processors is limited to what they need to complete the specific transfer you started.
We follow a defined retention schedule after account closure. The length depends on the rules applicable in your region. Once that period ends, records are removed. Submit a closure request through our support contact and we will confirm the retention period that applies to your account.
Yes. Bank Transfer deposit and withdrawal records are held within your pka333 account wallet and fall fully within this policy. The bank's own handling of the transfer sits outside our scope — check your bank's policy for that side of the transaction.