Slots / App
11ff is committed to being clear about what data we collect, why we collect it, and how you can review or correct it. Access to our platform depends on your local law and eligible regions, and this policy sets out the exact controls available to you.
When you open an account on 11ff, we collect certain information to operate your session correctly and keep your wallet activity on record. This includes your registration details, your payment method context — such as whether you use Nagad, Upay or Bank Transfer — and the device identifiers associated with your logins. We do not sell this data to third parties, and we do not use it for purposes outside those described in this document. Cookies and session tokens help us remember your device so you do not have to re-enter credentials on every visit; you can manage cookie preferences through your browser settings at any time. Transaction records linked to your account wallet are retained for the period required by the platform's operational obligations. If you add a mobile number or email address during account setup, that contact detail is used for account verification and support communication only. We review this policy when our platform changes, and the version published here reflects current practice. Your continued use of the platform after any update constitutes acknowledgement of the revised terms. If you have a question about a specific data point we hold, the support routes in this document are the right place to start.
Not every interaction on the platform falls under the same policy rules. Understanding which areas this document covers — and which sit outside it — helps you know where to go when a question comes up. Four distinct areas are outlined below.
This policy covers data collected during login, session activity and account registration. It includes device tokens, login timestamps and any contact detail you provide. Account access availability depends on your local law and eligible regions.
Records of deposits and withdrawals processed through Nagad, Upay or Bank Transfer sit within this policy's scope. We hold transaction references to support account queries. We do not store full payment credentials on our own servers.
Game session data — rounds played, session duration, feature triggers — is recorded for account integrity and fair-play purposes. This applies to all game categories available in the lobby. RTP data is shown only where the game provider exposes it directly.
Links to external sites, payment gateways operated independently, and any service outside the 11ff domain are not covered by this policy. Those services have their own privacy terms. We recommend reviewing them before sharing data with any external provider.
You have real, usable choices when it comes to the data 11ff holds against your account. Reviewing those choices does not require a formal legal process — most actions are handled through your signed-in account area or by contacting support directly. Start by checking the account settings page after logging in; the profile section shows the contact details, device records and notification preferences currently linked to your account. If any detail is inaccurate — a phone number, an email address, or a payment method label — you can flag it for correction through the support channel. We aim to acknowledge data correction requests and route them to the right team. Retention periods vary by data type: session logs are kept for a shorter period than transaction records, which must be held longer for operational reasons. If you want to know exactly how long a specific record type is kept, ask support and we will check the current schedule. Eligibility to exercise certain rights depends on applicable local law in Bangladesh and the regions where the platform operates.
Log into your account and open the profile or account history section. Your registered contact details, session history and linked payment methods are visible there. If something looks wrong, note the specific field before contacting support.
Send a correction request through the published support route. Describe the field and what the correct value should be. We route these requests to the account team and confirm once the update is applied.
If you want to understand why a specific piece of data was collected or how long it will be retained, open a support ticket with your account reference. We will pull the relevant policy section and respond with the applicable answer.
For anything that requires account-level action — linking a new Nagad number, updating a Bank Transfer reference or querying a wallet entry — the support routes below are the starting point. Keep your account ID ready when you reach out.
If your question concerns data stored against your account, a payment record linked to Nagad or Upay, or a correction you need made, these are the routes we publish for support. Use the channel that fits your query type and have your account reference available.
Open the chat widget from any page on the platform while signed in. Describe your data or account query and the agent will pull your record directly. This is the quickest route for straightforward correction requests.
For detailed privacy queries — retention periods, data correction confirmations or written records of your request — send an email through the contact address shown in your account area. Include your account ID and the specific data point in question.
The help section inside your signed-in account lists common data and policy questions with step-by-step answers. Check there first; if your question is not covered, escalate to live chat or email using the links provided on that page.
Knowing how your data moves through the platform is part of using it with confidence. The four areas below cover our approach to each key part of the data lifecycle.
Session cookies keep your device recognised between visits so your account state loads correctly on mobile or desktop. You can clear or block cookies through your browser at any time; doing so may affect how the account area behaves on your next visit.
Passwords are stored in hashed form and never in plain text. Login attempts that exceed the threshold shown on the login page trigger a verification step. If you notice an unrecognised login, report it through live chat immediately so the account team can review the session log.
Transaction records — including those tied to Nagad, Upay or Bank Transfer deposits — are held for the period our operational obligations require. Session and activity logs have a shorter retention window. Ask support for the current schedule for any specific record type.
If your circumstances change and you need to update the data we hold — a new contact number, a revised Bank Transfer reference or a change to your notification settings — submit the request via email support with your account ID. We confirm updates once applied.
These questions cover what our members in Bangladesh ask most often about how their data is handled, what rights they have, and how to act on those rights through the platform.
We collect your email address, a contact number, and the device information associated with your login. If you add a payment method like Nagad or Upay, the reference details for that method are also linked to your account. We collect only what is needed to operate your account correctly.
Yes. Log into your account and open the profile or account history section to view your registered details, session records and linked payment references. For a more detailed breakdown of a specific data category, raise the request through live chat or email support with your account ID.
Transaction records — including those from Nagad, Upay and Bank Transfer activity — are retained for the period required by our operational obligations. The exact schedule for each record type is available on request. Contact support and reference the specific transaction type you are asking about.
This policy covers data collected and held by 11ff directly. Payment gateways operated independently — including those used to process Nagad or Bank Transfer instructions — operate under their own privacy terms. We recommend reviewing those terms on the relevant provider's published page.
Send a correction request through live chat or email support. Describe the field that contains the error and provide the correct value. The account team reviews the request and confirms once the update is applied. Keep your account ID ready so the team can locate your record quickly.
We do not sell your data to third parties. Data may be shared only where required to operate the platform — for example, routing a payment instruction — or where applicable law in Bangladesh and eligible regions requires disclosure. We do not share data for advertising purposes outside our own platform.