What We Do With Your Account Data
tip bet keeps one written policy for every account we open, and this is it. You will see what we collect when you join — your name, mobile...
How We Apply This Policy In Practice
Where local law permits, this policy applies to every way you reach tip bet: the browser lobby, the mobile layout and any message you send our support desk. We decide why your details are held and how they are used, and the same rules sit behind a JazzCash wallet transfer, an Easypaisa payment, a SadaPay card load or a Raast bank reference.
Some account features only run in supported regions, and where a country's rules ask for something different, that local requirement comes first. We keep records long enough to meet accounting and dispute-handling duties, then delete or anonymise what is no longer needed. When a clause changes, we date it on this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The Checks Behind Every Policy Update
Every clause on this page passes through three people before it goes live: the desk that answers your messages, the team that runs JazzCash, Easypaisa, SadaPay and Raast handling, and a writer...
Plain wording
We write clauses in short sentences and cut legal shorthand, so you can read the whole page in minutes and see what each rule means for your account.
Dated versions
Every edit carries a date and a line describing what moved. Old drafts stay stored internally, so we can answer a question about a clause you agreed to months ago.
One data owner
A named manager on our team owns this policy and answers for it. If a payment partner asks us to change how data is shared, that call is theirs.
Two-step access
Your account sits behind a password and a code sent to your mobile. We never ask for a wallet PIN in chat, and nobody from our desk will request one.
Local rails only
We record the Pakistani rails you choose, from JazzCash and Easypaisa to SadaPay and Raast, so a payment can be matched to your account without you sending extra documents.
Clear retention
We state how long each record is held rather than saying it is kept as needed. Financial entries stay for the period local rules require; message preferences clear far sooner.
How This Page Sits With The Rest
Our policy pages share one structure, so you can move between them without relearning the layout. This page handles data and record-keeping; passwords, chat behaviour, app permissions and...
| Account terms | The terms page sets out what you agree to when you open an account. Where it touches your details, this policy holds the rule and the terms page points back. |
|---|---|
| Withdrawal handling | Withdrawal handling sits on its own page, covering the checks before money leaves. This page explains which records those checks read, how long they are stored and who sees them. |
| Cookie settings | Our cookie page lists the small files your browser stores and the switches you control. The data rules for those files are written here, so read both side by side. |
| Game rules | Each studio's rules page covers how a round is settled, from slots to live tables. We keep the data side here: which play history we store and for how long. |
| Sportsbook markets | Markets and odds live on the sportsbook page. How we hold your staking history, and how long an unsettled market stays on file, is set out in the section above. |
| Support routes | Our support page lists chat and email routes with opening hours. Data requests follow the same channels, and this page sets the reply window you can expect in supported regions. |
| App permissions | The app page explains what your phone allows us to reach. Anything collected through the app is governed by the clauses here, including notification settings and device identifiers. |
Layout Pieces You Will Notice Here
We keep this page scannable rather than dense. Headings say what each clause is about, region tags flag where a rule changes, and every edit carries...
Section headings
Every heading names one subject, from what we collect to how you ask for a copy. Jump straight to the clause you need without reading the page end to end.
Region tags
A short tag marks any rule that changes by country. Where local law permits something different, the tag tells you so before you read the full clause body.
Date stamps
The revision date sits above the first heading and inside each changed clause, so you always know which wording was live when you opened your account with us.
Icon shortcuts
Small icons point to chat, email and account settings, so the fastest route to a data question is visible without hunting through menus on a small phone screen.
Short paragraphs
Clauses run to a few sentences each rather than long blocks. If a subject needs more room, we split it into its own heading instead of stacking detail.
Contact strip
The support details repeat near the foot of every policy page, so you do not have to scroll back to a clause you passed earlier just to find our address.