Terms page boundary
The Terms page explains account rules and service use, while this policy explains data handling. When a term requires personal data, we point back to this privacy wording.
LEGAL REFERENCE
Privacy Policy for your isb 15 account
We keep your privacy choices clear before you open your isb 15 account, including what data we collect, why we collect it and how you can ask about...
Account data usePakistan payment recordsSecurity log handlingPrivacy request path
How this policy applies in Pakistan
This Privacy Policy explains how isb 15 collects, stores and uses data when you create an account, access the lobby, contact our team or make a payment through supported Pakistan rails. We process account identifiers, login activity, device data, location signals, verification files, transaction references and messages you send us. We use those records to run account access, protect sessions, meet legal
duties, resolve disputes and improve privacy controls. We do not sell your personal data. Sharing is limited to service partners who help with hosting, security, verification, analytics or payment handling, and only under controls that match this policy. Access remains for supported regions where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Where to send privacy requests
We separate privacy questions from ordinary account chat so your request reaches the right desk. Tell us what you need changed, copied, checked or removed, and include the account email or phone number you use with isb 15. We may ask for verification before we act.
Team online
Email privacy desk
Send privacy requests to our email team with your account phone, registered email and the exact data question. We log each message, check identity and reply with the next action or reason for delay.
Live chat handoff
When you start in live chat, ask for privacy help rather than account play help. The agent tags the case, avoids sensitive chat sharing and moves it to our privacy queue.
Payment record queries
If your request concerns JazzCash, Easypaisa, SadaPay or Raast records, share the transaction reference only. We use that reference to locate the ledger entry without asking for extra wallet secrets.
POLICY CARE
How we keep the policy reliable
Our privacy copy is written from the way isb 15 actually handles account data. We check it against support practice, security controls and Pakistan payment flows before publishing changes. When wording changes...
Named policy owner
Our operations team owns the policy text and checks it with security and payments staff. That keeps wording aligned with the data we collect during account access and payment support.
Separate data categories
We separate account identity, device signals, gameplay records, payment references and support messages. Clear categories make it easier for you to ask about a specific record.
Security wording
Security language covers password checks, session logs, device flags and suspicious access alerts. We describe these controls because they affect how long certain records are kept.
Local rail context
Payment references are explained using JazzCash, Easypaisa, SadaPay and Raast terms. We avoid asking for wallet secrets and focus on references needed for matching records.
Access request process
Account access requests require identity checks before records are shared or changed. This protects your account from another person attempting to obtain private account data.
Change checks
We check the policy after major account, security or payment changes. If a section becomes unclear, we edit the wording and keep the privacy purpose visible.
POLICY LINKS
Consistency with sibling privacy pages
This Privacy Policy sits beside other legal pages, but it has its own job. It explains personal data handling, not promotion rules or general account terms. We use matching labels across related...
Cookie notice boundary
The Cookie notice covers browser storage, analytics tags and device identifiers. This policy gives the wider context, including why those signals may connect to your account.
Promotion page boundary
Promotion rules may mention eligibility checks, but this policy explains the data used for those checks. We keep reward wording separate from privacy rights and retention.
Verification page boundary
Verification copy explains documents and account checks where required. This policy explains how those files are handled, protected, shared with service partners and removed when no longer needed.
Payment help boundary
Payment help describes matching wallet references and failed transaction cases. This policy explains the privacy side of storing those references with JazzCash, Easypaisa, SadaPay and Raast.
Support script boundary
Support scripts tell agents what they may ask during a case. This policy sets the privacy rule behind those scripts, including identity checks before personal records are discussed.
Archived copy boundary
Older policy versions are kept only for audit and dispute context. Current privacy wording controls new requests unless a past issue requires the version active at that time.
PAGE MARKERS
Visible cues across this policy
We designed this policy page to make privacy points easy to scan without turning them into vague claims. Each marker, card and question has a narrow purpose: show...
Date marker
A clear date marker helps you see when the privacy...
Plain labels
Section labels use direct privacy language such as account data...
Short chips
Chips highlight local context without adding long explanations. JazzCash, Easypaisa...
Contact cards
Contact cards separate email, chat and payment-record paths. That layout...
Rights prompts
Questions near the end focus on access, correction, deletion and...
Partner clarity
Partner references explain why hosting, security, verification or payment service...
Common privacy questions for isb 15
We collect account identifiers, contact details, login records, device signals, verification files when needed, payment references and support messages. We collect only what we need to run access, security, payments and privacy requests.
Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account, resolve failed credits, answer disputes and meet record duties. We do not need wallet passwords or private wallet codes.
Yes, you can ask for a copy of account data linked to you. We verify your identity first, then provide available records or explain why a record cannot be released.
You can ask us to correct account details that are inaccurate or outdated. Some changes may require verification, especially phone, payment or identity fields connected to account security.
Retention depends on the record type and legal need. Security logs, payment references and verification records may be kept longer than support messages when disputes, audits or compliance checks require it.
We share data only with service partners that help operate hosting, security, verification, analytics, support or payment processing. Those partners receive limited data tied to the task they perform.