Policy and terms
The terms page sets the rules of play. This page explains the data trail those rules create, and where any retention figure lives.
LEGAL REFERENCE
Privacy Policy: What We Hold, And Why
This page sets out what pak365 download collects when you open an account and how we store it. It runs through sign-up details, device and login records, lobby...
Account detailsLogin recordsLobby activitySupport chats
How We Treat Records In Each Region
We frame this policy around where you are, because the rules that apply differ by market and access is offered only where local law permits. If you sign in from Pakistan, your account records are handled under the terms on this page. If you sign in from another supported region, some clauses shift: retention windows, the list of processors we share with,
and how a deletion request is routed. Payment context helps here — a JazzCash load leaves a different trail from a Raast transfer or a SadaPay card credit. We keep the wording plain so you can spot which parts apply to you. Clauses that apply everywhere sit first, and market-specific wording is marked. Where the two differ, the more protective rule applies
to your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
REACHING THE DESK
Where To Send A Privacy Question
Privacy asks land on a desk beside our usual customer support, so you are not pushed through a general queue. Tell us which record you want to see — a JazzCash load log, a login history export, a support transcript — and we pull the right file against your account. Most written requests get a reply inside two working days.
Team online
Signed-in chat
Inside your account, open the help tab and mark the message as a data request. Your account ID travels with it, so the desk finds the file without retyping.
Written request
Email suits longer asks, such as a copy of everything tied to one route. Attach any JazzCash, Easypaisa, SadaPay or Raast confirmation you hold so we can match it.
Security channel
If someone else may have reached your account, use the security line first. The team can freeze the session, then handle the data question and give you a reference.
WHO WRITES THIS
The Team That Drafts These Clauses
Everything here is written and kept current in-house by the people who run account operations for pak365 download. Each clause maps to something the team built or watches: how a load is...
Written in-house
The policy team shares a workspace with the payments crew. When JazzCash or Easypaisa changes what it returns on a load, the wording here moves with the code.
Version stamps
Each update carries a revision date. If you want the wording as it stood when you opened your account, the desk can send that earlier copy.
Plain drafting
We draft in everyday English for Pakistan rather than legal shorthand. Long clauses are split up, and any fixed term is defined in the sentence using it.
Named rails only
Only the Pakistani routes we settle through are listed — JazzCash, Easypaisa, SadaPay, NayaPay and Raast. Anything unsupported stays out, so the list never overstates the platform.
Security stated plainly
Two-factor sign-in, session timeouts and login alerts are described in ordinary words, including how many failed attempts are allowed before an account freezes.
No contact-list selling
Your details run your account, meet our record-keeping duties and keep the lobby secure. We do not hand contact lists to advertising brokers or unrelated third parties.
SIDE BY SIDE
How This Policy Sits Beside Others
This privacy policy is one of a small set of documents you accept when you open an account, and it sits cleanly beside the rest. The terms page handles how you use...
Policy and cashier
Our cashier page shows how money moves in and out. This page shows what stays afterwards: reference numbers, timestamps, the route used and its status history.
Policy and cookies
The cookie notice deals with what sits on your device while you browse. This document deals with what reaches our servers once you sign in.
Policy and security
The security page describes the locks around your account. This page describes the login history, device markers and alert logs those locks produce.
Shared vocabulary
Words such as account, session and payout carry the same meaning in every document we publish, so you can move between pages without relearning a glossary.
One retention table
Retention windows are set out once, here, and referenced from the other documents rather than repeated, leaving one place to confirm how long a record is held.
How updates flow
New clauses appear on this page first, then spread to any document referring to them. If two pages disagree on a data question, this policy takes priority.
Visible Pieces Around This Document
A few visible pieces around this document do a fair share of the work. The date block shows how fresh the wording is, the menu down...
Last changed date
The block at the head of this document shows when the wording last moved. If you opened your account earlier, the previous version shaped how records already held were handled.
Jump menu
A fixed list beside the text reaches any clause without scrolling the whole policy. It matters most on a phone, where long documents are awkward to skim.
Language switcher
This page reads in English written for Pakistan. Where a translated copy exists, the switcher flags it as a translation and the English wording stays binding.
Rail labels
The chips name the Pakistani routes referenced when this page discusses transaction records. They act as labels, not links, so tapping one will not open a cashier.
Print view
A clean print style drops the navigation and leaves the clauses on the page, which helps if you want a copy for your own files.
Question block
The short question list near the foot answers what our desk sees most often, and each answer points back to the fuller clause.
Privacy Questions We Get Asked Most
Sign-up details you type in, a device marker, and the records your activity creates: lobby sessions, support chats and transaction logs from whichever route you use. We collect what the account needs.
Only with processors that keep the platform running: payment partners for settlement, hosting and fraud screening, and our own support tooling. Each is bound by contract and none may sell your details on.
Transaction records from JazzCash, Easypaisa, SadaPay and Raast are held for the period our accounting and dispute duties require, then cleared on a rolling schedule. Account and login records follow a shorter window.
Yes. Write in through the channels listed above, name the record you want — a login export, a load history, a chat transcript — and we compile it against your account ID and send it back in writing.
Closing an account ends new activity but does not wipe everything at once. Records tied to settled transactions stay for the period our duties require, and marketing contact ends the moment you ask.
Two-factor sign-in, session timeouts and login alerts are standard on every account. Repeated failed attempts freeze sign-in until you verify, and the security channel can lock a session when you report it.