dewi311 Privacy Policy For Pakistan
dewi311 keeps account, lobby and payment privacy terms in one clear policy, so you know what data we collect before you open your account. We explain why each...
How We Handle Your Data
This Privacy Policy applies when you use dewi311 in supported regions where local law permits. We collect account details, device signals, login records, payment references and support messages to operate your account, verify access, protect balances and answer your requests. We do not ask for extra data without a reason tied to account service, identity checks, security checks or legal duties. Payment
references from Pakistani rails are used to match your account activity, not to create unrelated profiles. If a law, regulator or banking partner requires a record, we keep only what is needed for that purpose.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How Our Policy Stays Accurate
We write this policy from our own account flow, support desk and payment matching process. When the product changes, we check whether a data type, retention period or...
Operational source
Policy wording is taken from account creation, login, wallet matching and support handling steps that our teams use daily. We...
Local payment checks
JazzCash, Easypaisa, SadaPay and Raast references are described as matching records, not banking access. We record transaction references so your...
Access controls
Internal account tools are limited by role, so support staff see only the records needed for the request. Sensitive changes...
Change log discipline
When we change this policy, we align the date, affected data category and reason before publishing. That helps you see...
Device clarity
We explain device and session records because they affect account safety. IP address, browser type and login timing help us...
Request handling
Privacy requests are logged with time, channel and outcome, so we can answer consistently. We do not use a support...
Consistency Across Legal Pages
Our Privacy Policy works with the rest of the legal pages, but it has its own job. Terms pages explain account rules; this page explains data handling. If...
| Terms page link | Account rules may mention verification, but this policy explains the personal details used for that check. We separate conduct rules from privacy handling so each page stays focused. |
|---|---|
| Cookie page link | Cookie wording covers browser storage, while this policy explains how those signals connect with session security. If cookie settings change, we check the related privacy paragraph too. |
| Payment page link | Wallet pages explain how a transaction is made; this policy explains how receipt references are stored. JazzCash, Easypaisa, SadaPay and Raast records are handled for account matching and checks. |
| Security page link | Security wording covers account protection steps, while this policy states what login data supports those steps. That includes device type, location signals and recent session history. |
| Promo page link | If a reward page asks for eligibility checks, this policy explains the account data used to confirm them. We do not add unrelated personal profiling for a campaign check. |
| Support page link | Support pages tell you how to reach us; this policy explains how your messages are stored. We keep request history to resolve repeated privacy or account questions. |
| Update consistency | When one legal page changes a data reference, we check matching wording across the set. That reduces mixed messages about access logs, wallet receipts or identity checks. |
What You See On This Policy
This page is built to make privacy decisions easier before you join, browse or contact us. The layout separates collection, use, storage, sharing and request rights, so you...