Same Definitions
Terms such as account, wallet and transaction carry one meaning across every legal page here, so you never relearn a definition when moving between them.
LEGAL REFERENCE
What We Collect And Why
Everything salma bet collects from you, and why, is set out on this one page. You will see which details travel with a JazzCash, Easypaisa, SadaPay or Raast...
Account Data TermsRail ClaritySupport You Can ReachPolicy Updates Dated
Policy Posture Where Local Law Permits
We operate salma bet under the rules that apply where you are, so this policy is written to be read alongside local law rather than in place of it. Where local law permits online play, we process your account details to run the service, confirm your age and identity, settle deposits and withdrawals, and keep the lobby secure. Where local law does
not permit it, we do not offer access. Our Pakistan payment partners receive only the reference data needed to complete your transaction, not your full account history. If a paragraph here conflicts with a mandatory local requirement, the local requirement wins, and we will tell you when that happens.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHO WRITES THIS
Who Prepared And Maintains This Policy
This policy is written and maintained by the salma bet compliance and product teams, the same people who run identity checks, payment rails and game integrations day to...
Named Team Ownership
A named compliance owner signs off each revision, so you know which internal team is accountable for the wording you...
Version History
Every published revision carries a date and a short summary of what moved, so you can track how our handling...
Everyday Drafting
We draft clauses in everyday language first, then align them with formal legal wording, so you can follow your rights...
Live Data Map
Our engineering team keeps a map of which system holds each category of your data, and that map is what...
Feedback Loop
Questions you raise with our desk are grouped and passed to the policy owner, so recurring confusion about a clause...
Written In House
This wording is produced in house rather than licensed from an outside template, so each clause describes functions you can...
MATCHING OUR PAGES
How This Policy Matches Our Other Pages
The legal pages on salmabet.com are built to read as one set. This privacy policy explains what we hold about you, the terms page covers the rules of use, and the payment...
Shared Rail Wording
Where a clause names JazzCash, Easypaisa, SadaPay, NayaPay or Raast, it repeats the phrasing used on the payment page, so those rails read identically wherever you find them.
One Contact Route
Requests to correct, export or close an account all travel through the same verified contact routes, keeping the trail consistent when a query crosses two pages.
Aligned Update Dates
When a rule changes in two places, we publish the revised pages together and note the cross-reference, so a fresh clause never sits beside an old one.
Matching Retention Rules
Retention periods stated here match those in the terms page, so a record is never held for two different lengths of time depending on which page you open.
Single Security Standard
Encryption, session handling and login checks follow one internal standard across our pages, and that standard is what the wording on each page describes.
No Contradicting Offers
A promise on a promotional page never overrides a commitment made here; if wording ever collided, we would correct the promotional page rather than weaken this one.
How This Policy Page Is Laid Out
This page is laid out so you can find your answer without scrolling through walls of text. Headings name the subject, summary boxes sit above the...
Section Headings
Each block opens with a heading naming its subject, so you can scan for account data, device data or transaction records and land on the right clause fast.
Summary Boxes
Short boxes above the detailed clauses state the same commitment in everyday words, which helps when you want the gist before the formal version.
Rail Chips
JazzCash, Easypaisa, SadaPay, NayaPay and Raast appear as chips that jump you to the clauses covering how each rail is handled on your account.
Change Markers
A marker sits beside any section that has been rewritten, so you can spot what moved between versions without re-reading the whole page.
Contact Panel
A panel at the foot of the page lists the channels you can use, each labelled with the type of request it suits.
Glossary Links
Unfamiliar terms link to a short glossary entry, so you can check what a word means here without leaving the page or losing your place.
Questions About Your Account Data
We collect what an account needs to work: your name, date of birth, contact details, a verified phone number and the identifiers your JazzCash, Easypaisa, SadaPay or Raast payment carries.
Only where a service genuinely needs them: payment rails, identity verification partners, fraud screening and hosting providers. Each works under contract, receives the minimum required, and cannot reuse your details.
Active account data is kept while your account is open. After closure we hold financial and identity records for the period local law requires, then delete or anonymise the rest on our own schedule.
Raise a request inside your account and we send you a copy of the data tied to your profile, with a plain-language summary of where each category came from.
Sessions run over encrypted connections, account access needs verified login details, and internal staff see your records only through role-based tools that record who opened what and when.
Account and policy messages are always sent because they affect your use of the service. Promotional messages arrive only if you have opted in, and each one carries a link that turns that kind of mail off.
We publish the revised wording on this page, date it, and mark the sections that moved. If a change affects how your account data is handled, we tell you before it takes effect.