Scope Match
The same collection scope appears across related policy pages, so you do not face one rule here and another rule elsewhere. We keep the definition of account details stable.
LEGAL REFERENCE
Privacy Policy for dosti 786
This page explains how we collect, use, store, and protect your account details on dosti 786. If you open an account from Pakistan, you can see what stays...
Pakistan AccountsPlain-English TermsWhere Local Law PermitsSupport Routes
How We Handle Your Data
When you use JazzCash, Easypaisa, SadaPay, or Raast, we keep the records needed to confirm the transfer, match it to your account, and stop duplicate handling. We also keep registration details, device signals, and support history so we can secure access, trace mistakes, and answer your requests without asking you to repeat the same facts. Where local law permits, some records may
stay with us longer for fraud checks, dispute handling, or tax duties. If a field is not required for account handling, we do not collect it just to have it on file. You can ask us to correct stale details, and we will act after we verify that the request comes from you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
EDITORIAL CHECKS
What We Check Before Publishing
We write this page in plain English so you can read what we keep, why we keep it, and when it may be shared. Our team checks the...
Data Scope
We limit this page to the records that matter for account access, payment checks, support cases, and abuse control. That...
Plain Language
We choose short sentences and direct terms so you can read the page on a phone without guesswork. Where a...
Change Log
When we amend the page, we update the date and keep the new text in place from that point forward...
Access Checks
Requests that touch account details go through verification before any change is made. This protects your profile from accidental edits...
Local Fit
We keep the wording aligned with Pakistan-facing account flow, including local payment rails and support paths. That way the page...
Record Care
We store only the records needed for security, settlement, support, and lawful retention. Anything outside that scope is not kept...
POLICY MATCH
How This Page Stays Consistent
This page follows the same privacy language across the site, so the terms for account details, device records, and support notes stay consistent. If another policy page mentions a record type, we...
Retention Match
The retention wording stays aligned with our other legal pages. If a record must stay for security or settlement reasons, this page uses the same timeline language.
Sharing Match
Any mention of sharing follows the same logic as our terms page: we only pass records to service partners, payment rails, or legal requests when there is a clear reason.
Correction Match
Correction requests are handled the same way across the site, which means you can use one support route instead of learning a separate process for every page.
Security Match
Security wording is kept consistent so you know when access checks, verification steps, and abuse prevention apply. We do not hide extra rules in a different page.
Local Law Match
Where local law permits appears in the same places across our policy set, helping you see when jurisdiction changes the way a record is handled.
Version Match
Change dates are placed in the same spot across related pages, so you can tell when the legal text moved without searching through old copies.
Visible Elements on This Page
The page is laid out so the key points are easy to scan on mobile. You will see short sections, clear headings, chip-style context labels, and...
Short Sections
Each block stays focused on one part of the policy, which makes the page easier to read in bursts when you are on a small screen or checking a specific rule.
Context Chips
Small labels sit beside the policy copy so you can spot the Pakistan-facing context quickly without scanning long paragraphs. They keep the page compact and readable.
Clear Dates
A visible date marker helps you see when the text changed, which matters when you want the current rule rather than an old version saved in your browser.
Linked Blocks
We keep related clauses near each other, so collection, sharing, and contact details do not feel scattered. That reduces back-and-forth when you are looking for one answer.
Support Panel
The support area sits close to the policy copy, making it easy to move from a question to a message without leaving the page structure behind.
Readable Flow
Headings, paragraph spacing, and short lines all work together so the policy reads cleanly on mobile data, where long walls of text can be hard to follow.
Privacy Policy Questions, Answered
We keep the details you submit when you open an account, along with the records needed to verify access, handle support, and meet lawful retention needs. We do not ask for anything that has no clear purpose.
Device records help us spot suspicious access, block duplicate sessions, and keep your account secure. They also help our support team understand whether a problem comes from the browser, the network, or the profile itself.
We only share records with service partners, payment rails, or legal requests when there is a clear reason. Any sharing is limited to the task at hand and not used for unrelated profiling.
We keep records only for the period needed for security, support, reconciliation, and lawful retention. Once that period ends, we either remove them or keep them only in a reduced form where required.
Yes. Send the exact detail that needs correction through the support route, and we will verify the request before updating the record. That protects your account from accidental or unauthorized changes.
If the rules change in Pakistan or in another supported region, we adjust the policy text to match the new requirement and update the date so you can see the latest version.