Account terms
The clauses about who may hold an account and what happens on closure use the same sentences here, so you will not find one rule at sign-up and another inside this page.
Your account details, funding records and game history sit behind one policy you can read in a single sitting. We set out what we collect, why we collect...
6pk365 applies this policy to everyone who opens an account with us, browses the lobby, or contacts our team, wherever local law permits access to our services. If you register from Pakistan, we process your data under the terms written on this page and under the rules that apply in your province. Where a local rule gives you stronger rights than this
page describes, that rule wins. Some features, including JazzCash, Easypaisa, SadaPay and Raast funding flows and location-based content, may only run in supported regions. Our team checks this page when payment rails, game studios or internal systems change, and we publish the current version with a revision marker by the heading. You can ask which version applies to your account by writing
to our privacy desk, and we will confirm in writing within a few working days.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Pick whichever channel suits you. Our privacy desk answers in Pakistani English, keeps a ticket open on every request, and tells you plainly what we can and cannot change. If your question touches a JazzCash, Easypaisa, SadaPay or Raast transaction, mention the reference number so the team can pull the record before replying.
Write to our privacy mailbox from the address linked to your account. We match it to your profile, log the request the same day, and reply within two working days with a reference you can quote later.
Our chat team runs around the clock in Pakistani English and can move a data question straight to the privacy desk. Ask for a ticket number so the same thread stays open for you.
If you prefer paper, our team shares the registered postal address once we confirm your account. The date your letter arrives is logged, and we answer inside the window your province sets.
Six people sign off before anything on this page changes: the data lead, a funding engineer, the support lead, a security analyst, our legal contact and a localisation editor who reads the...
Owns retention windows and signs off every change to how long records stay on file. Walks through the account, funding and cookie wording each quarter to confirm it still matches live system behaviour.
Confirms that JazzCash, Easypaisa, SadaPay and Raast references are written correctly before any update goes live, so nothing here drifts from the gateway behaviour you meet at checkout.
Brings the questions that land in your tickets into policy wording. When several people ask the same thing about a verification step, that question usually becomes a plain sentence here.
Checks the sign-in, device and session rules described on this page against how we actually handle logins, password resets and unusual attempts from within Pakistan or abroad.
Reads every clause against the rules that apply where you live, and flags anything that needs jurisdiction wording so you are never handed a promise we cannot keep.
Keeps the Pakistani English natural, replaces software jargon with everyday wording, and makes sure a term used here means exactly the same thing on our funding and account pages.
This page works alongside our other policy pages rather than repeating them. The wording on data sharing matches the account terms, the cookie list matches the cookie page, and every funding reference...
The clauses about who may hold an account and what happens on closure use the same sentences here, so you will not find one rule at sign-up and another inside this page.
Every cookie name listed in our cookie page appears in the same order here, with the same purpose written beside it, because both pages read from one shared list.
Funding references for JazzCash, Easypaisa, SadaPay and Raast match word for word, including the record types we keep for each transaction and how long those records stay.
Sign-in, device and session rules are described once and reused. If you read a password rule there, the same rule appears here without a softer or sharper version.
Escalation timings and the reference format we give you are identical on both pages, so a complaint about data handling follows the same clock as any other issue.
Support hours, chat availability and mailbox addresses are mirrored rather than rewritten, which means a channel listed on one page is never missing from the other.
Our Pakistani English wording is shared across every policy page, so translating one page into another language keeps the same meaning instead of creating a second set of rules.
The page you are reading is built to be scanned, not endured. A fixed section index follows you down the screen, a revision marker sits under the heading...