Slots / App
job3 publishes this legal page so you can read exactly where our obligations begin, where yours do, and how the two connect. Access to our platform and its account functions depends on your local law and the eligible regions we serve — we encourage you to review this page before opening or using an account.
Our legal position starts with a clear acknowledgement: what you can access on job3 depends on the laws and regulations applicable in your location and the eligible regions we currently serve. We do not represent that every feature, game category or account function is universally available, and we do not override local law. Where we collect information — including the wallet identifiers associated with bKash, Rocket or Upay transactions — we handle that information under the data retention and privacy commitments described in our published policy documents. Those documents are the authoritative source; this page summarises the key user-facing obligations in plain language. If a conflict exists between this summary and the full policy text, the full text applies. We update our legal documents when our operations or applicable frameworks change. When an update occurs, we post the revised version and note the change date at the top of the relevant document. Continuing to use your account after a policy update means you have had the opportunity to review the revised terms. If you have a question about a specific clause — for example, how your bKash wallet identifier is stored or how long a Rocket transaction record is retained — the support routes listed on this page are the correct place to raise it.
Transaction identifiers linked to your bKash wallet are retained in line with our published data retention schedule. You can request a summary of what we hold through the support route listed on this page.
Rocket payment references are stored as part of your account transaction log. We do not share these references with third parties outside the scope described in our full privacy document.
Upay transaction records follow the same retention rules as other wallet methods. If you close your account, we retain only what applicable policy requires and delete the rest on schedule.
Not every part of your experience on job3 falls under the same policy clause. This section maps the four main areas so you know which document governs each one. Reading this before raising a question saves time for both of us — you reach the right policy route faster, and we can respond to the correct team.
Creating, suspending or closing an account on job3 is governed by our Terms of Use. Access itself depends on your local law and eligible regions. The Terms of Use page sets out the exact eligibility conditions we apply at account level.
All payment activity — including deposits and withdrawals via bKash, Rocket or Upay — is covered by our Payment Terms and the transaction records visible in your account history. We do not adjudicate disputes outside those published terms.
The games available in our lobby, the categories shown and the studios whose content appears — including Pragmatic Play, Habanero and others on our platform — are governed by our Content and Availability notice. Studio availability can vary by eligible region.
Links to external sites, payment processors or identity verification providers are not covered by job3 policy. Those third parties publish their own terms, and we cannot be responsible for how they handle your information once you leave our platform.
This policy is not passive reading — it describes real steps you can take at any point. Reviewing your stored account data, correcting details that are out of date, raising a formal question about how we handle your information, and requesting account-level support are all available to you through the routes we publish. Start with your account dashboard, where your profile information and transaction history are visible. If the detail shown is wrong — for example a name or contact address linked to your account — you can submit a correction request through the support channel. For questions about data retention, what we hold and why, or requests that go beyond a simple account update, the legal contact route is the appropriate path. We aim to acknowledge formal policy questions within the timeframe stated in our published response commitment, though we do not invent or guarantee a specific hour count here. What we can confirm is that every request is logged and reviewed by the team responsible for that policy area.
Log in and open your account history to see the transaction records we hold, including wallet references from bKash, Rocket or Upay sessions. This is the starting point before raising any formal query.
If your name, contact address or wallet identifier is recorded incorrectly, submit a correction through the support channel. Attach the relevant account reference so the team can locate your record without delay.
For questions specifically about data handling, cookie use or retention periods, use the legal contact route rather than general support. This reaches the team with authority to answer those questions directly.
Account-level actions — including review of access decisions — are handled through the published support route. Describe the specific action you need so the team can route your request to the right area.
If a question goes beyond what you can resolve in your account dashboard, these are the published contact paths for policy and legal matters. Use the route that fits your question — general account support differs from a formal data or legal query, and routing correctly means a faster response.
The live chat widget on job3 connects you to the account support team for day-to-day queries — wallet issues, account access questions and general policy clarifications. Open the chat from any page while you are signed in.
Formal policy questions — data requests, retention queries, correction requests that require documentation — should come through the email address published in our Privacy Policy page. This route reaches the correct team directly.
The help centre on job3 covers common policy questions in structured articles. Search by topic — account data, wallet records, cookie settings — before opening a contact request, as many answers are already published there.
Understanding exactly how we manage what we collect is part of the trust relationship we want with every account holder. This section covers the four main areas: data handling, cookies, account security and who holds responsibility for each.
We collect the information you provide and the transaction records generated by your activity, including wallet references from bKash, Rocket and Upay sessions. Retention periods are published in our Privacy Policy and follow applicable framework requirements for the eligible regions we serve.
We use cookies to keep your session active, remember your language setting and understand how pages are used. The Cookie Notice on job3 lists each category of cookie, its purpose and how to manage or withdraw consent through your browser settings.
Your account is protected through the authentication steps visible on the login page. We do not store payment credentials directly — wallet references such as your bKash or Rocket identifiers are handled through the payment processing layer described in our Payment Terms.
Requests to change how we handle your data — including objections to processing or requests for deletion — go to the email address in our Privacy Policy. We log every request and respond through the same channel so you have a written record of the exchange.
These are the questions we receive most often about our legal framework, user rights and data practices. If your question is not here, the support and legal contact routes listed above are the right next step.
Access to job3 and the applicability of our policy depends on your local law and the eligible regions we serve. We recommend reviewing the Terms of Use and checking whether access is permitted under the laws that apply in your location before creating or using an account.
We hold the profile information you provided when registering, your transaction history — including wallet references from bKash, Rocket or Upay sessions — and technical session data. Log in and check your account history page for a direct view of the transaction records we hold.
Retention periods are set out in our published Privacy Policy and follow the requirements applicable to our eligible regions. The specific period depends on the type of record. For a precise answer tied to your account, submit a query through the legal email route.
Yes. If your name, contact detail or wallet reference is recorded incorrectly, open a correction request through the support channel. Include your account reference and the specific detail you want corrected so the team can locate and update your record without delay.
Open the Cookie Notice linked in the site footer. It lists each cookie category and explains how to manage or remove consent through your browser settings. Withdrawing consent for non-essential cookies does not affect your ability to log in or view your account.
Formal requests — data access, deletion, objections to processing — go to the email address published in our Privacy Policy page. That route reaches the team with authority to respond. General account support through live chat handles day-to-day queries but cannot process formal legal or data requests.