Privacy Policy for done 999
done 999 sets out how your account data, device signals and transaction records are handled before you open the lobby. Open your account with a clear privacy route...
How we handle your data
This Privacy Policy explains what we collect when you create an account, verify access, contact support, or use features available where local law permits. We collect only the data needed to run your account flow, protect sign-in sessions, process transaction checks, and answer your privacy requests. That may include your name, mobile number, email, device type, IP address, login time, KYC files
where required, and transaction references linked to JazzCash, Easypaisa, SadaPay or Raast. We keep records for operational, security, legal and dispute-handling reasons, then remove or anonymise them when they are no longer required. If we update this Privacy Policy, we place the current version on done999.onl so you can read the changes before continuing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about privacy
Your privacy questions should reach the team that can act on account records, not a generic mailbox. We separate privacy requests from routine help chats so corrections, access checks and deletion queries can be logged with the right account reference. Please include the mobile number or email linked to your done 999 account.
Email privacy desk
Ask us which account fields are stored, why we request them, and how you can ask for a correction. We answer from the help desk tied to done 999.
Live chat data query
Use live chat for a quick privacy routing check, especially if your mobile number changed. The agent may verify you before discussing any record linked to your account.
Account access request
If you want a copy of core account data, request it from the same profile you use on done 999. We may ask for proof before release.
Checks behind this policy
We keep this Privacy Policy practical by connecting each statement to an account action we operate ourselves. The language is checked against sign-in flow, payment verification, support handling and security logging. When...
Date stamp
Each policy pass checks whether the version date matches the copy shown on done999.onl. That helps you see when the privacy wording last changed.
Data map
We match policy clauses to account screens, support forms and security logs. If a field is collected, the reason should be clear in plain English.
Local wording
Privacy text is written for Pakistan in clear en-PK style. References to JazzCash, Easypaisa, SadaPay and Raast are included only where they affect records.
Security wording
We describe security logs without exposing controls that could weaken account protection. The policy explains categories of data, not private system rules.
Transaction trace
Where a transaction creates a reference number, we may store it for matching, dispute checks and audit trails. The policy states this in direct terms.
Change log
When privacy wording changes, we keep the current page visible at this path. You can return to it before sharing fresh account data.
Consistent privacy wording across pages
Privacy wording should not shift when you move between legal pages on done 999. We align this page with account terms, cookie wording and contact details, while keeping...
| Account terms | Terms explain account access rules, while this Privacy Policy explains the data behind those rules. We keep the two pages aligned so permissions do not conflict. |
|---|---|
| Cookie wording | Cookie text covers browser storage and session signals. This Privacy Policy connects those signals to account security, fraud checks and preference handling. |
| KYC handling | Where identity files are requested, this page explains why they may be stored, who can handle them, and when retention may be required. |
| Support scripts | Support teams receive privacy phrasing that matches this page. That reduces confusion when you ask about corrections, access copies or deletion requests. |
| Transaction records | Payment references are treated as privacy records when linked to your account. This page explains retention without turning into a cashier page. |
| Security alerts | Login alerts, device checks and suspicious access records sit under privacy handling. We describe them here so account protection remains transparent. |
| Policy updates | When related legal wording changes, this page is checked for matching privacy impact. We avoid hidden shifts between connected pages. |
Visible privacy layout markers
The Privacy Policy page is arranged so you can find the data clause you need without searching through unrelated copy. We use clear headings, short privacy badges and...