Live / App
Your account data on af44 belongs to you — we keep the controls visible and the support route one tap away. Access to certain features depends on your local law and eligible region.
Privacy on af44 starts with your account — the information you submit when you join, the wallet records tied to bKash, Rocket, or Upay transactions, and the session activity logged while you browse the lobby. We do not sell your details to third parties.
The privacy controls on af44 are built around what you can actually reach inside your account. Knowing where each control sits — and what it does — means you are never guessing about your own data.
Your name, contact number, and registered wallet identifier — bKash, Rocket, or Upay — appear in the profile section. You can review these at any time after logging in. To update a field, follow the edit prompt shown next to it and confirm the change through the verification step the system displays.
Every wallet movement — deposits and withdrawals processed through bKash, Rocket, or Upay — is logged in the transaction history tab. The record shows the amount, channel, date, and status.
Your login history and session activity are stored and visible in the account security section. If you spot a session you do not recognise, the log shows the device type and timestamp.
How we contact you — and how often — is controlled through the notifications section of your account. You can adjust which categories of account communication reach you. Changes take effect from the next scheduled send; the section shows the current preference state so you always know what is active.
Privacy terms are only useful if you can find them quickly. On af44, the published policy sits in the footer of every page — no account login required to read it. For account-specific data questions, the relevant section is inside the logged-in account panel.
The full privacy terms are accessible from the footer on every page of af44 — desktop or mobile browser. No login is needed to read the policy. The link is labelled clearly and opens the current published version, not a cached copy.
After logging in, the account settings panel shows the data fields we hold for your profile. This is where you review or update stored information. The panel reflects the live state of your account; changes made here are applied immediately and confirmed with an on-screen status message.
Your bKash, Rocket, and Upay payment records are stored in the transaction tab of your account. Each entry is time-stamped and shows the channel used. These records are the primary reference point when our support team investigates a wallet query on your behalf.
Any privacy or data query you raise through the published support route is logged. You can refer back to the conversation thread inside your account's support history. This applies whether you contacted us via live chat or the submitted-ticket route shown on the support page.
If a privacy question comes up — a data field you want corrected, a transaction record you need explained, or a session you do not recognise — the support routes below are how you reach us.
Open the live chat icon visible in the bottom corner of the account area after you log in. State that your query is about account privacy or data, and the team will pull up your prof
For written privacy requests — such as asking what data we hold or requesting a correction — use the ticket form on the support page. Include your registered wallet channel (bKash, Rocket, or Upay) so the team can locate your account without you needing to share sensitive details in the message body.
If you need to act on a privacy concern immediately — such as a session you do not recognise — the account security section has a built-in prompt. Use it to flag the session before you contact support. This creates a timestamped record that the support team can reference when they follow up.
Trust around privacy is built on things you can verify, not statements you have to take on faith. Each point below corresponds to something you can check directly — either in the published terms, inside your account, or through
The privacy policy is in the public footer — no login, no search needed. Open it from any page to read the current version.
Your bKash, Rocket, or Upay transaction log inside the account is the primary evidence layer. Every deposit and withdrawal is recorded with a timestamp and status.
The session activity section of your account shows each login event — device type and time. This is not summarised or filtered; you see the full log.
If a data field in your profile is wrong, the correction process is documented in the account settings panel itself — not buried in a separate help article.
Some terms in a privacy policy read cleanly the first time; others need a plain-language version alongside them. The definitions below cover the terms that come up most often when you are reading the af44 privacy terms or asking our support team a data question.
Personal data is any information that can identify you — your name, phone number, email, or registered wallet number (bKash, Rocket, Upay). It covers both what you submit directly and what the platform records from your activity.
A data controller is the entity that decides why and how your personal data is used. On af44, this is the platform operator. The controller is named in the published privacy terms, which are accessible from the site footer without logging in.
Data processing covers any action taken on your data — collecting it, storing it, using it to run your account, or referencing it when our support team resolves a query. Your wallet transaction records are processed each time a bKash or Rocket movement is logged.
A session log is a record of each time you log into your account, including the device type and timestamp. It is stored in the account security section and is used to help you spot activity you did not authorise.
A third party is any organisation outside af44 that may receive your data. The privacy terms specify which categories of third party are involved and why. We do not sell your details; third-party references typically cover payment processing infrastructure.
A data correction request is a formal ask to change information we hold that is inaccurate. You can initiate this from the account settings panel or by submitting a support ticket. Include your registered wallet channel so the team can locate your profile quickly.
The questions below are the ones that come up most often when you are navigating privacy settings or reading through the published terms on af44. If your question is not covered here, the support routes listed in the support section above are the right next step.
Log in and open the account settings panel. The fields shown there reflect your stored profile data. For transaction records, go to the transaction history tab — every bKash, Rocket, or Upay movement is lis
Yes — open the profile section inside your account settings. Each editable field shows an edit prompt next to it. Follow the verification step displayed on screen to confirm the change.
Your bKash, Rocket, and Upay transaction records are visible to you in the transaction tab and to af44 support staff when they are handling a query you have raised.
Open the account security section and review the session log. Note the timestamp and device type of the unrecognised entry. Use the security prompt on that page to flag it, then contact support through live chat or a ticket. Having the log entry details ready speeds up the team's investigation.
Wallet processing requires sharing the transaction-relevant details with the payment channel you use — bKash, Rocket, or Upay. This is limited to what is needed to complete the movement. The published privacy terms in the site footer describe the scope of this sharing; availability depends on your local law and eligible region.
Submit a written request through the ticket form on the support page. State clearly that you are requesting account data deletion and include your registered wallet channel to help the team identify your