Terms Of Use
That page records what you agree to when you open an account. This policy sits beside it and explains what happens to the data that account goes on to generate.
One page, in everyday Pakistani English, setting out what hugo casino records when you open an account, why we keep that data and the choices you hold over...
hugo casino keeps one privacy policy for all supported regions, though wording can shift where local law permits something different. When you open an account we record your name, date of birth, contact number and sign-in email, plus the identity documents we request once activity reaches the point where we must confirm who you are. Move money through JazzCash, Easypaisa, SadaPay, Nayapay
or Raast and our processor returns a reference number and status only — never a wallet PIN or a bank login. Device data such as IP address, browser type and session logs is stored too, because that is how a hijacked account gets spotted early. Where local law permits, contracted partners run some checks; they may use your data for the task
we set them and nothing else, then must delete it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If a clause here reads oddly, ask us rather than guess. Live chat runs around the clock, email is answered within a working day, and our Karachi-hours phone desk takes anything that needs a human voice. Quote your account email so the right record is pulled first time, and tell us in the first message if you want a copy of your data or a correction made to it.
Open chat from your account menu and an agent joins within minutes, day or night. Use it for quick checks on what we store and why we store it.
Email our data desk for copies, corrections or deletion requests. Receipt is confirmed the same working day with a reference number you can follow through to closure.
Some questions are easier spoken aloud. Our daytime line handles those, and having your account email ready lets the agent locate your record before the call goes further.
Anyone can publish a privacy page. What counts is whether the habits behind it hold up when you look closely. The points below describe how records are actually...
Every edit to this page passes a named data-protection lead before it goes live, so the wording is signed off...
We write for readers in Karachi, Lahore and Islamabad first. Jargon gets swapped for everyday wording so you can follow...
Records stay while your account is open and for the period local rules demand afterwards. Once that window closes, files...
Every staff look-up of your file is stamped with a time and a reason. Unusual patterns raise a flag with...
Data moving between your device and our servers travels over TLS, and stored records sit encrypted at rest. Wallet references...
Your profile is not sold to brokers or listed with advertising networks. Marketing from us follows only the preferences you...
This policy does not stand alone. Sibling pages handle cookies, identity checks, payouts and market rules, and they should read consistently whenever you move from one to the next. We hold the...
That page records what you agree to when you open an account. This policy sits beside it and explains what happens to the data that account goes on to generate.
Cookies get a page of their own because your browser sets many of them. It names each category and shows how to refuse anything optional without losing access to the lobby.
Identity checks and record keeping are described there in full. The retention window matches what you read here, so the two pages never contradict each other on timing.
Offers carry their own conditions on who qualifies and when they lapse. Nothing in those conditions changes how your personal data is stored, shared or deleted.
Payout timing, verification steps and the reference numbers that appear on your statement are set out there, while this policy covers the data sitting behind them.
Bet settlement and market rules live on that page. They matter here only because wagers create records we are obliged to keep for a set period.
Two-factor setup, password resets and session control are explained there. Alongside this policy it closes the loop around your account and the data inside it.
A few design choices make this policy easier to read on a phone as much as on a laptop. They exist so you can reach the...
A short block near the start repeats the essentials in one glance, built for anyone reading on a phone between shifts rather than sitting down with a full document.
A contents strip lets you skip straight to retention, sharing or your own rights instead of scrolling the whole document to find a single paragraph.
Every edit carries a date, so you can tell at a glance whether the version you saved last month still matches the text we publish today.
Wording shifts between supported regions, so a small selector shows which version applies to the country listed on your account, keeping you off the wrong text.
A print-friendly layout strips the design down to plain text, handy when you want a copy on paper or filed away on your own laptop for later reference.
A short form at the foot of the page sends a data question straight to the desk that owns this policy, instead of routing it through general support first.