Privacy Policy for your isb77 account
isb77 keeps this Privacy Policy close to your account flow, so you can see what we collect before you open an account. We explain account records, device signals...
How we handle your account data
This Privacy Policy sets out how isb77 collects, uses, stores and shares data linked to your account where local law permits and in supported regions. We collect the details you give us during account opening, login records, device signals, session activity, support messages and transaction references connected with JazzCash, Easypaisa, SadaPay and Raast. We use these records to run your account, confirm
access, process requests, protect the service from misuse and answer privacy questions. We do not write this policy as legal decoration; it is meant to help you decide what to share, how to contact us and what checks may happen before withdrawals or account changes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact paths for privacy requests
If you want to ask about this Privacy Policy, start with the same support route you use for your isb77 account. Tell us whether your question is about access, correction, deletion, transaction records or security checks. We may ask for matching account details before discussing private records, because privacy support must protect your account as well as answer your request.
Live chat privacy queue
Use live chat when your privacy question is tied to a current account issue. We ask for account matching details, then route the chat to the team handling data and access matters.
Email privacy request
Email suits longer privacy requests, especially corrections or record access questions. Include your account name, registered contact detail and the exact record you want us to check.
Payment record help
For JazzCash, Easypaisa, SadaPay or Raast privacy questions, share the transaction reference only through our support channel. We use it to match records without exposing extra financial details.
Privacy controls behind the policy
Our Privacy Policy is written from the way isb77 actually runs account handling. We separate login security, payment verification, support history and marketing preferences so each record has...
Purpose-based collection
We collect account data for named reasons: access, verification, support, transaction handling and security. The policy avoids broad wording so...
Role-based access
Support agents, finance handlers and security staff do not need the same records. Our policy reflects that split, so private...
Transaction matching
JazzCash, Easypaisa, SadaPay and Raast references are used to match your account with a request. We keep the policy focused...
Device security signals
We may read device type, browser signals, IP range and login timing to protect account access. The policy explains this...
Support history handling
Support chats and emails may be kept so we can follow your request, prevent repeat checks and answer disputes. The...
Policy change markers
When we adjust privacy wording, we keep changes tied to the page rather than hiding them inside account screens. You...
Consistent wording across legal pages
This Privacy Policy connects with our terms, cookie wording and account rules, but it has its own job. It explains personal data handling rather than game rules, promotions...
Visible privacy elements on this page
We designed this Privacy Policy page so the key privacy signals are easy to spot before you share account details. Headings separate collection, use, storage, support...
Plain-language headings
Each heading names a privacy action, such as collection, storage or contact. That makes the page easier to scan when you need a specific answer quickly.
Local rail chips
JazzCash, Easypaisa, SadaPay and Raast appear as context chips where transaction privacy matters. We use them to show local relevance without adding unrelated finance copy.
Account-first wording
The page speaks directly to your account choices, not abstract legal theory. We explain what you share, why we ask and how support checks your request.
Short policy cards
Card sections break privacy handling into smaller pieces, including access, support records and security signals. You can move through the policy without losing the thread.
Return-friendly layout
Privacy questions often come later, after account opening or a transaction query. The layout helps you return to the part that matches your current concern.
Conversion without pressure
We want you to open an account with clear privacy expectations. The page supports that choice by explaining data handling before asking you to share more details.