123apps - Read the rules before joining
123apps keeps account terms, privacy rules and access conditions together so you can understand the legal basis for using our service. Read the clauses before you open your...
Our legal terms follow your region
Our legal pages explain the conditions that apply when you create an account, access the lobby or use a supported payment rail. Availability depends on your location and local law. You must provide accurate account details, keep your login private and complete any checks requested for account security or withdrawals. JazzCash, Easypaisa, SadaPay and Raast appear as context chips because each rail
can involve separate processing steps, verification requests or availability conditions. We may update a clause when our account flow, privacy handling or regional access rules change. The date shown on each policy page helps you identify the current version. If a clause does not answer your situation, contact us before continuing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we maintain legal clarity
We write our policies around the account steps you actually see. Each clause is checked against the sign-in flow, privacy handling, verification process and supported regional access wording before a revised version...
Version date
Each policy page carries a visible date so you can identify the current wording and recognise when a revised clause has replaced an earlier version.
Plain-language clauses
We keep clauses direct and separate account duties from privacy rights, verification steps and regional availability. This makes the applicable rule easier to locate.
Regional wording
Access statements use supported-regions wording and refer to local law. We do not present availability as identical across every location or account circumstance.
Security alignment
Our legal wording reflects practical account protections, including private login details, identity checks where required and secure document submission for account-specific verification steps.
Payment context
Where payment rails affect a clause, we name JazzCash, Easypaisa, SadaPay or Raast clearly and explain that processing conditions can vary by account.
Revision control
We record policy changes before publication and keep related pages aligned when a revised clause affects privacy, account access or verification wording elsewhere.
How our legal pages fit together
Our legal pages work as a connected set. Start with the account terms, then read the related privacy, cookie, security and access clauses that apply to your situation...
Visible elements across our policies
We make key legal markers easy to spot before you act. Dates, clause headings, regional wording and contact routes appear where they are relevant, giving you...
Current date marker
A visible date helps you recognise the current policy version before you rely on a clause about account access, privacy handling or verification requirements.
Clause headings
Short headings separate privacy, account security, payment context and regional access rules, so you can locate the clause connected with your immediate question.
Regional statement
Access clauses state that service availability depends on supported regions and local law, rather than presenting one rule as applicable to every location.
Contact route
Legal pages point you towards a contact path when a clause needs account-specific clarification, including privacy requests and questions about verification requirements.
Rail context chips
JazzCash, Easypaisa, SadaPay and Raast chips identify where payment-related legal context applies without turning the policy page into a transaction screen.
Linked clauses
Related policy links connect account terms with privacy, cookie, security and regional access wording when one action is governed by more than one clause.