Sports / App
This page sets out the legal framework that governs your use of sn22, including how we handle your account data, what scope our policy covers, and how to reach us when you have a question. Access to sn22 depends on your local law and the eligible regions we serve.
sn22 operates under terms that are shaped by the jurisdiction in which you access the platform. Whether you use Nagad, Rocket or another supported method to fund your account, the same policy framework applies to every transaction and every account action recorded on the platform. We do not make blanket legal assurances about access from every location — if local law in your region restricts online account activity of this kind, it is your responsibility to check before proceeding. We ask that you read these terms carefully and keep a note of any reference number provided when you raise a query with our support team. Our policy covers the data we collect during account registration, the records generated by wallet activity such as Nagad transfers and Rocket payments, and the communication logs created when you contact support. Third-party payment processors operate under their own terms; our policy governs only the data that passes through the sn22 account layer. Changes to these terms are published on this page and take effect from the date shown. Continuing to use your account after that date means you have accepted the updated terms.
Our policy has a defined scope. Understanding what falls inside and outside it helps you know which route to take when you need to raise a concern or correct a record.
Policy covers all actions taken through your registered sn22 account — login activity, profile changes, wallet top-ups via Nagad or Rocket, and session records. Access eligibility still depends on your local law and the regions we serve.
Deposits and withdrawals processed through the sn22 account layer fall within policy scope. The records we hold include the method used, the amount and the timestamp. Third-party processor terms sit outside our scope and are governed separately.
Game content provided by studios available in the lobby — including titles from JDB, CQ9 and Bigtime Gaming — is subject to those studios' own content terms. Our policy governs how your interaction data with that content is recorded, not the content itself.
Links or redirects to external services, including payment processor portals, fall outside our direct policy scope. We do not control the data practices of those third parties, and we recommend you review their terms independently.
You have specific, actionable rights under the policy we maintain for your account. These are not abstract — each one maps to a real step you can take by signing into your account or contacting our support team directly. If you need to review the data we hold on you, the account settings area shows the profile information and transaction history we have on record. Corrections to your registered details — such as your contact number or linked wallet reference for Nagad or Rocket — can be requested through the support route described below. Where you believe a record is inaccurate, raise the point in writing through our published contact channel, quoting your account reference so the team can locate the record without delay. You may also request that we clarify which data categories we hold, how long we retain them, and whether any of your data has been shared with a third-party processor. Responses are handled through the same support route.
Sign into your account and open the transaction history section to see the payment records we hold, including Nagad and Rocket activity. For full data export requests, use the published support contact route.
To update registered details — contact number, linked wallet or email — log in and navigate to the account settings page. Changes that affect verification may require you to confirm identity through the steps shown there.
Any question about how we handle your data, what we retain and why, or whether your account action falls within scope can be submitted through our support channel. Quote your account reference in the message for a faster response.
If you believe your rights under this policy have not been respected, contact us using the routes listed in the support section below. We treat policy-related queries as a separate queue so they reach the right team member.
Policy questions have a dedicated path. Use only the routes published on the site; we do not accept policy or data requests through unofficial channels. Each route below is visible and active from your account area.
Open the live chat window from the account area to raise a policy question directly with the support team. Identify your query as a policy matter at the start of the conversation so it is routed correctly.
For written policy requests — including data correction or scope clarification — use the email address published in the site's contact section. Include your registered account reference in the subject line.
The Help Centre accessible from your signed-in account lists policy topics, account steps and published terms. Check there first; if the answer is not shown, escalate using live chat or email.
We take a direct approach to the data we hold: collect what is needed for account function, retain it for the period required, and give you a clear path to review or correct it. The following areas cover the main categories you are likely to ask about.
Account records — including registration details and wallet transaction logs covering Nagad and Rocket activity — are retained for the period set out in our published terms. After that period, records are deleted or anonymised in line with our internal data schedule.
We use cookies to maintain your session, remember your account preferences and measure site performance. You can manage cookie preferences through your browser settings. Disabling all cookies may affect how your account page loads and how your session is maintained.
Your account is protected by the login credentials you set at registration. If you suspect unauthorised access, change your password immediately through the account settings page and contact support using the live chat route to flag the incident.
When we update these terms, we publish the revised version on this page with a date. If you have a question about a specific change, contact us through the published email route and reference the section you are asking about.
These questions cover the policy topics we hear most often. If your question is not listed here, use the support routes above to reach the team directly.
Access and applicability depend on your local law and whether Bangladesh falls within our eligible regions. We do not make blanket claims about legal access from every location. Check the current policy terms and consult local rules before using the account.
We hold the details you provided at registration, your login and session records, and transaction logs for wallet activity including Nagad and Rocket payments. You can view your transaction history directly from the signed-in account area at any time.
Log into your account and navigate to the settings page to review your registered information. For changes that affect your linked wallet reference or verification status, contact support through live chat or email and quote your account reference in the message.
The records generated by Nagad and Rocket deposits and withdrawals at the sn22 account layer fall within our policy scope. The payment processors themselves operate under their own separate terms, which we do not govern or represent.
Retention periods are set out in the published terms on this page. After the applicable period, records are deleted or anonymised. If you want to know how long a specific data category is retained, submit a written query through the email support route.
Raise the matter through the published support channel — live chat for an immediate conversation or email for a written record. State clearly that your query is a policy matter and include your account reference. The team routes policy questions separately from general account queries.