Sports / Slots
ok63 sets out in this Privacy Policy how we collect, store and use the details tied to your account — from the sign-up fields you filled in to the bKash and Rocket transaction records linked to your wallet. We keep this page as the single reference point for what we do with your data and how you can ask us about it.
This Privacy Policy applies to every account opened on ok63 and to the data generated while you use it — login sessions, game history, and the payment trail attached to deposits and withdrawals made through bKash or Rocket. We do not treat this page as a one-time read: the terms here describe how account data is handled for as long as your account stays active, and what happens to records once it doesn't. Because online account access sits under local law, what we can show you, and how long we keep certain records, depends on your country's rules and whether your region is eligible to hold an account with us at all. We note this plainly rather than assume one blanket rule fits everyone. Where a payment rail like bKash or Rocket is used to fund or withdraw from your wallet, the transaction reference generated by that method becomes part of your account record and is handled under the same data principles set out here — not under a separate, looser standard. If a law in your jurisdiction requires a different disclosure or a stricter data rule than what's written on this page, that local law takes precedence over our general wording. We'd rather be upfront about that than word this policy as if one version applies everywhere.
This policy covers the account you hold with ok63 and the data tied to it — not every corner of the internet you reach through it. Inside scope: the sign-up fields you filled in, your login sessions, and the transaction trail attached to bKash and Rocket payments moving in and out of your wallet. Inside scope too: which lobby pages and game rooms you open, used only to keep your account history straight, not to make claims about outcomes. Outside scope: the internal data handling of a payment processor once money leaves their system and reaches your account as a confirmed entry — we describe what happens on our side, not theirs. Access to any of this, and how long certain records are held, depends on your local law and whether your region is eligible to hold an account with us at all. We keep the boundary clear so you know where this page stops applying.
Covers how we record sign-in attempts, device sessions and the login credentials tied to your account, so repeated access from the same profile always stays linked to one consistent record instead of scattered, disconnected entries across different sessions and devices.
Covers the bKash and Rocket references generated when you move money into or out of your wallet — these sit inside your account history and fall under this policy, not a separate payment-only notice that applies elsewhere on the site.
Covers which lobby pages and game rooms you open, used only to keep your account history accurate; it does not extend to claims about odds, outcomes or RTP beyond what a game or provider itself discloses, and never implies a result.
Where a service outside ok63 — such as a payment processor — handles part of a transaction, that provider's own data handling sits outside this page's scope; we only describe what we do once that data reaches your account record.
You're not locked out of your own account record. If something in your profile looks off — a saved name, a contact detail, a mismatched wallet reference — you can ask us to look at it rather than guess at a fix yourself. The same goes for questions about why a particular bKash or Rocket entry appears the way it does on your account: raise it through a published support route and reference the transaction so we're both looking at the same record. We built this policy page around the idea that account data should be checkable, not just stored. None of this requires you to submit anything beyond what you already use to sign in and manage your wallet. A short message with the right reference usually gets you a closer look at the exact entry in question.
Open your account area to check the login history and payment trail linked to your profile, including bKash and Rocket references tied to past transactions.
Contact us through a published support route if a saved detail on your account — contact info, wallet reference, profile field — needs correcting.
Ask us directly if you're unsure why a record exists or how long it's kept; reference the account and transaction so we can locate it.
If an earlier question wasn't resolved, follow up through the same support route and reference your account so the thread stays connected.
Privacy questions don't need a separate form — the same support route you'd use for an account or payment question works here too. If your question touches a bKash or Rocket entry, keep the reference number handy so whoever picks up the message can match it against your account straight away. We'd rather you ask early than sit on a question about how your data is handled; a short note pointing at the exact record — a login date, a transaction reference, a saved detail — gets you a clearer answer than a general message. None of the routes below promise a fixed response window; we're simply telling you where a privacy question actually reaches us, using the contact paths already published on the site, rather than a channel we're inventing for this page. That keeps the answer tied to your actual account instead of a generic reply.
Use the contact route published on ok63 to send a privacy question tied to your account. Include your username and, if it relates to a transaction, the bKash or Rocket reference so the record is easy to match on our side.
Open the help section inside your signed-in account to check the data and payment entries linked to your profile — login history, bKash and Rocket wallet references, and past support threads — before you send in a new privacy question.
If you need a written answer to a privacy question, use the same contact route you'd use for an account issue, and keep the reference number from any earlier message so the full thread stays connected to your account record.
Account security on ok63 starts with what you control — your password, the device you stay signed in on, and whether you log out on a shared browser. We store what's needed to keep your account working: login history, device sessions, and the bKash or Rocket references tied to deposits and withdrawals, kept only as long as your account stays open and useful to you. Cookies handle the lighter work — keeping your session alive and remembering small preferences — and clearing them simply resets that, nothing more. If you ever want to ask how long something is kept, or flag an entry that doesn't look right, the same published support route handles that too; reference your account and the specific record so we're looking at the same thing you are. None of this changes depending on which game or table you're using at the time.
We keep account details, login history and the bKash or Rocket references generated by your deposits and withdrawals, using them only to maintain one accurate, checkable record for your profile rather than scattered entries across the platform or lost between separate support threads.
ok63 uses cookies to keep you signed in across pages and to remember basic preferences like display settings; clearing cookies on your device signs you out of your account and resets those saved preferences the next time you open the site in that browser.
Keep your login details private, avoid saving passwords on shared devices, and sign out when you're done on a browser that isn't only yours; report anything unusual on your account through a published support route as soon as you notice it.
Records stay linked to your account for as long as it's active on ok63; if you want to ask about how long something is kept, or request a change to a saved detail, use the support route and reference your account so we can locate the entry.
These are the questions we hear most about how ok63 handles account data — not generic platform talk, but specifics tied to your login, your payment trail and the support route you'd actually use. If your question isn't answered below, the same published contact route covers it; reference your account and, where relevant, the bKash or Rocket transaction you're asking about. We keep these answers short on purpose: a privacy question usually has one exact answer, not a long explanation, and we'd rather point you at the record than talk around it. Availability of any route, and how we respond to what you ask, still depends on your local law and whether your region can hold an account with us — we're not promising one blanket answer fits everyone reading this page. Keep that in mind if you're reaching this page from outside Bangladesh, where a different rule might apply to the same question.
We collect the details you give at sign-up, your login activity, and the transaction references created when you fund or withdraw through bKash or Rocket. This keeps one accurate account record rather than separate, disconnected entries across different parts of the site.
Yes — your account area shows the transaction history tied to your profile, including bKash and Rocket references. If an entry looks unclear, raise it through a published support route and mention the reference so we can check the same record.
Parts of it do. Because account access depends on local law and eligible regions, what we can disclose or how long certain records are kept may differ depending on your jurisdiction rather than following one fixed rule for everyone.
Use the support contact route published on ok63 and tell us which field needs fixing — a contact detail, a saved name or a wallet reference. We'll match it against your account record before making any change, keeping the update inside the same support thread.
Yes, cookies keep your session signed in and remember basic preferences on your device. Clearing cookies in your browser will sign you out and reset those saved preferences the next time you open the site on that device or browser.
Reach us through the support contact route published on the site and reference your account so the question is easy to trace. We look at the same transaction and login history you see in your account area, not a separate record kept somewhere else.