Shared Definitions
Terms like account, personal data and supported region carry the same meaning on every tdd777 policy page, so you never have to guess which version applies when you switch.
LEGAL REFERENCE
How tdd777 Handles Your Privacy
Privacy here is a live page, not an archive. This policy explains what tdd777 collects when you open an account, which records we keep, and how far your...
Account Data ControlEncrypted Payment DetailsClear Retention WindowsSupport You Can Reach
What This Privacy Policy Covers
tdd777 operates where local law permits, and this policy is written for supported regions, including Pakistan. It covers the personal data you hand us when you register, verify, deposit or contact support, and it sets out the lawful basis we rely on for each step. Where a local rule asks for more than this page promises, the local rule wins and we
follow it. Where a rule asks for less, we keep the standards described here anyway. Read it as our public posture: what we hold, how long we hold it, and how you ask us to change or delete it. Requests from outside a supported region may be limited, and we will say so plainly to you.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE WRITE IT
Why You Can Read This Plainly
Every line here is written by the team that runs tdd777, not bought from an agency. We name the rails we actually use, the support hours we actually...
Written In-House
Signed off by the same operations team that handles your account every day, so the wording on this page matches...
Dated Revisions
Each update carries a revision date at the head of the page, so you can see when a clause changed...
Named Payment Rails
We list JazzCash, Easypaisa, SadaPay, NayaPay and Raast by name because those are the routes we genuinely support, rather than...
Real Support Hours
Live chat runs from 9am to midnight Pakistan time, seven days a week, and email is answered within two working...
No Hidden Profiling
We describe the categories we use for account security and service quality, and no others. If a category is not...
Your Copy On Request
Ask and we send a structured copy of the personal data tied to your account, covering registration details, transaction history...
ACROSS OUR PAGES
How This Page Sits With Others
Our policy family is deliberately consistent. This privacy page covers data, the terms page covers account rules, and the payment page covers transaction handling. The same definitions and the same contact routes...
Same Region Wording
Where we mention supported regions or local law, we use identical phrasing across the terms, privacy and payment pages so jurisdiction limits read the same everywhere you look.
One Contact Route
Email and live chat details are repeated on each policy page rather than scattered, meaning a data request reaches the same privacy team no matter which page you started from.
No Contradictions
If a clause here appears to conflict with the terms page, the stricter position is honoured while we investigate, and the weaker wording is corrected within a few days.
Version History
Each policy page shows when it was last revised, and the amendment log names the clause that changed so you can compare an older copy with the current one.
Same Retention Rules
Deletion windows quoted here match the schedules on our payment and account pages, so you get one answer about how long transaction records are kept after you close an account.
Reading Order
We link the policy pages together in a fixed order so you can move from privacy to terms to payments without losing your place or re-reading shared context.
ON-SCREEN ELEMENTS
Elements You See On Screen
The page in front of you is built from a few visible pieces. A summary block opens with the short version of each promise. Anchored headings let you...
Summary Block
The opening block gives you the short version first, so...
Anchored Headings
Each section carries a stable anchor, which means a support...
Payment Chip Row
Local rails appear as small chips inside the section that...
Mobile First Text
Paragraphs are written for a narrow screen first, keeping sentences...
Revision Stamp
A date line at the head of the page records...
Plain Language
We avoid legal padding wherever the meaning survives without it...
Questions We Handle About Privacy
Your name, contact details, date of birth, device details and the payment reference tied to your chosen rail. We collect the minimum needed to run your account and meet the checks the region requires.
Only the transaction reference needed to confirm a deposit or withdrawal through JazzCash, Easypaisa, SadaPay, NayaPay or Raast. We do not sell your contact details, and we do not pass your data to unrelated third parties.
Account records stay while your account is open and for a defined period afterwards where the region requires it. Support tickets and transaction logs follow shorter schedules, and you can ask for the exact window.
Yes. Request it from live chat or the privacy mailbox and we compile a structured file covering your registration details, transaction history and any support tickets raised under your reference.
We end active processing, keep only what the region's record-keeping rules demand, and delete the rest on the published schedule. You can confirm the status of that deletion through support.
We use encrypted connections, device checks at login and session timeouts on mobile. Keeping your password private and your device updated matters just as much as anything we do on our side.
Any amendment is dated on this page, and material changes that affect how your data is used are flagged to you through your account notifications before they take effect.