Terms page
The terms page covers account duties and platform access. This legal page points back to those duties when a clause affects registration, login or account status.
2ds puts the account terms, privacy duties and cash-out rules in one legal space for Pakistan, so you can read the deal before you open your account. Where...
This legal page sets the rules we apply to your account record, privacy handling, identity checks, cash-out requests and service access in supported regions of Pakistan. It is not a licence statement or a promise that access is available in every place; where local law permits, we operate under the terms shown here and in connected policy pages. We may ask for
clear documents when withdrawals, charge queries or account recovery need verification, and we keep those steps tied to the purpose requested. JazzCash, Easypaisa, SadaPay and Raast names may appear in payment records only to match the transaction route you used. If a clause changes, we place the updated wording on this page before applying it to future activity on 2ds.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Legal questions need clear routing, not a generic inbox shuffle. We keep account, privacy and cash-out queries separated so the right team can read your request and match it with the records behind your 2ds account.
Ask us to explain a clause tied to account access, password recovery or verification. Share your registered contact detail only, and we will tell you which record we need next.
Use the privacy route when you want to ask about stored profile data, device logs or document copies. We check ownership before discussing any personal record with you.
For withdrawal status tied to legal checks, send the transaction time, route and account name. We compare those details with our ledger before giving a final response.
Our legal wording is written from the same account flows we operate every day. When support, payments or security steps change, we check the affected clauses before asking...
Each legal page has an internal owner who checks whether the wording still matches the account path, privacy workflow and...
When we alter a clause, we keep a record of the reason and the affected section. That helps support answer...
We use clear Pakistani English for legal copy so you can understand account duties, document requests and cash-out checks without...
Document checks are linked to specific legal reasons such as ownership, withdrawal approval or account recovery. We avoid asking for...
Payment route names such as JazzCash, Easypaisa, SadaPay and Raast are used to match records. They do not change the...
Our support scripts are checked against the terms here, so a legal answer in chat should not conflict with the...
The legal page sits beside privacy, account and transaction policies. We keep the pages connected so you do not have to guess which clause controls a verification request, data question or access...
The terms page covers account duties and platform access. This legal page points back to those duties when a clause affects registration, login or account status.
The privacy page explains data handling in greater depth. This legal page summarises when identity, device or payment records may be checked for lawful account purposes.
The cash-out policy explains timing and verification steps. This page states the legal reason we may hold a request while ownership or route details are checked.
The cookie page covers browser storage and similar tools. This legal page connects those tools to account security, session checks and fraud prevention duties.
The security page explains access controls and login protection. This page sets the legal basis for action when account safety or record accuracy is at stake.
The support policy covers response handling and evidence requests. This legal page explains why we may need proof before discussing private account matters.
The updates page records wording changes across policy pages. This legal page explains when changed clauses apply to future account activity on 2ds.
We design the legal area so you can find the clause you need before joining or sending a support request. Headings, chips and short blocks reduce...
Each visible block is written to answer one legal point, such as account access, data use or verification. You can read the section without searching through unrelated wording.
Context chips name Pakistan and common account routes where needed. They help you see when a clause relates to records, not to a separate service promise.
Headings describe the legal subject directly, so you can move from privacy to account checks without decoding labels. We avoid vague labels on policy pages.
Where a clause affects something you may do, we state the action plainly. Examples include opening an account, updating details or asking about a withdrawal.
Contact prompts sit near the legal subject they relate to. That way, you can ask the right team instead of repeating the same account issue twice.
When wording changes, the page structure helps us show the affected area clearly. You can return later and compare the clause with your current account need.