LEGAL REFERENCE

Privacy policy for your isb 15 account

Our Privacy Policy explains what account data we collect before you enter the live casino, slot rooms or sportsbook, why we need it, and how you can reach...

Account data useWallet reference carePakistan privacy routesSupport request handling

Explore Lobby Read FAQ

How we handle your account data

Our policy starts with the data you give us while creating or using your isb 15 account: name, mobile number, email, login events, device signals, and transaction references. We use these records to run account access, confirm payments, protect your balance area, answer support requests, and meet record duties in supported regions of Pakistan where local law permits. Payment partners may send

status codes or reference IDs, not your wallet PIN. We do not sell your personal data. When we need service providers for hosting, fraud checks, analytics, or messaging, we restrict their use to the privacy purpose stated in our contract and keep retention periods aligned with account, security, and legal needs. You can ask us to correct records held by us.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT PATHS

Reach us about privacy matters

Privacy questions deserve a route that is easy to find. Use the channel that matches your concern, and include your registered mobile...

POLICY CHECKS

How we keep this policy accurate

We check this policy against how our account, wallet, support, and security flows actually work. When a process changes, our content and operations teams update the wording before the change is released...

Process matching

Policy wording is checked against live account screens, payment status flow, and support scripts. If a screen asks for data, this page must explain the privacy reason in plain English.

Plain language

We avoid vague privacy wording where a clear term works better. Names, mobile numbers, wallet references, device signals, and support records are described as separate data categories.

Access control

Internal access to personal records is limited by role. Support can see what is needed for your ticket, while wallet and security checks stay with trained teams.

Retention checks

We keep records only for account operation, dispute handling, security, and legal reasons. When a record is no longer required, we remove it or reduce identifying detail.

Pakistan context

The policy reflects Pakistan account flows, including JazzCash, Easypaisa, SadaPay, Raast, and local mobile-number use. Each reference is treated as account data, not public material.

Security link

Privacy and security work together on isb 15. Device checks, login alerts, and verification steps are used to protect records from account access that looks unusual.

Privacy wording across related pages

Your privacy expectations should not change from page to page. We align this page with our cookie, terms, contact, and account-help pages so the same categories, request paths...

Cookie page

Our cookie page deals with browser storage and device signals. This Privacy Policy explains how those signals connect to account protection, session reliability, and preference handling on isb 15.

Terms page

The terms explain account rules, while this policy explains personal data use behind those rules. We keep both pages aligned so privacy wording supports account obligations clearly.

Contact page

The contact page gives support routes, but this policy explains how messages, attachments, and identity checks are handled once you send a privacy-related request to us.

Account help

Account-help content may mention verification steps. This policy adds why we ask for certain details, who can view them, and how long related records may stay.

Wallet flow

Payment pages show transaction movement, while this policy covers reference IDs, wallet status messages, and fraud-check signals connected with JazzCash, Easypaisa, SadaPay, and Raast.

Lobby access

Lobby pages describe account entry, but this policy covers login events, device checks, and session records used when you access casino, slot, or sportsbook areas.

Policy updates

When related pages change, we check whether privacy wording also needs an update. That keeps your rights, request paths, and data categories consistent across isb 15.

Policy cues you see on page

We design privacy pages so you can understand them before opening an account. The layout keeps legal language close to the account actions it affects, from...

Short section labels

Each label points to a specific privacy task, such as collection, sharing, retention, or contact. That helps you scan the page without losing the legal meaning.

Account examples

Examples refer to real isb 15 actions, including login checks, wallet references, support tickets, and device signals. We use them to make privacy wording practical.

Request prompts

Where a privacy request is possible, we show the route in direct language. You can see what to include and why verification may happen first.

Retention markers

Retention wording appears near the data category it affects. That makes it easier to understand why account records, transaction references, and support logs differ.

Sharing boundaries

We separate internal access from external service support. The page makes clear when hosting, messaging, analytics, or security vendors may process data for us.

Update visibility

Policy updates are written so you can identify changed privacy duties quickly. We avoid burying account-data changes inside general platform wording or promotional copy.

Privacy questions before you open an account

We collect details needed to create and protect your account, such as name, mobile number, email, login records, device signals, and transaction references connected with supported Pakistan payment routes.

No. Wallet authentication stays with the wallet provider. We may receive payment status, amount, timing, and reference codes, but we do not ask for or store wallet PINs.

Device signals help us detect unusual account access, keep sessions stable, and investigate security reports. We use them for privacy and account protection, not to sell your personal data.

Yes. Contact us with the detail you believe is wrong and enough account context to verify you. We correct records when the request is valid and lawful.

Retention depends on the record type. Account, support, security, and transaction references may be kept for different periods where needed for operation, dispute checks, and legal duties.

We may use providers for hosting, messaging, analytics, security checks, and support tools. They process data for isb 15 under restricted purposes rather than for their own use.