Sports / App
This is the pg444 Privacy Policy, and it covers what we collect when you open an account, add funds through bKash or a bank transfer, and move through the lobby on your phone. Read it before you sign in, so you know which records you can open yourself and which choices sit with you.
Privacy rules differ from one country to the next, and we do not pretend otherwise. pg444 sets this policy out as a plain statement of how we handle personal data, and we apply it alongside whatever your local law and eligible regions require. Where a rule in your country gives you a stronger right than this page describes, that local rule takes priority and shapes how we answer you. In practice it comes down to the details you hand us and the records your payments leave behind. Creating an account means typing in your own details: your name, contact number, date of birth as you enter it, and the login you will use again next week. Adding funds is different, because the rail you pick writes its own trail. A bKash Send Money confirmation arrives with a reference number, and a bank transfer comes with a deposit slip carrying a and a transaction ID. We keep those transaction records so your wallet history matches what you see on screen, and so we can trace a specific deposit when you ask about it. This page is not a contract that overrides your legal rights, and it is not a promise about anything beyond data handling. Payment availability, game availability and account eligibility depend on your local law and eligible regions, and they can differ from one person to the next. When a question turns on your country's rules rather than ours, we say so instead of guessing, and we point you to the route that can confirm it.
Not every screen you touch falls under the same document, so it helps to know where the line sits. This policy covers the personal data tied to your account: the details you type in, the login records that show when you signed in, and the transactions that appear in your account wallet. It also covers the messages you send us, because a support thread usually carries the account details we need to trace your case. What sits outside is just as important. When you open bKash or your bank's transfer screen, that provider handles your data under its own terms, and we only see the confirmation it returns to us. Any external site you reach from a link in our lobby works the same way. Your device settings, permissions, saved passwords and browser cookies, belong to you and your phone, not to this policy. Session activity also differs by game category. A live table session and a sportsbook entry leave different records on our side. The four cards below set out what each part of the site means for your data.
Login data and profile fields sit here. That means the email or phone number you sign in with, your password, and the records that show when your account was opened. If you ever see a sign-in you do not recognise, this is the data to raise through a support route.
Deposits and withdrawals shown in your account wallet. A bKash deposit carries a reference number from the Send Money confirmation, and a bank transfer carries a transaction ID from your deposit slip. We keep these records so you can line your account history up against your own receipts.
Pages you open, games you launch and preferences you set while signed in. This layer keeps your lobby familiar between visits. If you would rather leave a lighter footprint, browser and device settings let you clear cookies and decide what is remembered on your phone.
Payment providers, external links and your device's own settings all run on separate terms. We do not control what bKash, your bank or another website records, and this policy ends where their screen takes over from ours. Ask them directly about their own handling.
A policy is only worth reading if you can act on it, so here is what you can actually ask for. You can request the personal data we hold about your account, and you can open much of it yourself: profile details, wallet history and the transactions tied to your bKash or bank transfer deposits. You can correct details that have gone stale, such as a contact number you no longer use, and you can close an account instead of leaving it idle. When something looks wrong, write through a route published on this page and describe it plainly: which deposit, which date, which reference number. One clear line usually tells us more than a long message. If you want data removed, say so directly. We will explain what we can action and what we have to keep for transaction records. And if a request falls outside what we can do, we tell you why, then point you to whatever route your local law offers.
Profile details, wallet history and transaction lines are already visible once you sign in. Read them first, because the reference number on your own bKash confirmation often answers the question on the spot and makes any follow-up with our team faster.
You can request the personal data we hold about your account, and we will set out what we keep and why. Nothing here is meant to be hidden from you; the point is that you can see your own records and compare them with your receipts.
Changed your phone number or spotted a misspelled name? Tell us and we will work the correction through with you. Good contact details also matter for account security, since they are how we reach you about activity on your login.
You can ask us to delete personal data that is no longer needed. Certain transaction records have to stay for as long as accounting and dispute rules require, and we will tell you plainly which part we can remove and which part stays.
Policy questions land with the same team that handles account help. The contact form on this site is the plainest route: choose the closest category, describe your question in your own words, and add the reference number or transaction ID if it concerns a bKash deposit or a bank transfer. If you are signed in, the help link inside your account keeps the conversation attached to your profile, which saves you repeating your details. Use the support address published on the site when you need to send a screenshot of a deposit slip or a document relating to your account. Keep the subject line short and say what outcome you want: a correction, a record, or an answer about how we handle data. We reply to the contact details on your account, so keep them current. We do not publish fixed response times, and we would rather say that honestly than mislead you. If your question is really about another provider's app or your bank's own records, we will tell you so and point you their way.
Found on this page and across the site. Choose the closest category, describe the issue in your own words, and attach the reference number or transaction ID if a deposit is involved. You can use it without signing in, so a privacy question never has to wait.
The support address published on this site. Use it for screenshots, deposit slips and anything with an attachment. Keep the subject line short, name the account you are writing about, and tell us what you want changed or explained. We answer to the contact details held on your account, so keep those up to date.
Signed in, the help link sits inside your account area and keeps your message tied to your profile. It suits questions about a specific login, a wallet line or a session you do not recognise, because we can already see the account it belongs to.
We collect what an account needs to function: your login details, the profile fields you fill in, your wallet history and the references your payments create. That data lets us run your account, match a deposit to your record, reply to your messages and keep your lobby looking the way it did last time you signed in. Cookies do a smaller job than most people assume. They keep you signed in between pages, remember a preference you set, and tell us which sections load slowly on a mobile connection. Clear them through your browser at any time and the site simply asks you to sign in again. Account security is shared work: we hold your login on our side, and you keep your password private and tell us if a session looks unfamiliar. We keep personal data while your account is open and for the period afterwards that transaction and dispute records require. If you want something changed or removed, use a published support route; we will explain what we can action and what has to stay.
Login details, profile fields, wallet history and payment references. We use them to run your account, trace a deposit you ask about and keep your lobby consistent between visits. You can ask to see this data, or read most of it yourself after signing in.
Cookies keep you signed in between pages, remember a setting you chose and show us which sections run slowly on mobile. Clear them in your browser whenever you like; the site will ask you to sign in again, and nothing else about your account changes.
Your login belongs to you. Keep the password private, sign out on shared devices, and contact us if a session or a wallet entry looks unfamiliar. If your contact number changes, update it so we can still reach you about activity on the account.
We keep personal data while your account is open, and for the period afterwards that transaction and dispute records require. Ask for a correction or a removal through a published support route and we will explain what we can action and what must stay.
A privacy page should answer the questions people actually type, not the ones that sound impressive on paper. Every question below is about your data rather than about payments or games, though a few touch the records a payment leaves behind. Below are the ones we get asked most: what data we hold, how long we keep it, what you can change and who you write to. Read them in order or jump to the one you need; each answer stands on its own. If your question is about a specific deposit, a bKash reference number or a bank transfer transaction ID, have those details ready before you write in; it turns a slow exchange into a single clear reply. Nothing on this page changes your rights under the law where you live, and where the two differ, local law and eligible regions decide how we handle your request.
It covers the personal data we collect through your account: your login details, profile fields, wallet history and the references your payments create. It also covers your messages to our team. Payment providers, external links and your device's own settings sit outside it. Eligibility itself depends on your local law and eligible regions.
Yes. Much of it is already in front of you once you sign in: your profile details, wallet history and transaction lines. For anything else, ask through a published support route and we will set out what we keep and why we keep it.
We keep personal data while your account remains open, and for the period afterwards that transaction and dispute records require. We do not publish a single fixed number, because it depends on the records involved and on local accounting rules. Ask us about a specific record if you need clarity.
Cookies keep you signed in between pages, remember a preference you set, and show us which sections load slowly on mobile. You can clear them through your browser at any time. The site will then ask you to sign in again, and nothing else about your account changes.
Use the contact form on this site, the support address published there, or the help link inside your signed-in account. Keep the subject short and include a reference number or transaction ID if a deposit is involved, so we can trace the record you are asking about.
Access to pg444 depends on your local law and eligible regions, so part of the answer sits with where you are. Where we cannot offer an account, this policy does not create one. Where we can, it applies to the data we collect through your account, wherever you happen to be signing in from.