Privacy Policy for 804 slots
804 slots gives you a clear Privacy Policy before you open an account, covering account data, device checks, KYC files and payout records in one place. If you...
How our policy applies in Pakistan
This Privacy Policy applies to your 804 slots account when you access our brand home from Pakistan, where local law permits. We collect only the data needed to create and protect your account, confirm eligibility, run security checks, process payouts, respond to your messages and keep required records. Some data comes from you, such as your name, phone number and identity documents.
Some data is created during access, such as device signals, login time, IP region and transaction references from JazzCash, Easypaisa, SadaPay or Raast. We do not sell your personal data. We share it only with service partners who help us verify accounts, secure sessions, process transfers or meet lawful requests, and we keep them bound to defined use.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about privacy rights
Privacy questions should reach the team that can act on them. Tell us which account, phone number or transaction reference is involved, but do not send passwords or full card details. We log each request, check identity first and reply with the next step for your data concern.
Logged-in chat
Use live chat after logging in when your question concerns account data, device checks or KYC status. We verify you inside the session before discussing records, then attach the privacy ticket to your account.
Privacy email
Email us from the address connected to your account if you need copies, correction or deletion assessment. Include the last four digits of your phone number so we can match the request safely.
Transaction route
For JazzCash, Easypaisa, SadaPay or Raast record questions, share the transaction reference and date only. Our payout team confirms the log without asking for your app PIN or wallet password.
How we keep policy wording accountable
Policy wording matters because it sets the rules for your data. We keep this page aligned with our account screens, KYC flow, session logs and support scripts. When a process changes, our...
Account field checks
Account screens are checked against this Privacy Policy so the data requested during joining matches what this page explains. If a field becomes unnecessary, we remove it from the flow rather than storing it quietly.
KYC access control
KYC handling is separated from general support access. Only trained staff can view identity files, and every view is logged, making it easier to investigate a privacy complaint tied to your account.
Wallet record scope
Transaction data from JazzCash, Easypaisa, SadaPay and Raast is used to match transfers, prevent duplicate payout action and resolve disputes. We avoid collecting wallet login details because those stay with your provider.
Session security context
Device and IP signals are used for session safety, fraud checks and regional availability in supported regions. The policy names these uses so you understand why security data appears in account records.
Human privacy replies
Support replies follow prepared privacy scripts for access, correction and deletion questions, but your request is still checked by a human. That keeps answers consistent without hiding context from you.
Retention schedule
Retention periods are linked to account status, legal duties, disputes and payout records. When a record no longer has a valid reason, we delete it or anonymise it according to our schedule.
Consistency across our legal pages
Our Privacy Policy should not conflict with the other legal pages you read on 804 slots. We align definitions, data categories and contact paths across pages so you...
| Terms page | The Terms describe account rules; this Privacy Policy explains the data behind those rules. When both pages mention verification, the wording is aligned so you know why documents may be requested. |
|---|---|
| Cookie page | Our cookie page covers browser storage and tracking choices. This Privacy Policy connects those signals to account security, remembering preferences and measuring page performance without turning cookie wording into account rules. |
| KYC page | KYC wording explains what documents may be required, while this page explains how those files are stored, viewed and shared. Both pages use the same identity terms to reduce confusion. |
| Payout rules | Payout rules explain checks before release; this policy explains the transaction data used in those checks. JazzCash, Easypaisa, SadaPay and Raast references are handled as account records. |
| Security page | Security wording covers passwords, device alerts and suspicious access. The Privacy Policy explains which security signals are collected and how long related logs may be kept after a session ends. |
| Offer pages | Offer pages may request consent for messages or contact preferences. This Privacy Policy explains how you can change those choices and how we record consent before sending account-related updates. |
| Support page | The support page tells you where to contact us. This policy explains what we need to verify your identity before sharing, correcting or deleting account data connected to you. |
Privacy layout you can read quickly
The Privacy Policy page is designed to be scanned, not decoded. We place the main privacy points near the start, then separate rights, contact paths and...
Scope badge
The scope badge shows that the policy applies to 804 slots account access in supported regions. It helps you confirm you are reading the privacy text for this brand before sharing data.
Data category cards
Data category cards separate account details, device signals, KYC files, support messages and transaction records. Each card connects a data type with the reason we collect it and the teams that may handle it.
Rights panel
The rights panel puts access, correction, deletion assessment and objection requests in one place. We state that identity checks come first, so private records are not released to the wrong person.
Retention markers
Retention markers explain why some records are kept longer than others, especially KYC, payout and dispute logs. Clear timing language helps you understand what changes when an account is closed.
Contact chips
Contact chips show privacy chat, email and transaction-reference routes without mixing them into sales copy. You can choose the path that fits your data question and avoid repeating details.
Version cues
Version cues show when the policy text was last changed and which areas were updated. We use plain labels so you can spot meaningful edits without reading the whole page again.