Mobile / Live
kriya111 publishes this page so you know how your account, the games you open and the payment references in your wallet are covered under one policy. Check this page before you sign in, deposit through bKash, Nagad or Rocket, or browse our lobby on mobile or desktop.
This policy covers how kriya111 handles your account, the records tied to it and the way payment references appear in your wallet. Access to our lobby, including slots, live casino tables and sportsbook markets covering cricket and BPL matches, depends on your local law and the regions where we can offer service — if your region is not eligible, parts of the lobby may not open for you. When you add a payment method such as bKash, Nagad or Rocket, the reference number and transaction entry sit in your account history exactly as the wallet provider reports them to us; we do not alter or round these entries. We keep this policy consistent across the browser version and the mobile view, so the same terms apply whether you open kriya111 from a phone browser or a desktop tab. Where a term in this policy conflicts with a rule set by your payment provider or by local regulation, the stricter rule applies to your account. We update specific clauses from time to time to reflect changes in payment processing or regional eligibility, and the version shown on this page is the one in force. You remain responsible for keeping your login private and for checking that the payment chip you select — bKash, Nagad or Rocket — matches the account you intend to use.
This policy does not reach every corner of your account activity the same way. Some areas, like your login and your payment chip entries, sit squarely inside scope because kriya111 records and stores them directly. Other areas, like a payment provider's own processing step or a game studio's info screen, sit outside direct scope even though you reach them from inside your account. The four areas below show how we draw that line.
Your login, profile details and session on mobile or desktop fall inside this policy; how you reach your account depends on your local law and whether your region is eligible for service.
Entries recorded against bKash, Nagad or Rocket inside your wallet history fall under this policy; it covers how the record is stored, not the internal processing rules of the payment provider itself.
Game lobbies, pages like this one and listings for titles such as BPL Night Match or Roulette Royal Night sit inside scope; the games themselves follow the rules shown on their own info screens.
Services run by payment providers or game studios sit outside this policy's direct control; we link to them from your account but their own terms govern how they handle your data.
You hold a few practical options under this policy. You can open your account page at any time to check the details we hold against your profile, including the payment chip you last used. If something in your account record looks wrong — a name spelling, a contact number, a saved bKash or Nagad reference — you can raise it through the support route listed below and ask for a correction. You can also ask us a direct question about how a clause in this policy applies to your situation rather than guessing from the general wording. None of these actions change your eligibility to use kriya111; they simply give you a way to check, correct and ask, which is the baseline this policy is built to support.
Open your account page to see the profile and payment details we hold, including which chip — bKash, Nagad or Rocket — is attached to recent entries in your history.
Contact support if a saved detail, like a contact number or payment reference, needs updating; corrections apply to your account record once confirmed.
Send a direct question through our support route if a specific line in this policy is unclear for your situation; we answer against the version published here.
Raise a support ticket if you need help understanding how this policy applies to a transaction or an access issue tied to your region.
If a clause in this policy raises a question, these are the routes we publish for reaching kriya111 about it. Each one connects back to your account so a reply can reference the specific detail you raised, whether that's a payment chip entry or a line in this page. We do not operate separate channels outside what's listed here, so start with the option that matches your question.
Open the support option inside your account to ask about this policy, a payment reference or an access issue; replies come back through the same channel.
Use the message option listed on our support page to send a specific question about a clause in this policy rather than a general account issue.
Check the notice shown inside the lobby for any update to this policy; we post changes there before they take effect on your account.
This section covers the practical side of how kriya111 handles the data behind your account — what we store, how your session works, what you should check before a transaction and how long records stick around. None of this changes based on whether you sign in from a phone browser or a desktop tab; the same handling applies either way, and the same support route answers questions about any of it.
We store account and transaction details, including payment references from bKash, Nagad or Rocket, only to run your account and resolve support questions you raise.
Your browser session on kriya111 uses basic cookies to keep you signed in between the lobby, your account page and this policy page; clearing them signs you out.
Keep your login private and check that any payment chip you select matches your own bKash, Nagad or Rocket account before confirming a transaction.
We keep account and transaction records for as long as your account is active and for the period needed to answer a support question; contact us through your account to ask about a specific record.
No. The terms stay the same whether you sign in from a phone browser or a desktop tab; only the layout of the account page changes between mobile and desktop.
Yes. Open your account page to check the profile and payment details on file, including the last chip — bKash, Nagad or Rocket — used on a transaction.
Access depends on local law and the regions we can serve; if your region falls outside that scope, parts of the lobby or payment chips may not be available to your account.
Raise it through the support route on your account page and describe the detail that needs fixing, such as a contact number or saved payment reference.
No. We record the reference and entry exactly as the payment provider — bKash, Nagad or Rocket — reports it; we do not edit or round these entries.
Use the message option on our support page to ask about a specific line in this policy; we answer against the version published on this page.