Terms page boundary
Our Terms may describe account conduct, but privacy wording here explains what personal data supports enforcement, account checks and service records without mixing rules with data rights.
LEGAL REFERENCE
Privacy Policy for your account
Clear account-data rules, Pakistan payment checks and privacy contact routes sit on this page so you know how sloat pk handles your details. Open your account only after...
Account data usePakistan payment checksPrivacy contact pathPolicy change alerts
How we handle your details
This Privacy Policy explains how we collect, use, store and share data linked to your sloat pk account where local law permits. We collect details you provide at account creation, login records, device signals, transaction references and support messages so we can run account access, verify payments, handle withdrawals and answer privacy requests. JazzCash, Easypaisa, SadaPay and Raast references may be checked
against your account name and mobile number before a payout is released. We keep records only for service, security, legal and audit needs, then remove or anonymise them when they are no longer required. If you ask us to correct or access your data, we verify you first so your account is not exposed to another person.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY CHECKS
How this policy stays accurate
We treat this Privacy Policy as an operating document, not a decorative page. Changes are checked against account flows, payment verification, support handling and security logs before the...
Account flow mapping
We compare each policy point with the account screens you use, including registration fields, login checks and profile edits, so...
Payment trace control
We check how JazzCash, Easypaisa, SadaPay and Raast references move through verification queues, payout approval and audit storage, then keep...
Security log limits
Login time, device type, IP pattern and session events help us detect account misuse. The policy explains these logs without...
Support message handling
Chats, emails and complaint records may contain personal details. We restrict access to staff who need the file, then retain...
Access request checks
Before we answer a data access or correction request, we confirm the account link through safer clues. This reduces the...
Update date discipline
When wording changes, we keep the new text on this page and avoid quiet edits that alter your rights without...
PAGE CONSISTENCY
Where this policy connects
This page sits beside our Terms and Cookie Policy, but it has a separate job. The Terms explain account rules, while this Privacy Policy explains data handling behind those rules. Cookie wording...
Cookie Policy link
Cookie wording covers browser storage, preferences and session signals. This Privacy Policy explains how those signals may connect to login security, account recognition and fraud checks.
Promotion records
If your account receives a promotion entry, this policy explains how eligibility data and message history are kept. It does not set the promotion rules themselves.
Withdrawal checks
Withdrawal pages explain payout steps; this policy explains the identity, mobile and transaction data used to verify that a payout request belongs to your account.
Support archive
Help pages explain how to contact us. This policy explains how those messages are stored, who may access them and when they may be deleted or anonymised.
Security settings
Account-security pages show available controls. This policy explains the personal records behind those controls, including login history, device clues and alerts linked to unusual access.
Regional access
Access may depend on supported regions and local law. This policy explains how location clues can be used for availability checks and account protection decisions.
PAGE MARKERS
Visible cues inside this policy
We designed this legal page so you can scan it without losing the privacy context. Headings identify what data is involved, short chips show Pakistan payment touchpoints, and...
Plain section headings
Each heading names the privacy matter before the paragraph begins...
Local context chips
Short chips mention JazzCash, Easypaisa, SadaPay and Raast only where...
Actionable contact cards
Contact cards explain what to include with a privacy request...
Policy-only wording
The page avoids broad lobby promises and keeps every paragraph...
Change awareness
Where the policy changes, we keep language direct and visible...
Mobile readable layout
Privacy text is split into short blocks for phone screens...
Privacy Policy questions answered
We collect account details you enter, login records, device clues, payment references, support messages and activity needed to run your account. We do not ask for data that has no service or security purpose.
JazzCash, Easypaisa, SadaPay and Raast references help us match a payment or withdrawal request to your account. The check reduces misdirected payouts and creates an audit trail for later privacy questions.
Yes. Contact us from your registered email or logged-in chat and state what needs correction. We verify the request first, then update eligible records or explain why a record must stay unchanged.
We share data only when needed for payment processing, security checks, service tools, legal requests or account operations. Any outside handling must relate to your sloat pk account and the purpose described here.
We keep records for account service, dispute handling, fraud prevention, payment audit and legal needs. When those reasons end, we delete, anonymise or reduce the record according to the data type.
Material changes appear on this page and may be flagged through account-facing messages. We avoid silent wording shifts that alter how your data is handled without giving you a clear chance to read them.