Sports / App
Your account data on jetbuz123 is collected only for what the platform needs to run — login access, wallet verification and session continuity across your devices.
The privacy framework on jetbuz123 applies to every interaction your account has with the platform — from the moment you log in on mobile to the point where a wallet transaction is recorded against your session.
The privacy policy is structured around four practical areas that affect your account directly. Each one maps to something you can verify by opening the relevant section in your account settings or the published terms p
When you register or verify your wallet — whether through Upay or Bank Transfer — you share contact and identity details. These are held only for account operation and the verification requirements shown in your account settings. Nothing extra is retained beyond what the process needs.
Your device type, browser version, IP address and session timestamps are logged automatically each time you connect. This data supports account continuity across mobile and desktop, so your lobby state and game history remain consistent. You can review the specific fields in the published policy.
Retention periods vary by data type. Active account data is held while your account remains open. Transaction records linked to Upay or Bank Transfer payments follow the retention schedule set out in the terms. Closed accounts follow the deletion timeline described in the policy footer section.
Data is shared only with the service providers that run the platform's core functions — payment processing, identity verification and fraud detection.
The controls available to you are straightforward and accessible directly from your account page. You do not need to contact support to use most of them — the account settings panel covers the actions listed below.
Open your account settings and navigate to the data section to see what information is recorded against your profile. The view covers contact details, device records and transaction history linked to your wallet, including Upay and Bank Transfer entries.
Your registered contact information can be updated from the account page. Changes take effect on the next login. If a verification step is required — for example, after a wallet method change — the account page will display the fields and instructions for that step.
A deletion request can be submitted through the support route published in your account. Processing timelines depend on your account status and any outstanding transaction records. The policy document details which data categories can be deleted and which must be retained by law.
Cookie settings are managed through the consent layer shown on your first visit and are adjustable from the site footer at any time. Functional cookies required for login and session continuity cannot be switched off, but analytics preferences can be changed without affecting your account access.
If the published privacy document does not answer your question directly, or if you need to action a specific request — such as correcting a data record or following up on a deletion — the support routes below are the published channels for privacy-related queries.
Most data queries — viewing your records, updating contact details or checking what wallet information is stored — can be handled directly from the account settings page without opening a support ticket. Start there before reaching out.
For requests that require manual review — data deletion, objection to processing or a formal access request — use the support contact route published in your account footer. Include your registered contact detail so the team can locate your record without delay.
The full policy is linked from the site footer and from your account settings page. It is the authoritative reference for retention periods, sharing categories, and the legal basis for processing. Check it first — most specific questions are answered there in plain language.
Transparency in a privacy policy means more than a published document — it means each claim in that document points to something you can verify yourself.
The privacy document is not buried in a generic legal archive. It is linked directly from your signed-in account footer, so you can reach it without leaving the platform.
Each data type — contact details, device identifiers, payment records for Upay and Bank Transfer, session logs — is named separately in the policy rather than grouped under a vague um
The policy states that access and data rights depend on local law and eligible regions. For Bangladesh, the relevant sections describe what applies to your account.
The sharing section of the policy lists each category of recipient by purpose — payment processing, fraud checks, account verification — with no catch-all clause that allows marketing use. If the purpose changes, the policy must be updated and you are notified through the contact detail on your account.
These definitions cover the terms you are most likely to encounter when reading the privacy policy or managing your account data settings. Each one is written in plain language so you can match the term to what it means for your account specifically.
The data controller is the entity that decides why and how your personal data is collected and used. On jetbuz123, that is the platform operator. The controller's identity is named in the published privacy document linked from your account footer.
This is the legal reason a platform is permitted to handle your data — such as fulfilling a contract, meeting a legal obligation, or acting on your consent. The policy lists the basis applied to each data category so you know which applies to your account records.
A DSAR is a formal request you submit to see the personal data held about you. You can ask what data exists, why it is held and who it has been shared with. The process and identity verification steps are described in the privacy policy support section.
Retention period is how long the platform keeps a specific type of data after it is collected. Transaction records, session logs and contact details each have different retention schedules. The privacy document sets these out by data category, not as a single blanket timeframe.
A cookie is a small data file stored on your device by the browser. Functional cookies keep your login session active and your lobby state consistent across pages. Analytics cookies track usage patterns and can be adjusted from the site footer consent settings.
A third-party processor is a company that handles data on the platform's behalf — for example, a payment verification service for Upay or Bank Transfer. They act under the controller's instructions and are listed by purpose in the privacy policy's sharing section.
These are the questions we hear most often about account privacy on jetbuz123. Each answer points to a specific action or document section so you are not left with a vague direction.
Payment method records linked to Upay or Bank Transfer are retained for the period specified in the privacy policy's transaction data section. They are held for account verification and fraud prevention purposes, not for marketing. You can view what is stored from your account settings panel.
Yes. A deletion request can be submitted through the support channel published in your account footer.
Data rights and platform obligations depend on local law and eligible regions. The policy references Bangladesh-specific conditions where they differ from the general terms. Read the jurisdiction section of the published document to understand what applies to your account based on where you access the platform.
The document carries a version date at the top. When the policy changes, the updated version replaces the previous one at the same footer link, and the date changes.
Game studios including CQ9 and PG Soft supply game content to the lobby. They do not receive your personal login or session data from jetbuz123. The sharing section of the privacy policy lists each recipient category by purpose — game studios are not included in the data-sharing scope.
Contact the support route published in your account footer with your registered contact detail and a description of the concern. The privacy policy also references the formal complaint process for data handling disputes. Processing and response steps depend on the nature of the request and applicable local requirements.