Privacy Policy For Your i5kbd Account
i5kbd gives you one clear privacy policy for casino, live table and sportsbook account data, so you know what we collect before you open your account. We explain...
How We Handle Your Pakistan Data
Our privacy policy explains how we collect account details, verify identity, protect login records and connect transaction references with Pakistani rails such as JazzCash, Easypaisa, SadaPay and Raast. We use your data to run your account, apply security checks, process support requests and meet lawful record duties that apply to our service where local law permits. We do not sell your personal
data. Access controls restrict internal use to trained teams handling account safety, funding, technical faults or customer care. When we use service partners for hosting, analytics or message delivery, we require them to handle data only for the task assigned. Retention periods depend on account status, legal needs and dispute handling, then records are deleted or de-identified when no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Policy Text Current
We maintain this privacy policy as an operating document, not a static footer link. When our login tools, KYC flow, cookie stack or Pakistan payment references change, we...
Service mapping
We map policy wording against account creation, login, KYC, wallet, casino, sportsbook and support flows so each data use has...
Access roles
Internal access is role based, so support, risk and technical teams see only the account data needed for the task...
Partner checks
Where hosting, analytics or message partners process data for us, we check the purpose, retention need and transfer path before...
Change records
Policy edits are logged with the reason for change, helping us connect public wording with product updates, support practice and...
Plain language
We write privacy terms in direct Pakistani English, avoiding vague legal phrasing where a practical account example explains the point...
Regional access
Access wording stays tied to supported regions and where local law permits, so the policy does not suggest availability beyond...
Same Privacy Logic Across Pages
Your privacy rights should not change because you enter from a casino page, sportsbook page, mobile screen or help area. We keep the same policy logic across those...
| Account pages | Account screens point back to the same privacy policy, so your name, contact details, login history and KYC status follow one clear handling standard. |
|---|---|
| Casino pages | Casino activity references are treated as account activity data, with access limited to service operation, security checks, dispute handling and lawful record needs. |
| Sportsbook pages | Sportsbook records use the same privacy controls as other account activity, including retention rules, support access boundaries and internal role limits. |
| Mobile screens | On mobile, shorter labels still link to the same policy points, so cookie choices and account privacy wording do not change by device. |
| Support area | Support tickets may include screenshots, references or chat text, and this policy explains how those details are stored, routed and later removed. |
| Wallet records | Wallet references connect transaction status with your account, while provider-side processing remains separate from our own privacy handling and support records. |
| Cookie banner | Cookie controls use the same categories described here, helping you understand what is necessary for security and what supports measurement. |
Visible Cues Inside This Policy
This privacy policy is arranged so you can scan what matters before opening an account or while managing one. Section labels, short chips and direct contact...
Plain headings
Headings separate collection, use, sharing, retention and rights, so you can move to the privacy point affecting your account without reading unrelated legal text.
Local wording
Pakistan references appear where they affect privacy, such as KYC context, wallet references, local support language and access where local law permits.
Data categories
We describe account details, device signals, cookies, identity records and support messages as separate categories because each has a different privacy purpose.
Rights path
Requests to access, correct or remove data are placed near contact options, making privacy action clearer after you have logged in securely.
Security signals
Login protection, restricted staff access and verification checks are grouped together, showing how privacy and account safety work in the same flow.
Update date
When wording changes, the policy area can show the current version date, helping you see whether privacy terms have changed recently.