App / Live
At 0777bt, your account data is handled with a clear set of rules — what we collect, why we hold it, and how you can act on it. Access and eligibility depend on your local law and the regions we serve; this policy sets out exactly where those boundaries sit.
This privacy policy describes how 0777bt collects, uses and retains information when you access our platform, create an account, or carry out a transaction. Information we collect includes the details you provide during registration — your name, contact details and account credentials — alongside transaction records generated when you use Nagad, Upay or Bank Transfer to move funds through your wallet. We also collect technical data: device type, browser session identifiers and IP address, which help us keep your account accessible across devices and detect unusual access patterns. We do not sell your personal data to third parties for marketing purposes. Retention periods vary by data type: transaction records connected to Nagad, Upay or Bank Transfer are held for as long as required by the applicable financial and legal obligations in the regions we operate. You can request a summary of what we hold at any time through the support route listed on this page. This policy applies where local law and eligible regions allow, and we update it when our practices or obligations change — the current version is always available here.
Not every element of your interaction with the platform falls under this policy in the same way. The table below sets out four distinct areas so you know exactly what is and is not within scope. Understanding the scope prevents confusion when you raise a data question with our support team.
Login activity, session data and device identifiers tied to your account are within scope. We record when and how you access your account so that unusual access can be flagged and your session history is available for review on request.
Payment records — including transfers through Nagad, Upay and Bank Transfer — are within scope. These records are held as required by applicable financial obligations and are accessible to you through the account support route.
Browsing behaviour on our platform — pages visited, time on site and navigation paths — is collected in aggregate for operational purposes. This data is anonymised at the aggregate level and does not identify you individually in reports.
Links to external sites, third-party payment processors and services operated outside our platform are not covered by this policy. Those services operate under their own privacy terms, which you should review separately before providing information to them.
Several practical steps are available to you as an account holder. You can request a copy of the personal data we hold about you at any time — this includes registration details, transaction history connected to Nagad, Upay or Bank Transfer, and session records. If any of the information we hold is incorrect — for example, an outdated contact number or a misrecorded account detail — you can ask us to correct it through the support route. Where data is held beyond what you consider necessary, you can raise a deletion or restriction request; we will assess it against our retention obligations and respond with a clear outcome. All requests are handled through the published contact path, not through in-lobby chat. Eligibility to exercise these rights depends on local law and the region your account falls under, and we will tell you clearly if a specific request falls outside what we can action in your jurisdiction.
Submit a data access request through the published support route. We will provide a summary of the personal data held on your account, including transaction records and session identifiers, scoped to what is held at the time of the request.
If a name, contact detail or account field is recorded incorrectly, notify us through the support channel. We will verify the correction against your account and update the record where the change is eligible under our verification process.
Questions about how a specific piece of data is used — for example, why a device identifier is retained or how a Nagad transaction record is categorised — can be directed to the policy contact route listed in the support section of this page.
For broader account concerns that touch on data handling — such as understanding what is visible to our support team when you contact us — open a support request referencing your account ID so the right team can respond with accurate, account-specific detail.
Data and privacy requests follow a specific contact path, separate from general account queries. Use the routes below to ensure your request reaches the right team. All three routes are published on the platform; we do not accept data requests through social media or anonymous channels.
Submit a data request through the account support form in your profile area. Include your registered contact detail and a clear description of the data question or correction you need so the team can respond to the right record.
Open the live chat from any page on 0777bt and identify your request as a privacy or data matter. The agent will log it and route it to the appropriate team; response time varies depending on the type of request submitted.
For written records of data requests, use the email contact published in the help section. Write clearly that you are raising a privacy matter, include your account username, and allow the team time to verify your identity before responding.
These four areas explain how we manage the information your account generates. Each point reflects current platform practice, not a general statement — if any of these practices change, this policy page is updated and the change is noted.
We use session cookies to keep your account accessible as you move between pages and to remember your device so you do not need to re-authenticate on every visit. You can manage cookie preferences through your browser settings; disabling certain cookies may affect how the platform functions on your device.
Account credentials are stored using standard encryption practices. We do not display your full password to any team member; support agents can verify identity through account-level signals without seeing your login credential directly. Unusual login activity triggers an account flag visible in your session history.
Transaction records — including those linked to Nagad, Upay and Bank Transfer — are retained in line with applicable financial and legal obligations for the regions we operate. Non-transactional data such as browsing behaviour is held for a shorter operational period and is not linked to your named account in aggregate reports.
When this policy changes in a material way, we update this page and note the change at the top of the document. We do not send automated alerts for minor wording updates; significant changes that affect your rights or our data practices are communicated through your account notification path.
The questions below cover what account holders most often ask when they read this policy. If your question is not here, the support contact routes above are the right next step.
We collect the details you provide during registration — typically your name, contact information and account credentials. We also record device identifiers and session data at the point of login. This information is used to operate your account and is not shared with third parties for marketing.
Yes. Payment records connected to Nagad, Upay and Bank Transfer are stored as part of your account transaction history. These records are held for as long as required by applicable financial obligations in your region. You can request a copy through the account support form.
Submit a data access request through the account support form or the email contact route listed in the support section. Include your registered username and specify that you are requesting a personal data summary. We verify your identity before releasing any information.
Yes. If a contact detail or account field is recorded incorrectly, contact us through the support channel and identify it as a correction request. We will verify the change against your account and update the record where it is eligible under our current verification process.
The policy applies where local law and eligible regions allow. Certain rights — such as deletion requests — may be subject to local legal obligations that affect what we can action. If a specific request falls outside what we can complete in your jurisdiction, we will tell you clearly and explain why.
We update this page when the policy changes. For material changes that affect your rights or our data practices, we send a notification through your account. Minor wording or structural updates are made to this page without a direct account notification, so checking this page periodically is worthwhile.