Skip to content
2p888 Mobile / App
YOUR DATA RIGHTS

2p888 Privacy Policy: How We Handle Your Information

2p888 collects only the account and transaction data needed to run your wallet, process payments through bKash, Nagad, and Bank Transfer, and keep your account secure. This policy tells you exactly what we collect, why we hold it, and what you can do about it — access, correction, and contact routes included.

  • Account data collected at registration
  • bKash, Nagad & Bank Transfer transaction records
  • Your right to review and correct data
  • Contact route for all privacy questions
POLICY SCOPE NOTICE

What This Policy Covers and How It Applies

This privacy notice applies to every interaction you have with 2p888 — from the moment you open an account through to any withdrawal request you raise. We collect your registration details (name, contact information, and account credentials), your session activity on the site, and the records associated with any payment you make via bKash, Nagad, or Bank Transfer. Payment data is handled only to the extent needed to process and verify your transaction; we do not store full wallet credentials beyond what the payment flow requires. Your data is held on secure servers and is not sold to third parties for marketing purposes. We may share limited information with payment processors and fraud-screening services where that is necessary to complete a transaction or protect your account. Retention periods reflect legal and operational requirements; once data is no longer needed for those purposes, we move to delete or anonymise it. Access to and use of the 2p888 platform depends on your local law and eligible regions. If local regulations in your jurisdiction restrict access, those rules apply regardless of this policy's scope. If you have questions about a specific data point or transaction record, the support routes at the bottom of this page are the right starting point.

  • bKash transaction records

  • Nagad payment history

  • Bank Transfer account logs

  • Registration and login data

  • Session and device identifiers

INSIDE VS OUTSIDE

Where This Policy Applies — and Where It Does Not

Not every service connected to your 2p888 session falls within this policy. The table below draws the line clearly so you know which data practices we own and which are handled elsewhere. When you tap a bKash or Nagad payment link, the wallet app's own privacy terms govern that leg of the transaction; our policy covers only the record we receive back once the transfer is confirmed.

  • Account access and registration

    Covered fully. Any data you enter during sign-up, identity verification or password reset sits within this policy. You can request a review or correction through our support route at any time.

  • Transaction and payment records

    Covered for the records 2p888 holds. bKash, Nagad and Bank Transfer each maintain their own logs inside their platforms; what we hold is the confirmation data returned to us after your transfer completes.

  • Site content and game activity

    Covered for session data and game history tied to your account. RTP and game mechanics are governed by the studio supplying the title; we hold only the activity record linked to your wallet and account.

  • Third-party services and linked sites

    Not covered. If you follow a link to an external service, that site's own policy applies from that point. We are not responsible for data practices on pages we do not operate.

YOUR PRACTICAL CHOICES

Actions Available to You Under This Policy

You have concrete options when it comes to the data we hold. Reviewing your account details is the first step — log in and check the account settings page to see the profile information we currently hold. If any detail is wrong, you can raise a correction request directly through the support contact on this page; our team checks the submitted request against your account record and updates what is within our control to change. For transaction records tied to bKash, Nagad or Bank Transfer, we can confirm what our system shows on our side — if a discrepancy sits within the payment provider's own ledger, we will point you to the right contact route there. You can also ask what categories of data we hold on your account, request that outdated or unnecessary data be removed where that is operationally and legally possible, and withdraw any consent you gave at registration for optional data uses. Every request goes through the support route; we do not accept data requests submitted through unverified channels.

  • Review your account record

    Log in, open account settings, and check the profile fields we hold. If something is missing or wrong, note the specific field before contacting support — it speeds up the correction process.

  • Request a data correction

    Send your correction request through the published support route. Include your account identifier and the field you want changed. We check it against your original registration and update where we are able to.

  • Ask about retention and deletion

    You can ask which categories of data we hold and how long we keep them. Where data is no longer needed for legal or operational reasons, we can act on a deletion request within the limits the law allows.

  • Raise a privacy question

    Any question about how your data is used — including payment records linked to bKash, Nagad or Bank Transfer — goes to our support team. We respond through the same channel you used to contact us.

PRIVACY CONTACT PATHS

How to Reach Us About This Policy

All privacy-related questions, correction requests and data enquiries go through the contact routes below. Use the route that suits you; every channel connects to the same support team handling account and data matters. We ask that you include your account identifier in any message so we can locate your record without delays.

  • Live chat

    Open the live chat from any page while logged in to raise a data or privacy question directly. It connects to the account support team who can pull up your record during the session.

  • Email support

    Send your privacy request or correction query to our support email address shown in the Help section of your account. Include your account identifier and the specific data point your question concerns.

  • Help centre

    The Help section inside your logged-in account lists the published contact options and links to this policy. Start there if you want to understand the process before submitting a formal request.

HOW WE PROTECT DATA

Data Handling, Cookies, Security and Retention at 2p888

Knowing the mechanics behind how we protect your data matters as much as reading the policy text. Here is how we approach four key areas on the account and payment side of 2p888.

  • Cookies and session tracking

    We use session cookies to keep you logged in and functional cookies to remember your account preferences. Analytics cookies help us understand how the site is used in aggregate. You can manage non-essential cookies through your browser settings; removing session cookies will log you out.

  • Payment data and wallet records

    When you deposit or withdraw via bKash, Nagad or Bank Transfer, we record the transaction reference and status returned by the payment provider. We do not store full mobile wallet credentials or bank account numbers in our own database beyond what the session requires.

  • Account security and access controls

    Your account is protected by login credentials you set at registration. We recommend using a strong, unique password and reviewing your account activity regularly. If you notice an unfamiliar session or transaction, contact support through the routes listed on this page immediately.

  • Retention and how to request changes

    We keep account and transaction data for as long as it is needed for the purpose it was collected or as required by applicable law. Once retention obligations end, data is deleted or anonymised. To request a review of what we hold, use the support contact route described in this policy.

POLICY FAQ

Common Questions About the 2p888 Privacy Policy

These are the questions we hear most often about how data is handled on the account and payment side. If your question is not here, the support contact route is the right next step.

What personal data does 2p888 collect when I open an account?

We collect the information you enter at registration — name, contact details and login credentials. Once you make a deposit via bKash, Nagad or Bank Transfer, we also hold the transaction reference and status returned by the payment provider for that transfer.

Can I see what data 2p888 holds on my account?

Yes. Log in and open account settings to review the profile fields we currently hold. For a fuller picture of transaction records or session data, submit a request through the live chat or email support route and include your account identifier.

How do I correct information that is wrong on my account?

Contact support through live chat or email with your account identifier and the specific field you want corrected. We check it against your registration record and update what is within our control. Fields tied to identity verification may require additional steps shown in your account.

Does 2p888 share my data with third parties?

We share limited data only where needed — for example, with payment processors handling bKash, Nagad or Bank Transfer transactions, or with fraud-screening services protecting your account. We do not sell your data to advertisers or unrelated third parties.

How long does 2p888 keep my account and payment data?

Retention periods depend on the type of data and the legal or operational reason we hold it. Transaction records may be kept longer than general profile data due to applicable financial obligations. Once the retention period ends, data is deleted or anonymised.

Who do I contact if I have a privacy concern or want to request deletion?

Use the live chat or email support route listed in the Help section of your account. Include your account identifier and describe what you need. We handle all data requests through these published routes; we do not accept requests through unverified channels.