Terms page
Terms explain account conduct and platform rules. This Privacy Policy explains what personal data supports those rules, including identity checks, access logs and misuse checks.
LEGAL REFERENCE
Privacy Policy for your 777sp account
777sp keeps account, lobby and Pakistan payment privacy terms in one clear policy, so you can see what data we collect before you open your account. Read it...
Account dataDevice checksPayment recordsSupport privacy
How we handle your personal data
This Privacy Policy explains how 777sp collects, uses, stores and shares personal data linked to your account where local law permits. We may process your name, mobile number, login records, device details, location signals, account activity, support messages and payment references needed for JazzCash, Easypaisa, SadaPay and Raast handling. We use this data to create and protect your account, confirm payment status,
prevent misuse, respond to your questions and meet legal duties that apply in supported regions. We do not sell your personal data. Access is limited to trained staff, service providers that help run our platform, and authorities where a lawful request applies. We keep records only for business, security and legal needs, then remove or anonymise them when they are no longer
required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How we keep this policy reliable
We write this Privacy Policy from the way our service actually runs. That means account registration, payment status checks, device security and support records are described as operating teams handle them. We...
Operational drafting
The policy reflects real account flows, including mobile number checks, login sessions and payment references. We avoid vague promises and explain why each data category is needed.
Pakistan context
Our wording covers Pakistan-facing account use in supported regions. Payment examples use JazzCash, Easypaisa, SadaPay and Raast because those records affect privacy handling.
Security input
Security staff help define how device, session and access records are described. Those records help us detect account misuse and protect your personal data.
Support feedback
Questions received by support shape clearer privacy wording. If a request shows confusion around data access or correction, we use that learning in future edits.
Change control
When data handling changes, we check the policy text before release. This keeps your privacy expectations aligned with account, payment and support processing.
Limited access
Personal data is not open across the company. We restrict access by work need, keep internal controls, and log sensitive handling where systems allow.
PAGE ALIGNMENT
Where this policy connects with other pages
Our Privacy Policy sits beside other legal pages, but it has a narrower role. It explains data collection, use, storage, sharing and your privacy choices. If another page explains account rules or...
Cookie page
Cookie wording deals with browser storage and similar tools. This Privacy Policy shows how those signals connect with account security, analytics and preference handling.
Payment wording
Payment pages may explain cash-in and payout steps. This policy explains the data trail behind them, such as wallet references and status messages.
Promotion terms
Promotion terms describe eligibility and account credit handling. This Privacy Policy covers the personal data used to apply, track and resolve those account entries.
Security notices
Security notices may ask you to verify activity. This policy explains why device, location and session data may be checked during that process.
Support pages
Support pages tell you where to contact us. This policy explains how messages, attachments and identity checks are stored and handled after contact.
Account area
Your account area may show editable details. This policy explains how corrections, retention periods and removal requests are handled behind those visible fields.
LAYOUT CUES
Privacy details you can spot quickly
We design the Privacy Policy page so important data points are easy to find. The layout separates collection, use, sharing, security, retention and contact rights instead of burying...
Clear data categories
We name the main data types, such as account details...
Purpose labels
Each purpose is tied to a real need, such as...
Sharing boundaries
The policy separates internal access from service provider sharing and...
Retention wording
Retention is explained around business, security and legal need. We...
Rights section
You can see how to ask for access, correction or...
Contact prompts
Contact routes appear near the policy details, so privacy questions...
Common questions about your data
We may collect account details, mobile number, login records, device data, payment references, location signals and support messages. The exact data depends on how you use your account in supported regions.
JazzCash, Easypaisa, SadaPay and Raast activity creates references we need to confirm status, resolve disputes, protect accounts and keep records required for business and legal purposes.
No. We do not sell your personal data. Limited sharing may happen with service providers, security partners or authorities where a valid legal request applies.
Yes, you can contact us to correct inaccurate account details. We may ask for identity checks first, because changing personal data can affect access and payment records.
We keep records for business, security and legal needs, including account protection and payment traceability. When data is no longer required, we remove or anonymise it where possible.
Device data helps us secure your account, manage sessions and identify unusual access. It may include browser type, device signals, IP data and login timing.
Use live chat or email and state that your request concerns privacy. Include your account ID, but do not send wallet PINs, passwords or unnecessary sensitive details.