Terms connection
The account terms may explain when records are needed for disputes or access control. This privacy page explains the data side of that same process and your available request routes.
6nn keeps one privacy page for your account data, casino activity, slot records and sportsbook access where local law permits. Read it before you open your account so...
This Privacy Policy explains how we handle personal data when you create a 6nn account, sign in, manage your wallet, contact support or access the lobby from supported regions. We collect only the data needed to run your account flow, verify access, process requests, detect misuse and meet record keeping duties that apply where local law permits. Payment references from Pakistani rails
are used to match your request with your 6nn wallet record; they are not used to sell your profile. We may share limited data with processors that help with hosting, security, analytics, customer care and transaction checks. We keep records for as long as needed for account, legal and security purposes, then remove or anonymise them when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We treat this Privacy Policy as an operating document, not a static legal page. Our checks involve account, wallet, security and support teams so the wording reflects how 6nn actually handles your...
We map sign-in, device, wallet and support records before writing policy text. That helps us explain what we hold, why we hold it and which team can act on your request.
Security checks cover login alerts, unusual wallet activity and session controls. The policy states these uses plainly so you understand why some data is retained after account changes.
Pakistan payment references are described as matching records, not public profile data. We separate JazzCash, Easypaisa, SadaPay and Raast handling from wider account activity in our internal checks.
Our cookie wording is checked against the tags running on 6nn pages. We describe essential, preference and analytics uses without hiding them behind vague technical phrasing.
We compare retention wording with account, security and wallet record needs. If a record must stay for legal or dispute reasons, the policy explains that limit clearly.
Support scripts mirror this policy so replies stay consistent. When you ask for access, correction or deletion, agents follow the same privacy steps described on this page.
Your privacy rights connect with our other legal pages, but each page has its own job. This Privacy Policy explains data collection and use, while related terms explain account rules, promotions, cookies...
The account terms may explain when records are needed for disputes or access control. This privacy page explains the data side of that same process and your available request routes.
Cookie wording here matches the choices shown in our cookie panel. If the panel label changes, we adjust the policy text so your controls stay easy to recognise.
Promo history may be retained to resolve eligibility questions and account queries. This policy explains that retention as account data handling, not as a separate marketing claim.
Security pages may describe password steps or device checks. This Privacy Policy explains why those checks create records and how long we may need to keep them.
When you raise a complaint, we may keep chat logs, emails and wallet references. The privacy wording explains how those files support fair handling and later audit checks.
Access wording across our pages uses supported regions and where local law permits. This policy applies the same phrasing when explaining data collection for Pakistan account use.
When legal page wording changes, we aim to keep dates and headings aligned. That makes it easier for you to see which privacy text applies to your account.
The page layout is built to help you find privacy answers quickly without reading unrelated lobby copy. We separate data categories, use plain labels, place contact routes near...