Terms Page
Sets out the agreement between you and salam bet, which this page assumes and never overrides; where the two touch, the terms decide. We point you there wherever the two overlap.
LEGAL REFERENCE
How We Handle Your Data at salam bet
We gather only what an account needs: your registration details, payment references from JazzCash, Easypaisa, SadaPay or Raast, and the session data that keeps a login safe. Below...
Registration Details OnlyPayment References Kept SeparateSession Safety LogsYour Choices Over Records
Rules That Travel With Your Region
We run salam bet for supported regions, and every clause here is written to be read where local law permits access. The rules you accept when you open an account are the rules you can point to later: what we store, how long we keep it, who on our team can see it, and how a deletion request travels through our systems.
Where a Pakistani requirement or a payment partner's own rule is stricter, the stricter rule governs that record. Nothing here narrows a right you already hold under the law that applies to you. If a section reads differently in your region because of a licensing condition or a bank rule, we say so instead of leaving you to guess. We also keep
a dated log of changes.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHO MAINTAINS THIS
The People Who Keep This Page Current
A policy only earns its place if someone actually owns it. The desks below split the work: drafting clauses, reading them against regional law, checking them against how our systems behave, and...
Policy Drafting Desk
Writes and revises every clause on this page, keeps the wording as plain as possible, and logs each change so you can spot the difference after a few months away.
Regional Law Reader
Checks each section against the rules that apply where you live, and flags anything stricter so a Pakistani requirement always shapes the final wording you agree to when you join.
Security Team Sign-Off
Confirms that the storage and access practices described here match what our engineers built, including encryption at rest and the narrow list of staff who can view account records.
Payment Liaison
Talks to JazzCash, Easypaisa, SadaPay and Raast contacts about what order data travels between us, so the description here stays true to the live integration you actually use.
Retention Custodian
Sets the clock on how long each record class survives, schedules deletions, and confirms that a closed account no longer generates new entries once the final payout settles.
Change Log Keeper
Dates every update to this page and keeps the previous wording on file, so you can see exactly what applied on the day you opened your salam bet account.
SIDE BY SIDE
How This Page Sits Next to the Others
Our legal pages share one structure on purpose: the same headings, the same plain wording, the same dated change log. This page covers data handling; its siblings cover the agreement, cookies, account...
Cookies Page
Explains the small files that keep a signed-in session alive and remember your language choice, naming each category rather than hiding them behind a single switch, so you can decide what stays.
Account Access Page
Describes how a login is protected, how a password is changed and what happens when you use a shared device, which is the practical half of what we cover here.
Cash-Out Timing Page
Covers how long a withdrawal takes to reach JazzCash, Easypaisa, SadaPay or Raast, and it explains the verification step that can hold a transfer for a short while.
Account Closure Page
Walks through closing your profile, exporting the records you want to keep first, and what survives deletion because a payment record has to stay for accounting rules. Our retention section explains the rest.
Language Options Page
Shows the languages we publish in and how the English wording here stays the reference version if a translation ever reads differently to you. Translations follow the English text in every case.
Complaint Path Page
Sets out what to do if an answer from our team does not settle your question, including the escalation route and the records you should have ready. Start with your reference number.
WHAT THIS PAGE SHOWS
The Blocks That Build This Policy
We lay this page out so you can answer a question in under a minute. A short opening tells you what we hold, numbered clauses carry the detail...
Opening Summary
The first block gives you the short version: what we...
Numbered Clauses
Each clause carries a number you can quote in a...
Context Chips
Chips beside the opening summary name the payment rails we...
Change Log Strip
A dated strip records when the wording last moved, so...
Cross-Links
Where another page covers a subject more fully, we link...
Contact Block
The closing block repeats every route to our team along...
Questions We Get About Your Data
Your registration details, contact address, device and session data, and the references your payments carry. We do not ask for anything the account itself does not need to function.
No. JazzCash, Easypaisa, SadaPay, NayaPay and Raast receive an order reference and the amount, not your account history, messages or device details. They settle a transfer; the profile stays with us.
Two clocks run at once: account data lives while your profile is open and clears after closure, while payment records stay far longer because accounting rules require a trail.
Yes. Send the request from the email on your account through the records address above, and we will return a copy or fix the entry within a few working days.
Your profile no longer generates new entries once the final withdrawal settles. Anything that must remain, such as a settled payment record, is kept to the schedule on this page.
Only if you asked us to. Your contact address carries account notices, security messages and anything you opted into, and you can switch the optional ones off whenever you like.