Account terms
Account terms may mention verification or security duties, while this Privacy Policy explains the data behind those duties and the purpose for keeping each related record.
LEGAL REFERENCE
Privacy Policy for your account
Starburst casino connects slots, live tables and sportsbook access to one account record, and this Privacy Policy explains how that record is handled. Read it before you open...
Pakistan data contextAccount privacy choicesPayment record handlingSupport contact paths
Pakistan data stance for your account
This Privacy Policy describes how starburst casino handles your account data when you access our site from Pakistan or other supported regions where local law permits. We collect details you provide during account opening, identity checks, payment activity, device access and support contact. We use that data to run account security, process payout requests, keep payment records tied to JazzCash, Easypaisa, SadaPay
or Raast activity, and respond when you ask for help. We do not write this policy as a blanket permission to use your data for unrelated purposes. When we need extra consent for a specific use, we present that request separately. We also keep access to your records limited to staff or service partners who need it for account, security or legal
handling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How we keep policy care current
We treat the Privacy Policy as an operating control, not a static page. Our product, support and security teams check the wording when account flows change, when local payment handling changes, or...
Field mapping
We map account forms to the policy wording so each requested field has a stated purpose. If a field is no longer needed, it is flagged for removal from future flows.
Payment trace
Payment records are described by rail, reference and timing, not by unnecessary card-style data. JazzCash, Easypaisa, SadaPay and Raast checks stay linked to account matching only.
Access control
Staff access is limited by role, so support can see what is needed for your case while sensitive verification records remain restricted to trained account-security handlers.
Device signals
We use device and session signals to protect account access, detect unusual logins and keep your profile stable across mobile browser, app shell or larger screen sessions.
Partner limits
Service partners receive only the data needed for hosting, payments, security checks or support delivery. We expect each partner to handle that data under written duties.
Change log
When the Privacy Policy changes in a meaningful way, we update the page date and may add an account message so you can read the new wording before continuing.
PAGE ALIGNMENT
Consistent privacy wording across pages
Privacy wording should not change depending on where you read it. We keep this page aligned with account terms, cookie wording, payment help and support scripts. If another page explains a data...
Cookie wording
Cookie wording describes browser storage and session tools. This page connects those tools to account access, fraud checks, preference handling and measurement of page reliability.
Payment help
Payment help may explain JazzCash, Easypaisa, SadaPay and Raast steps. The Privacy Policy explains how related references, timestamps and account matches are stored.
Support scripts
Support scripts ask for only the data needed to handle your case. This policy explains why those checks exist and how the request trail is kept.
Security prompts
Security prompts can request fresh verification after unusual activity. The Privacy Policy describes how those signals help protect access without opening wider data use.
Profile settings
Profile settings let you adjust contact details and some preferences. This policy explains which changes affect account records, message routing and verification history.
Promo controls
If you choose to receive offer messages, the Privacy Policy explains the contact data involved and how you can change message choices through account or support paths.
POLICY LAYOUT
Policy layout you can read fast
We designed this page so you can find privacy details without searching through unrelated copy. The layout groups collection, use, sharing, storage and contact rights in a clear...
Plain headings
Headings use everyday terms such as account data, payment records...
Local context
Pakistan references appear where they matter, especially around JazzCash, Easypaisa...
Short clauses
Clauses are kept compact, with one purpose per paragraph where...
Contact cues
Contact routes are repeated near rights and correction wording, so...
Security labels
Security wording is labelled around login checks, device signals and...
Change markers
Policy updates are marked by date and visible wording changes...
Privacy Policy questions answered
We collect the details needed to create and secure your account, such as contact data, login credentials, device signals and verification records. We also store support contact history when you ask for help.
We keep payment references, timing and account links needed to process requests, match receipts and answer queries. We do not ask you to send full wallet credentials through support chats.
Device and session data helps us recognise your access pattern, keep the account stable and detect unusual logins. It is used for account security and service reliability, not unrelated profiling.
Yes. Contact our privacy email with the account email or phone number tied to your profile. We verify the request before sharing data so another person cannot obtain your record.
We keep records for as long as needed for account operation, payment handling, security checks, support history and legal duties. When data is no longer needed, we remove or de-identify it.
You can adjust message choices through account settings or support where available. Some service messages, such as security or payment status alerts, may still be sent when needed.