App / Slots
acl444 collects only the account and transaction data needed to run your wallet, process bKash or Upay transfers and keep your session secure. This policy explains exactly what we hold, why we hold it and what you can do about it — availability of our services depends on your local law and eligible regions.
When you open an account with acl444, we collect the registration details you enter — your name, contact address and the credentials you set. When you fund your account through bKash, Upay or Bank Transfer, we record transaction references so your wallet balance stays accurate and disputes can be resolved. We also collect device and browser session data — the type of device, the browser version and your IP region — to detect unusual access patterns and protect your account from unauthorised login. Cookie data tied to your session is used to keep you signed in and to remember your lobby preferences between visits; it is not used for cross-site advertising profiling. We do not share identifiable account data with advertising networks. Data shared with payment processors like bKash or Upay is limited to what those processors need to confirm your transfer. Any third-party processor we work with is bound by its own published terms, and we recommend you review those separately. Retention periods follow the operational need: active account data is held while your account is open; transaction records are held for the period required to resolve disputes and meet applicable reporting obligations in your region. All access and data use depends on your local law and eligible regions.
This policy covers the data acl444 collects directly through its site and account system. It does not extend to third-party services you reach through links on our pages — those services run under their own policies. Check each section below to understand what falls inside and outside this policy's reach.
Data collected when you register, sign in or update your account details is fully covered by this policy. That includes your email, contact details and any security credentials you set inside the account area.
When you move funds through bKash, Upay or Bank Transfer, we record the reference and amount on our side. The payment processor holds its own record under its own terms — this policy covers only our copy of that data.
Session cookies, lobby navigation events and device data collected while you browse acl444 fall inside this policy. We use this data to improve how the site loads and to keep your session active while you switch between sports and casino sections.
Any external link, payment gateway page or game studio content served from a third-party domain is outside this policy's scope. We cannot control how those services handle your data and recommend you read their own disclosures before interacting with them.
You have clear, actionable options for the data acl444 holds on your account. Reviewing your stored details starts inside the signed-in account area — the profile section shows the registration information we hold and lets you correct a wrong name, contact address or email directly. If a correction is not available through self-service, you can raise a request through the support channel shown on our contact page and we will update it on the back end. For questions about what specific data we hold or why a particular record exists — for example a bKash transaction reference you do not recognise — our support route is the right place to ask. Requests to close your account and remove data that is not required for ongoing dispute resolution or legal reporting obligations are also handled through the same support channel. Response timing depends on the nature of the request; we do not commit to a fixed hour window, but we do action each request in the order it arrives.
Open the account profile page once signed in. Your name, contact details and registered email are displayed there. Check them at any time without contacting support.
Edit fields directly in the profile section for most details. If a field is locked, raise a correction request through the support channel and include the detail that needs updating.
Send a data enquiry through our published support route. Describe the data type or transaction reference in question — for example a Upay deposit record — so we can locate it accurately.
Contact support with a written closure request. We will process it and confirm what data, if any, must be retained under applicable regional reporting requirements before deletion.
If your question is about data held on your account — a transaction record, a stored detail or a deletion request — use the contact routes below. We handle each privacy enquiry separately from general account help so it reaches the right team without delay. Availability depends on your local law and eligible regions.
Open the chat window visible on the acl444 site while signed in. Describe your privacy question clearly — include the data type or transaction reference — so the team can locate your record.
Send your privacy request to the email address shown on the published contact page. Use a subject line that names the request type, such as data review or account detail correction.
The help section inside your signed-in account area lists the steps for common privacy requests, including how to update your contact address or ask about a bKash transaction reference on file.
acl444 applies access controls and session security measures to limit who can read account records internally. Cookies are scoped to the session and the lobby preference function — they are cleared when your session ends or when you clear your browser data manually. Retention is tied to operational need: we do not hold data longer than the period required to keep your account functional or to meet applicable regional obligations.
Session cookies keep you signed in and remember your lobby state while you browse between sports markets and casino sections. They are not used to build an advertising profile. Clear your browser cookies at any time to remove them.
Access to your account data inside acl444 systems is restricted to the roles that need it for wallet operations, transaction verification and support. Unusual login attempts from unexpected device regions trigger access checks.
Active account data stays on file while your account is open. Transaction references — including bKash and Bank Transfer records — are kept for the period needed to resolve disputes. Data not required for those purposes is removed on account closure.
When this policy changes in a material way, we post the updated version at this page path. Continuing to use your account after an update is posted means you have seen the revised terms. Check this page periodically if you want to stay current.
Real questions about the acl444 privacy policy, answered directly. If your question is not here, use the support contact route shown above.
We collect the name, contact address and login credentials you enter during registration. We also record the device type and IP region of each login to detect unusual access. We do not collect more than we need to run your account and wallet.
We share transaction references with payment processors like bKash or Upay only to the extent needed to confirm your transfer. We do not sell your identifiable data to advertising networks. Any processor we work with handles data under its own published terms.
Sign in and open the profile section — most details can be edited directly there. If a field is locked, contact support through the chat window or email route shown on our contact page and describe the correction you need.
Transaction references — including bKash, Upay and Bank Transfer records — are kept for the period needed to resolve disputes and meet applicable regional reporting obligations. Once those periods pass, records not required for open matters are removed.
Yes. Send a written closure and deletion request through the published support route. We will confirm what data, if any, must be retained under regional obligations before we process the deletion. All other data is removed on account closure.
No. External links, payment gateway pages and any content served from a third-party domain fall outside this policy. We recommend reading each external service's own privacy disclosure before you interact with it, as we cannot control how those services handle your data.