Casino / Slots
p2226 collects only what it needs to run your account and keep your session secure. This policy explains what we hold, why we hold it, and the steps you can take to review or correct it — availability depends on your local law and eligible regions.
When you open an account with us, we collect the registration details you enter — name, contact information and the payment method you connect at that point. If you use Nagad or Upay as your deposit rail, we record the transaction reference that those services return to us; we do not store your mobile wallet credentials or PIN. Session data such as device type, browser and approximate region helps us keep your account accessible across visits and flag unusual access attempts. We also retain records of account activity — deposits, withdrawals and support messages — for as long as your account remains active and for a period after closure as required by applicable rules. We do not sell this data to third parties for advertising. Where we share data, it is with payment processors like Nagad and Upay to complete a transaction you initiated, or with infrastructure providers who operate under confidentiality obligations. Cookies and similar tools track session state and page behaviour; you can adjust these through your browser settings at any time. Your rights and our obligations under this policy depend on your local law and the eligible regions from which our service can lawfully be accessed.
This policy covers the data we process directly through p2226. It does not extend to every service you might reach from our pages — third-party payment processors, linked sites and any external app store operate under their own separate policies.
Data collected when you register, log in or update your account details falls fully within this policy. This includes the email address, contact number and payment method reference you provide during setup.
Deposit and withdrawal records processed through Nagad or Upay are covered here to the extent we hold them. The payment service itself processes your wallet credentials under its own terms, which sit outside our policy.
Browsing behaviour on our pages — which sections you visit, how long you stay, which game lobby areas you open — is captured by our session tools and governed by this policy, including cookie preferences you set in your browser.
Any service you reach by following a link away from p2226, including external payment apps, is outside the scope of this policy. We recommend you read the privacy terms of those services separately before sharing personal information there.
You have practical options for managing the data we hold. Start from your account settings page, where the details you entered at registration are displayed and can be edited directly — name, contact information and preferred language. If you spot an error in a transaction record tied to a Nagad or Upay deposit, raise it through our support route and include the transaction reference shown in your account history; we will check it against the payment processor record and correct any discrepancy on our side. For broader questions — what data we hold, how long we keep it, or a request to close your account and have records handled according to applicable rules — send a written request via the contact route below. We aim to respond within a reasonable period, though the exact timeframe depends on the nature of the request and the requirements that apply to your region. Eligibility to exercise these rights depends on your local law.
Open account settings to see the registration details and transaction history we hold. The display reflects the current state of your account; if anything looks wrong, the correction path is one step away.
Edit your name, contact number or email directly in the account settings fields. Changes take effect immediately. If a field is locked, raise a support request with the correction you need.
Send any privacy question to our support contact with your account reference and a clear description of the data point in question. We will locate the relevant record and respond with what we hold.
A written closure request sent via support starts the process. We handle the records left after closure in line with applicable rules for your region and the timeframes those rules set out.
All privacy-related requests go through the contact routes below. Use the one that suits how you prefer to communicate — each route connects to the same team handling account and policy queries.
Open the chat widget from any page while signed in. Share your account reference and describe your privacy question; the team will pull up your record from there.
Send a written request to the support address shown in the Contact section of the site. Include your registered contact number and, if relevant, a Nagad or Upay transaction reference for the specific record in question.
The Help section accessible from your signed-in account lists the current published routes and any updated contact details. Check there first if you are unsure which route to use.
We apply access controls so that your account data is reachable only through authenticated sessions. Cookie preferences you set in your browser are respected across your visits, and session tokens expire after a period of inactivity to reduce risk from shared devices.
We keep your account records while your account is open and for a defined period after closure, in line with applicable rules. Transaction references from Nagad or Upay payments are part of this record and are held accordingly.
Our pages use cookies for session management and basic analytics. You can adjust or withdraw cookie consent through your browser settings at any time; this does not affect your ability to access your account.
Access to your data within the platform requires a signed-in session. Unusual login attempts from unfamiliar devices trigger a review step visible from your account security page. We do not store wallet PINs or credentials for Nagad or Upay.
When this policy changes in a way that affects your rights, we post the updated version on this page and note the revision date at the top. Continuing to use your account after an update means you have had the opportunity to review the changes.
These are the questions we see most often about how p2226 handles account data. If your question is not here, reach us through any of the contact routes listed in the support section above.
We collect the name, contact number and email address you enter during registration. If you connect a Nagad or Upay account for deposits, we record the transaction reference returned by that service — not your wallet PIN or login credentials.
Yes. Open account settings while signed in to view your registration details and transaction history. For a broader picture of everything we hold, send a written request through live chat or email support with your account reference included.
Editable fields — name, contact number, email — are available directly in account settings. If a field is locked or the error is in a transaction record, raise a support request with the specific correction and we will check the record and update it.
We share only what is necessary to complete a service you requested. Payment references go to Nagad or Upay to process a transaction. Infrastructure providers handling hosting or security operate under confidentiality obligations. We do not sell your data for advertising.
Records are retained for a defined period after closure in line with applicable rules for your region. The exact duration depends on local law and the type of record. You can ask for details by contacting support with your account reference and closure date.
Check the login history shown in your account security page. If you spot an access you did not make, change your password immediately and contact us through live chat. Include the date, time and device shown in the record and we will investigate from our side.