Terms of use
Our terms page covers account conduct and lobby rules; this policy covers what we do with the data those terms create, and the two never pull in different directions.
Every account at btc casino comes with a privacy policy written in plain English instead of legal shorthand, so you know what happens to your details before you...
Where local law permits, this policy follows the full journey of your data at btc casino: what we gather at sign-up, what we read while you use the lobby, and what we pass to payment partners to move money through JazzCash, Easypaisa, SadaPay or Raast. We ask only for what an account genuinely needs — your name, contact details, date of birth
and the documents our verification step requires. Everything else is optional, and declining it will not cost you lobby access. Where a local rule differs from what we describe here, that requirement takes priority and we tell you in writing before any change touches your account. You can ask what we hold, ask for a correction, or close your account and have
your profile erased, subject to records we must keep under applicable law.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our privacy policy is maintained by the same people who run account operations at btc casino, not by an outside agency. Every revision passes a data-handling check before it goes live, and...
A named data protection lead signs off every change to this policy and answers account questions personally when a request needs judgement rather than a standard response from our team.
We draft in everyday English and test each paragraph with support staff, so you can read the whole policy in a few minutes and still follow where your data travels.
The wording is written for accounts held across Pakistan, and money flows are described the way JazzCash, Easypaisa, SadaPay and Raast actually clear on our ledger, day by day.
Account sessions run over encrypted connections, passwords sit in our systems as salted hashes, and staff access to profile records is logged and limited to the people who need it.
Identification records stay with us for as long as local rules demand, then leave on a fixed schedule, so nothing sits on our servers without a written reason.
Each amendment carries a version number and a date above the first clause, and we email you before any material change takes effect, usually several days ahead of time.
This policy follows the same wording conventions as our terms and payments pages, so a phrase means the same thing wherever you meet it. Where a sibling page covers a narrower topic...
Our terms page covers account conduct and lobby rules; this policy covers what we do with the data those terms create, and the two never pull in different directions.
The payments page explains JazzCash, Easypaisa, SadaPay and Raast timing, while this policy explains which transaction records we keep, how long we hold them and who may see them.
Browser storage, device identifiers and similar tools are described on our cookie notice, and this policy picks up from there with how long each item stays on your phone.
Sign-in, verification and password reset steps live on the security page; here we set out how those records are stored, who reads them and when they are cleared from our systems.
Short answers about data requests sit in our help centre, and every article links back to the matching clause on this page so you can confirm the detail yourself.
English is the governing version of this policy; where a translated copy reads differently, the English wording on this page decides how your request is handled by our team.
Older versions stay archived and dated, so you can trace what changed, when it changed, and which wording applied to your account on any given date.
The layout follows the order you actually need: a summary box near the start, the full clauses underneath, and the contact routes at the end. Headings carry anchor...