Casino / Live
ber1111 explains here how your account details, wallet activity and site usage are handled. This page covers what we collect when you open an account, how payment records like Nagad and Upay transfers are stored, and what choices you have over your own data.
This privacy policy sets out how ber1111 handles the records tied to your account, your device and the payment routes you use to fund it. We collect what's needed to open and verify an account: your registration details, login activity, and the records created when you move money through Nagad or Upay into your account wallet. We do not sell this data to outside parties for marketing use. Where you access our platform from Bangladesh, how this policy applies — and whether certain account features are available to you — depends on your local law and the regions we are permitted to serve at any given time. If eligibility rules change in your area, access to parts of the lobby or to payment routes may change accordingly. We keep transaction records, including Nagad and Upay references, for as long as needed to resolve a dispute, answer a support query, or meet a request from a payment partner. Cookies and device data help us keep your session signed in and recognise returning account holders; you can clear these through your browser at any point. This policy does not cover the internal systems of Nagad, Upay or other payment providers once a transfer leaves our platform — those providers hold their own policies for the data they process. If any term here conflicts with a mandatory local rule, the local rule takes priority for users in that region.
Not every page or feature on ber1111 sits under the same information rules, and that's worth spelling out plainly. Account access, payment transactions, the content inside the lobby and services run by outside partners each carry a different scope — some generate records we hold directly, others pass through a partner system we don't control. We've split these four areas out below so it's clear what sits where. Reading through them helps you understand where to look if you have a question about a specific piece of data: your login history, a Nagad or Upay reference number, or a cookie set while you were browsing a game page such as Roulette Winner's Wheel or Football Oddszone. If a topic isn't covered in one of these four areas, it generally falls outside what this particular policy addresses, and a separate published document may apply instead.
This policy covers the records created when you register, sign in or update details on ber1111 — your login activity, device type and account settings. It does not extend to any other account you hold elsewhere; what happens outside our platform sits with that other service's own policy.
We hold records of transfers made through Nagad or Upay into your account wallet — amount markers, timestamps and reference numbers used for support and dispute checks. We do not control how Nagad or Upay process a transfer on their own systems once it leaves our platform.
Pages, game listings and lobby text fall under this policy only where they collect data — session cookies, search terms typed into the lobby, or display settings you choose. Game screens such as Cricket FastPlay or Crash Bangladesh Arena do not create separate records beyond ordinary play activity shown in your account.
Services run by payment partners or identity-verification tools sit outside this policy once data passes to their own systems. Game providers whose titles appear in our lobby supply game content only; we do not share your account data with them, and they do not process payments or identity checks on ber1111.
You're not locked out of your own account record. Inside your account area you can check the personal details you registered with, see the device and login history tied to your profile, and check the payment references created by Nagad or Upay transfers. If something looks wrong — a misspelled name, an old phone number, a payment reference that doesn't match — you can raise it through the support route listed in your account rather than waiting for us to notice. We treat a correction request and a general question the same way: both go through the same support channel, and we look at account records before replying. Keeping your own details accurate also helps us resolve a wallet or login issue faster, since a mismatched detail is one of the more common reasons a support query takes longer to close. This applies whether you reach us from a mobile browser or desktop, since your account record stays the same across devices.
Open your account area to see the registration details, device history and payment references tied to your profile, including entries created by Nagad or Upay transfers into your account wallet.
If a name, number or contact field is wrong, use the support route inside your account to ask for a correction rather than registering a second account.
Questions about how we hold your data, cookies or payment records can be sent through the same support channel used for account and wallet queries.
After you raise a question or correction, follow up through the same support route shown in your account until you get a reply tied to your account record.
Questions about this privacy policy don't need a separate form. We route them through the same support paths you'd use for an everyday account or wallet query, so there's one place to check instead of several scattered contact points. Whether you're asking about a cookie, a login record, or a reference tied to a Nagad or Upay transfer into your account wallet, start from the support option inside your account if you're already signed in. If you're still deciding whether to open an account, the contact page listed on our site accepts the same kind of question before you register. We look at the account record tied to your request before replying, which is also why including a payment reference number speeds up the match. This applies equally if you reach us from a phone browser or from desktop, since your account carries the same record either way.
The quickest path for a privacy question is the support option inside your signed-in account. Open it, describe what you want corrected — your registration details, device history or a payment reference — and we'll match your request to the account record on file.
If you haven't opened an account yet, the contact page listed on our site lets you send a privacy-related question before registering. Tell us what detail you're asking about — a cookie, a login record or a payment entry — so we can route the question properly.
For a question tied to a specific Nagad or Upay transfer into your account wallet, include the reference number shown on that transaction. It helps us match your query to the exact record instead of searching through general account activity.
Keeping your account data in order is part of running ber1111 day to day, not a separate task we do once a year. Login details, device data and payment references from Nagad or Upay transfers sit inside your account record, and we hold onto them as long as needed to answer a support query or resolve a dispute over a transaction. Cookies on our site keep your session active so you're not asked to sign in again every time you switch between a slot room and a sportsbook page. Account security on your end starts with the basics — a password you don't reuse elsewhere and a device you trust — and we recommend checking your account activity now and then for anything that doesn't look familiar. If you want a change made to how your data is held, the same support route covers that request, and we match it against the record tied to your account.
We keep registration details, device and login history, and payment references created by Nagad or Upay transfers into your account wallet. This data supports account verification, dispute resolution and support replies — we don't sell it to outside marketing lists.
Cookies keep you signed in as you move between a casino table and a sportsbook page, and they remember basic display settings. You can clear cookies through your browser settings at any time; doing so may sign you out of your account the next time you visit.
A trusted device and a password you don't reuse elsewhere are the first line of protection for your account. We recommend checking recent login activity in your account area and raising anything unfamiliar through the support route straight away, before making another deposit or transfer.
We hold account and transaction records for as long as needed to answer a support query or meet a request from a payment partner like Nagad or Upay. If you want a record corrected or removed where possible, raise it through the support route in your account.
Here are the privacy questions we hear most often from people opening or using an account on ber1111. If your question isn't answered below, the support route inside your account or the contact page on our site takes it from there, and we'll match your question to the record tied to your account.
We collect the registration details you provide — name, contact details and login credentials — along with device and session data created while you use the site. Payment references from a Nagad or Upay transfer into your account wallet are also kept as part of your account record.
Yes. Open your account area to check registration details, login history and payment references tied to your profile. If something looks incomplete or you want a fuller look, raise a request through the support route in your account and we'll check the record directly.
We share only what's needed to process a transfer you initiate — enough for Nagad or Upay to match the payment to your account wallet. We don't pass your wider account data, like browsing activity or game history, to either payment provider.
Open the support route inside your signed-in account and tell us what needs fixing — a misspelled name, an outdated contact number or a mismatched payment reference. We check the request against your existing account record before applying any change.
How this policy applies, and whether certain account or payment features are available to you, depends on your local law and the regions we are permitted to serve at any given time. Access can change if local eligibility rules change.
Clearing cookies through your browser settings removes the session markers that keep you signed in and remember display preferences. You'll likely be asked to sign in again next time, but your underlying account record and payment history stay stored as before.