Privacy Policy
This page covers what we collect, why we hold it, how long we keep it, and how you ask us to correct or remove a record tied to your account.
Your privacy policy sits at the centre of how sixs bet runs your account. We set out what we collect when you register, why we hold it, and...
We keep one privacy policy for the whole of sixs bet and apply it the same way whether you reach us on desktop or on a phone. Where local law permits, we process your account details to open and run your account, to clear transfers through JazzCash, Easypaisa, SadaPay or Raast, and to hold the records auditors may later ask us to
produce. Some places carry their own rules on what we may store and for how long, so this wording adapts to supported regions rather than promising one global standard. You decide what you hand over, and we tell you what happens if you decline. If a clause does not fit the law where you live, that local rule wins over this page.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Write to our team the moment something about your record looks wrong and we will walk you through what we hold. Support reads every privacy request by hand, checks the account reference you give, and replies in the channel you used, keeping a written trail as it goes.
Open live chat from your signed-in account and ask about our privacy policy directly. Our team covers Pakistani hours every day, verifies you with your registered number, and answers data questions while you wait.
Send a written request to our privacy mailbox and we reply from a monitored address. Use it for access requests, corrections or deletions, and attach your account reference so we can match your record without delay.
Help pages inside your account explain what the privacy policy covers before you ever write to us. Raise the question from there and the whole thread stays attached to your profile for later.
We maintain this page in-house rather than lifting it from a shared template. Every version carries a date, earlier wording stays on file, and each edit passes the people who run accounts...
A small in-house group owns this privacy policy, and every version carries a change date. When a rule shifts you see the update instead of a silent edit buried somewhere on the site.
We write in plain English for Pakistan rather than legal filler. Where a term carries a technical meaning, we explain it in the same paragraph so you can judge whether to share the detail we ask for.
We keep an internal map of every system that touches your account data, from the login you create to the rail you pick for a payout, so we can tell you where details travel.
Edits are logged with the reason behind them. If our handling of JazzCash, Easypaisa, SadaPay or Raast records changes, the log shows what moved, when, and which clause it touched.
Questions you raise in chat or email feed straight back into this text. When the same point comes up twice, we rewrite the clause so the next reader finds the answer first time.
Outside writers do not touch this text. The team that checks withdrawals and verifies accounts also owns the wording, which keeps the promise here close to daily practice on the platform.
Our privacy policy, terms and cookie pages are written to sit together without contradicting one another. If one page states a retention period, the others follow the same line, so reading them...
This page covers what we collect, why we hold it, how long we keep it, and how you ask us to correct or remove a record tied to your account.
The terms describe the deal between you and sixs bet for using the lobby, while the privacy policy handles the data behind that deal. Neither page answers the other's question.
Cookies sit under the same privacy policy rather than beside it. The notice lists the categories we set and the switches you can use to limit tracking on your device.
Wording for JazzCash, Easypaisa, SadaPay, NayaPay and Raast explains clearing times and limits, while the privacy policy explains what we retain from each transfer and how long that record stays on file.
House rules for how you use your login and the privacy policy for how we protect it share no conflicting lines. Where the two meet, both point to one retention period.
Checks wording appears in one place only, so the same standard applies when you open your account and again when you ask for a payout to a Pakistani rail.
Every policy page ends with the same support routes, so one request can mention the privacy policy, the terms and the cookie notice without you repeating the same details twice.
Scroll this page and you meet the same blocks found on every sixs bet policy page: a summary strip, a dated body of clauses, short cards that break...