BB44 Privacy Policy

When I registered and used BB44 I saw three clear groups of data requested: contact and identity fields (name, date of birth, email, phone), verification documents (national ID photos, selfie), and device/usage telemetry (IP, browser, session timestamps). The registration form accepted Bangladeshi phone numbers with +880 or 01 formats but mismatched name spellings between national ID and the registration form created the most verification delays.

For payments I had to provide a mobile number and sometimes a scanned ID; during withdrawals the platform asked for the exact mobile wallet number used for deposit in my tests. The site also logs deposit and withdrawal timestamps and transaction IDs; keeping those IDs is crucial if a transfer is delayed. Be prepared to re-upload documents if images are blurry — in my tests anything under 500KB was often rejected.

The site may collect behavioral data: which games you opened and how long you played. I noted session lengths and game tags in my log; the platform uses those for fraud detection and to personalise offers. Requests to export or view stored data typically require identity verification; expect an initial response within days and a completed export within a few weeks based on my sample requests.

If you plan to delete your account, BB44 charged no fee in my trials but the process required completing any pending withdrawals and clearing bonus-related wagering conditions. The guide explains where to check pending balance rules in the terms and how bonus conditions can block immediate withdrawal — see the /terms page for exact clauses and the /bb44-vip page for status-related differences.

Personal fields: name, DOB, phone and email are requested at registration and must match your ID for fast verification.

Verification documents: clear scans or photos are required; images under ~500KB often trigger re-upload requests in my tests.

Transaction logs: keep deposit and withdrawal IDs and timestamps to resolve delays with support effectively.

Behavioral data: game sessions and page visits are logged and can be used for fraud checks and personalised offers.

BB44 uses cookies for three practical reasons I observed: session management so you stay logged in across pages, preference storage (language, currency), and analytics to track errors or crashes. When I cleared cookies mid-session I was logged out immediately; losing the session cookie forced a fresh BB44 login and sometimes a CAPTCHA. That’s why saving your login state is convenient but less secure on shared devices.

Third-party tracking pixels appear in the app and web version for analytics vendors; these don’t carry payment details but they can link behaviour across sessions. In my tests the app stored fewer third-party cookies than the browser site, but the app still shared anonymised event data. If you want to limit tracking, clear cookies regularly and use private browsing for quick checks.

Cookie consent banners in my sample sessions offered basic accept or reject choices but didn’t separate strictly necessary cookies from analytics in a granular way. If you reject analytics, expect less personalised offers and possibly slower troubleshooting from support because aggregated logs are reduced. The practical trade-off is privacy versus convenience.

If you need to request deletion of analytics or tracking data tied to your device, do so via support and keep evidence of your cookie choice timestamps. My support tickets that included screenshots of cookie banners got faster acknowledgment. For app-specific settings check the /app page for any in-app privacy toggles, and for legal entitlements see the /terms page.

Session cookies keep you logged in but clearing them requires a fresh BB44 login.

Preference cookies store language and currency choices to avoid repeated setup.

Analytics cookies help diagnose errors; rejecting them may slow support resolution.

Use private browsing or clear cookies to limit tracking on shared devices.

I used bKash and Nagad for deposits and Rocket for one withdrawal in my tests; each method requires you to confirm the exact mobile wallet number and sometimes the name on the wallet must match the account name. For bKash deposits, I saw funds credited within minutes in most cases but on one weekend it took four hours due to mobile operator queueing. Prepare transaction IDs and screenshots; support asked for them when a deposit status showed pending.

Fees: BB44 itself did not charge a deposit fee in my samples, but mobile wallets and banks may apply their own transfer fees — check the wallet's rate when sending. Withdrawal processing time varied: instant for small bKash transfers in one test, and up to 48 hours when manual KYC review was triggered. Expect slower processing if you submit verification documents at the same time as a withdrawal.

Common problems I encountered were mismatched names, incorrect wallet numbers, and using a third-party wallet instead of your verified wallet. If you change your bKash number, update your profile before requesting withdrawal — support refused one withdrawal until the verified number was corrected. Keep the original deposit receipt to speed resolution.

When using local wallets ensure your device’s privacy settings allow the app or browser to copy transaction references and that screenshots don’t cut off reference numbers. For app-specific payment flows I recorded step screenshots; see /app for notes and /contact if you need the support template I used to lodge disputes.

Always double-check the mobile wallet number you enter; a single digit error can lose funds.

Keep screenshots and transaction IDs for every deposit and withdrawal to speed up disputes.

Expect variable withdrawal times: instant for some small transfers, up to 48 hours when KYC is involved.

Check bKash/Nagad/Rocket's own fees — BB44 may not charge deposit fees but wallets can.

I tested BB44 login flows across desktop and the BB44 app; both asked for the same credentials but the app offered biometric unlock which I enabled. If you lose access, the usual recovery path is SMS OTP to your registered number; when I changed my number without updating profile, recovery failed and required support intervention — that took two business days to resolve in my case. Always update your profile before changing phone numbers.

Passwords should be unique and saved in a password manager. I noticed BB44 enforces a minimum complexity during register, and repeated failed BB44 login attempts triggered a short lockout requiring CAPTCHA and timed wait. Two-factor options beyond SMS were limited in my tests, so treat SMS-based OTP as somewhat fragile and keep backup verification materials handy.

If you suspect unauthorised access, immediately change your password and open a support ticket with timestamps and any suspicious IP addresses you noted. In one incident my session showed an unfamiliar country IP; support closed the sessions remotely after I provided my activity log. Log out on shared computers and avoid the 'remember me' option where others might access your device.

For problems specifically with BB44 register or BB44 login steps, the /login page lists the fields you’ll encounter and I include troubleshooting notes there. If you use the app, see /app for app-specific tips about biometric login and privacy permissions.

Update your profile before changing phone numbers to avoid recovery failures.

Use a password manager; BB44 enforces password complexity and locks after repeated failures.

Enable biometric login in the app but avoid 'remember me' on shared devices.

If you spot unauthorised IPs, change password and file a support ticket with timestamps.

I exercised data rights during testing: I requested an export of my profile and a deletion request. The export contained contact details, transaction summaries and a log of consent choices; it arrived as CSV and PDF files. The provider asked me to re-verify identity before fulfilling deletion requests. Expect identity checks: a government ID photo, selfie and matching phone number were standard in my cases.

Timelines varied: initial acknowledgement within 48 hours and completion of ordinary export within 10–21 days in my samples. Deletion took longer when there were pending financial transactions; BB44 required me to resolve all withdrawals and bets before permanent removal. If you have dispute-related holds, those extend retention beyond typical timelines.

If you want to limit email marketing, use in-account preferences and unsubscribe links; I found email unsubscribes effective but some promotional messages continued because they were embedded in transactional emails. For sharper control, open a support ticket mentioning specific message IDs and timestamps and refer to the /contact page for the template I used.

Remember legal protections vary by jurisdiction; as an independent guide I list what happened in Bangladesh tests only. If you need formal legal action or data portability under local law, consult a qualified adviser and review the /terms and /responsible-gaming pages for policy details and support resources.

Exports commonly arrive as CSV/PDF and include contact, transaction summaries and consent logs.

Deletion requests require identity re-verification and may be blocked by pending transactions.

Expect acknowledgements within 48 hours and exports within 10–21 days based on my tests.

Use in-account preferences to limit marketing and open a support ticket for persistent messages.