Live / App
255ok sets out the terms, rights and responsibilities that shape how your account is created, used and protected. Access to this platform and eligibility to participate depend on your local law and the regions in which our services are available.
These terms govern your relationship with 255ok from the moment you open an account. They cover how we collect and use information shared during account registration, how transactions processed through bKash, Upay or Bank Transfer are recorded in your account history, and what obligations both sides carry. We do not make legal certainty claims about access from any region — your eligibility depends entirely on the laws applicable where you are located. If a provision in these terms conflicts with a law in your jurisdiction, that local law takes priority, and the remaining provisions continue to apply. We update these terms when our services or applicable requirements change. When we do, the revised version will be published here with a clear indication that it has changed. Continuing to use the account after that point means you have reviewed and accepted the update. If anything in these terms is unclear, the right route is to contact our support team directly rather than act on an assumption. We keep a record of major term versions so you can ask to see what applied at any earlier point in your account history. Payment context chips below reflect the rails we support.
bKash transactions made through your account are logged in your account history. These records are available for you to review at any time from the transaction section of your account.
Upay transfers follow the same account-record rules. Each transaction entry shows the amount, direction and status, giving you a clear reference when you need to raise a question with support.
Bank Transfer records are held in the same account transaction log. If a transfer status appears incorrect, the policy support route is the correct first step before escalating further.
Not every element of your experience with 255ok falls under the same policy provisions. Understanding the scope helps you know which route to take when a question comes up — whether that is an account matter, a payment record, a content query or something involving a third-party service linked through our platform.
Login, account registration, session controls and wallet-linked actions all fall within this policy. Any access eligibility question — including whether you can use the platform from your region — is addressed here and depends on your local law and eligible regions.
Payments processed via bKash, Upay or Bank Transfer sit within the scope of our terms. Transaction records are maintained in your account, and any dispute about a recorded amount is handled through the policy support route outlined in the support section.
Game content available in the lobby — from studios including Habanero, CQ9, Microgaming and Bigtime Gaming — is subject to provider-level terms alongside ours. We do not override individual provider content policies, but we do handle access-level questions on your behalf.
Links or integrations that direct you away from 255ok, such as external payment gateways or identity verification services, are governed by their own terms. We cannot accept policy responsibility for those external steps, though we can help you understand what to expect before you reach them.
Your rights under these terms are practical, not abstract. You can review your account transaction records at any time — every bKash, Upay or Bank Transfer entry is listed in the account history section with its status and amount. If a detail recorded against your account is incorrect — name, contact email or wallet reference — you can request a correction by contacting support with the relevant information. Raising a formal policy question follows a clear path: open a support request, state the specific issue and reference any transaction ID or session date that applies. We treat every policy request as a documentation matter, which means we keep a record of it and follow it through to a resolution. You are not required to accept a decision without further review — if the initial response does not address the question, you can ask for escalation within the same support thread.
Open the transaction section of your account to see every payment entry — bKash, Upay and Bank Transfer records are all listed there with status and date. No separate request is needed to view your own history.
If your registered contact, name or wallet reference is incorrect, contact support directly with the correct information and your account reference. We will update the record and confirm the change in writing.
Submit your question through the published support route and reference the specific term or transaction you are asking about. A policy question logged this way creates a documented thread that you can refer back to at any stage.
If an initial support response does not resolve your policy concern, ask within the same thread for the matter to be reviewed at a higher level. We document escalation requests and respond through the same contact channel.
Policy questions have a specific contact path at 255ok. Use the routes below for account, transaction or terms-related queries. We do not publish operating hours or response-time commitments we cannot verify — what we can confirm is that each route produces a documented record of your request.
The live chat option in your account dashboard is the fastest way to raise a policy question. State the specific issue at the start of the conversation so the agent can open the correct documentation thread immediately.
For formal policy requests — including correction of account details or questions about your transaction record — submit by email through the address listed in the contact section of the site. Include your account reference and the relevant transaction ID.
The support ticket form inside your account is the recommended route for matters that need a written record. Each ticket is assigned a reference number, allowing you to track the status and refer back to the thread at any point.
We handle account and payment data according to the terms published here, and we do not share your information with parties outside the scope described in our privacy provisions. Cookies are used for session management and account authentication — you can review and manage cookie preferences through your browser settings. Account security is your shared responsibility: we protect the account infrastructure, and you control access credentials. If you believe your account has been accessed without your authorisation, report it immediately through the live chat route so we can act on it without delay.
Account and transaction records — including bKash, Upay and Bank Transfer entries — are retained in line with the period stated in our terms. You may ask to see what we hold about your account by submitting a request through the email contact route.
We use cookies to keep your session active and to remember your account preferences across visits. The full list of cookies in use and how to manage them is covered in the cookie section of our published privacy terms.
Your account password and wallet-linked credentials should not be shared. If you receive a message asking for your login details that does not come from a verified 255ok contact route, report it immediately through the support ticket form.
Any request to change recorded account data — contact details, wallet reference or registered name — must come through the published support contact route with sufficient identification. We do not process change requests made through unverified channels.
These questions cover what we hear most often about account rights, data, eligibility and how to raise a formal policy request. If your question is not addressed here, the support ticket route produces a documented response.
Eligibility to access 255ok and the applicability of these terms depend on the laws in force where you are located. We do not make blanket eligibility claims — if you are unsure whether access is permitted under your local law, review your regional legal position before opening an account.
We retain major versions of our terms. Submit a request through the email policy contact route with your account reference, and we will confirm which version was in effect when your account was created and what the main provisions stated at that time.
Contact support through live chat or the support ticket form. Include your account reference and specify the field that needs correcting — name, contact email or wallet reference. We will update the record and send a written confirmation once the change has been made.
Your full transaction log — covering bKash, Upay and Bank Transfer entries — is available in your account's transaction section without any separate request. For a formal policy dispute, reference the specific transaction ID in your support ticket so we can locate the relevant record quickly.
Ask for escalation within the same support thread. A documented escalation request is reviewed separately from the initial response. We keep a record of every stage so the matter can be traced from the original question through to the final outcome.
Submit a data access request through the email contact route published in the site's contact section. Include your account reference and we will confirm what information is held, the period it covers and the categories of data retained in line with our stated terms.