Legal Terms For Your Account
cd77 sets out your account rules, privacy duties, and Pakistan access terms in plain English so you know where you stand before you open an account. Read the...
How Our Legal Terms Apply
Our legal stance is written for cross-border access and Pakistan-facing account flow, not as a promise that every location can use every service. You may open and use cd77 only where local law permits, and you remain responsible for checking the rules that apply to your device, address, and payment rail. We separate contract terms, privacy duties, cookie controls, dispute steps, and
promotional rules so each page can be read on its own. If a rule changes, we aim to place the updated wording on the relevant policy page and apply it from the stated update time. JazzCash, Easypaisa, SadaPay, and Raast are named only where a legal duty needs local payment context. Keep copies of messages and transaction references because they help us
match your request with the clause involved.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep Text Current
Our legal pages are maintained like working account documents. Each update is checked for plain Pakistani English, consistent clause names, and fit with the way cd77 handles registration, verification, local payment references...
Version dates
Each policy page carries a date marker so you can see which wording applies. When a clause changes, we keep the new text tied to the page where it belongs.
Plain wording
We avoid legal padding where simple wording can do the job. Short clauses help you understand account duties before you agree to them or raise a dispute.
Local references
Pakistan references are used only where they affect access, verification, or payment context. We do not turn local names into promises about availability in every area.
Privacy handoff
Privacy requests move through a separate record path because identity data needs tighter handling. The legal page points you to that route when personal data is involved.
Security checks
Account security clauses match our actual login, device, and verification controls. If we add a control, the legal wording is checked so duties remain aligned.
Dispute record
When you raise a legal dispute, we record the clause, account action, time, and evidence supplied. That record helps both sides track the issue clearly.
How Our Policy Pages Align
Your account touches several policy pages at once, so we keep names and remedies aligned across them. The legal page anchors the contract, while privacy, cookie, promotion, and...
| Terms page | The terms page sets the account contract and core duties. It explains eligibility wording, acceptance, suspension reasons, dispute steps, and how other policy pages connect to those clauses. |
|---|---|
| Privacy page | The privacy page handles identity data, device logs, and records linked to verification. It uses the same account labels as the legal page so requests do not split across terms. |
| Cookie page | The cookie page explains browser storage and session tools. Its labels match the legal wording for login security, device recognition, and consent choices where local law permits. |
| Promotions page | The promotions page explains offer conditions, expiry timing, wagering wording, and account eligibility. Its rules sit under the main contract rather than replacing the legal terms. |
| Payment clauses | Payment clauses cover verification, transaction records, and local rail references. They are written to work with JazzCash, Easypaisa, SadaPay, and Raast context without promising universal access. |
| Account action | Account action wording explains freezes, checks, closures, and dispute handling. We use the same status names across policy pages so you can follow a case without mixed labels. |
| Change notices | Change wording explains when a policy update applies and where it appears. We aim to keep updates visible on the page that actually changed. |
Legal Page Layout Cues
The legal area is built to be scanned before you commit to an account action. We use short labels, visible dates, clause anchors, and plain status...
Date marker
A visible date marker helps you check whether the clause you read matches the current policy. Keep that date when you quote wording in a support request.
Clause anchors
Clause anchors let you point us to the exact legal sentence instead of describing a whole page. That keeps account, privacy, and dispute questions easier to trace.
Status labels
Status labels show whether a section applies to access, verification, privacy, or dispute handling. The label helps you avoid mixing policy duties with lobby features.
Plain summaries
Short summaries introduce longer clauses without changing their effect. They help you decide whether to read the full wording before opening your account or sending a request.
Evidence prompts
Evidence prompts list the references we may need, such as dates, transaction IDs, or screenshots. Supplying them early helps us connect your question to the legal record.
Local markers
Local markers appear where Pakistan access or payment context matters. They remind you that availability depends on supported regions and rules that apply where you are.