How dewi21 Handles Your Privacy
dewi21 gives you a clear Privacy Policy before you open your account, covering the data we collect, why we use it, and when we may share it for...
Our Pakistan Privacy Policy Posture
This Privacy Policy explains how dewi21 handles personal data connected to your account, verification steps, device access, game session records, support chats and payout checks. We collect only what we need to run the account flow, respond to your requests, prevent misuse and meet lawful duties in supported regions. When you use Pakistani payment rails, we may record transaction references, account names,
time stamps and status messages so your balance and payout requests can be matched correctly. We do not sell your personal data. Limited sharing may happen with service providers who help us process payments, secure accounts, host systems or answer support messages. We keep those providers tied to privacy duties and we limit access to the task they perform for us.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Questions Reach Us Directly
You can contact us about this Privacy Policy without using a public channel. We ask for enough account detail to locate your record, then we handle the request through support tools with restricted access. If your question concerns a payment reference, include the rail name and date so we can trace the privacy record faster.
Email privacy desk
Send your privacy request by email with your dewi21 account name, contact number and the exact record you want us to check, correct or explain.
Live chat handoff
Use chat to ask for privacy help, and our agent can move the case to the team that handles account records and payment references.
Payment record query
For JazzCash, Easypaisa, SadaPay or Raast concerns, share the transaction time and reference so we can confirm what data is stored.
How We Keep This Policy Current
Our Privacy Policy is maintained as an operating document, not a decorative page. We check it against account flows, support tooling, payment handling and device security changes before wording is updated. That...
Named policy owner
A dewi21 internal owner keeps privacy wording tied to account flows, support access and payment record handling, so changes are tracked before publication.
Data map checks
We compare the Privacy Policy with our data map for account details, device logs, payment references and support conversations used during service handling.
Payment rail checks
When JazzCash, Easypaisa, SadaPay or Raast handling changes, we check whether this Privacy Policy needs clearer wording about stored transaction records.
Access control testing
We limit staff access to privacy records by role and check that support agents see only the account data needed for the case.
Request response logs
Your privacy requests are logged with time, channel and outcome so we can confirm how the request was handled if you contact us again.
Plain language edits
We remove unclear legal phrasing where possible and explain privacy choices in direct Pakistani English so you know what each section means.
Same Privacy Language Across Pages
This Privacy Policy connects with our other legal pages through the same definitions and account terms. If another page discusses cookies, promotions, payment handling or account security, we...
| Cookie page match | Where cookies support sign-in, session safety or preference storage, this Privacy Policy uses matching language so you understand both browser and account data. |
|---|---|
| Terms page match | Our account terms and this Privacy Policy use the same account identity wording, which helps you connect privacy duties with your account access. |
| Promo page match | If a promotion needs account checks, this Privacy Policy explains the data use behind eligibility, record matching and support handling. |
| Security page match | Device logs, login alerts and access checks are described with the same privacy meaning wherever our security pages mention account protection. |
| Payment page match | Payment wording stays consistent with this Privacy Policy when we describe transaction references, account names and status records from Pakistan payment rails. |
| Support page match | Support forms and chat prompts collect details for case handling, and this Privacy Policy explains how those records are stored and limited. |
| Change notice match | When our privacy wording changes, we align the date and change message across legal pages so you can see what moved. |
Visible Privacy Cues On Page
We design this Privacy Policy so you can scan the privacy parts that matter before sharing account details. The page separates collection, use, sharing, storage and...
Collection block
This block lists the account, device, support and payment records we may collect, helping you see the Privacy Policy scope quickly.
Purpose block
We explain why each data group is used, from account access and balance records to support replies and misuse prevention.
Sharing block
This area names the limited provider categories that may handle data for hosting, payment processing, support tooling or account security.
Storage block
We describe retention in practical terms, including why some records remain longer for account disputes, payment traces or lawful duties.
Rights block
You can see how to ask for access, correction or removal where local law permits and where account records allow it.
Contact block
The contact block keeps privacy support separate from general service questions, so your request reaches the correct handling route.