LEGAL REFERENCE

Privacy Policy for Your Account Data

We keep this privacy policy focused on the data that matters to you: account details, device signals, transaction references and support records. On isb 7, you can see...

Account dataPakistan scopeClear retentionLocal law
isb 7 Privacy Policy for Your Account Data

How We Handle Data in Pakistan

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

REACH OUR TEAM

How to Reach Us About Privacy

If you want help with access, correction or removal requests, we keep the contact routes simple. You can reach us through the form inside your account, by email, or through the help inbox attached to your profile. We verify the request before any change is made, which protects your record while we check the right data and the right authority.

Team online

Email

Email us from the address linked to your account if you want to see what we hold, fix a detail, or ask for removal where local law permits.

In-app form

Use the form inside your account for access or correction requests. We match it to your profile before we reply, which helps keep the request private and traceable.

Help inbox

If your matter needs extra checking, our help inbox lets us continue the same thread so you do not repeat yourself while we verify the request.

HANDLING STANDARDS

Why This Policy Stays Clear

We write this policy in plain English so you can see what we collect, why we keep it, and which checks apply before a request is handled. The same standards shape every...

Plain wording

We avoid dense legal language where a simple sentence will do. That helps you understand what data we ask for, why we ask for it, and how you can ask us to change it.

Minimal collection

We only ask for the fields needed to open, secure and service your account. If a field is optional, we treat it that way and do not use it for unrelated purposes.

Purpose limits

Each data point has a stated reason, such as access control, account checks, issue handling or legal retention. We do not widen the use later without updating this page.

Access control

Only staff who need a record for a defined job can see it, and access is logged. That keeps routine support separate from sensitive account handling and limits unnecessary exposure.

Retention rules

We keep records only for the period needed to meet legal duties, resolve disputes and protect the account history you created. After that, we delete or anonymise them where possible.

Change log

When this page changes, we update the text rather than burying the shift in a side message. You can compare the wording with the date stamp to spot what moved.

PAGE CONSISTENCY

How This Page Stays Aligned

This page stays aligned with our other legal pages, but it keeps the focus on personal data rather than contract language, account conduct or payment flow. When a sibling page explains rules...

01

Scope

Our terms page can set contract rules, but this page narrows in on personal data only. That keeps the boundary clear when you look for the right legal point.

02

Collection

Sibling pages may mention verification or account conduct, while this page spells out which details we collect, such as contact data, device signals and transaction references, and why.

03

Use

Where another page may discuss access conditions, this page explains how we use your data for security checks, support replies, record keeping and lawful processing tied to your account.

04

Sharing

A different legal page may focus on service rules; this one says exactly when data can be shared with processors, auditors or authorities, and only for a stated purpose.

05

Retention

The retention paragraph stays distinct here. Instead of repeating general account language, it tells you how long records remain, what triggers removal and when legal duties keep them longer.

06

Requests

If a sibling page covers disputes, this page covers privacy requests like access, correction and deletion. You can move between them without losing sight of which form to use.

07

Updates

Other policy pages may change for product reasons, but this page changes only when our data handling changes or law asks for it. That keeps the privacy terms aligned.

LAYOUT MARKERS

What You See On This Page

We keep the privacy page easy to scan. Headings are short, each section starts with a clear label, and the layout uses compact cards so you can find...

Sticky anchors The privacy page uses short anchors so you can jump...
Short blocks Each block stays compact, with one clear idea per paragraph...
Date stamp We keep the update date close to the heading so...
Contact strip The contact area sits near the end, so your privacy...
Plain labels Headings use plain labels like collection, use, sharing and retention...
Clear spacing Generous spacing separates each section, which matters when you are...

Privacy Questions You May Ask

We keep the contact and profile fields needed to set up access, verify the account and answer future requests. If a field is optional, you can leave it out unless a check requires it.

Yes, we may keep transaction references, status flags and time stamps tied to those rails so we can match entries, solve mismatches and meet record-keeping duties where local law permits.

Device and browser signals help us spot suspicious access, remember your session and reduce repeated checks. We use them for security and service continuity, not for unrelated profiling.

Only staff or service partners who need the record for a defined job can access it, and that access is limited to the purpose stated in this policy. We log those actions.

We keep records for the period needed to run the account, settle disputes, meet legal duties and protect against misuse. After that, we delete or anonymise them where possible.

Yes, send the request through the contact paths on this page and we will verify it before acting. Where local law permits, we can correct or remove the data linked to your account.