Terms of use
This framework records the boundary of website use and illustrative content. Binding website, sales, and pilot terms are not yet approved by a legal owner, and this page is not a contract or offer.
No price, access, SLA, deployment, support, or commercial outcome is committed merely by viewing or using this website.
The website supports discovery and early evaluation.
Pages explain the product model, illustrative flows, availability boundaries, and conversation paths.
A real deployment requires separate review of scope, configuration, commercial terms, responsibilities, and agreement.
Interface names, times, values, and records may be illustrative.
Interactive examples explain intended behaviour and operating decisions; they are not customer data or performance claims.
Prototype, pilot, approval-required, and release-ready labels must be read in their stated context; technical existence alone does not mean public availability.
Illustrative prices and estimates do not replace a formal proposal.
Scope factors such as branches, workflows, hardware, deployment, support, and operating location can affect a proposal.
Price, tax, timing, payment, and services become authoritative only in an approved commercial source and the agreement for that project.
Offline-first explanation is not a guarantee of indefinite operation or immunity from failure.
Power, hardware, local network, payment, and third-party services each have separate boundaries.
Availability, recovery, support, and service-level commitments can only be stated after environment testing and a separate agreement.
Permitted use and the legal owner of brand assets still require approval.
Ordinary viewing and linking to public pages should not be interpreted as endorsement, representation, or permission to use a mark.
Rules for republishing text, imagery, screenshots, marks, and brand assets must be defined by the legal owner before binding terms are published.
Binding rules, governing law, and dispute route are not yet assigned.
The website should not be used to attempt unauthorised access, cause disruption, extract personal data, or misrepresent a relationship with Mizi.
Governing law, liability limits, warranty disclaimers, termination, and dispute resolution require legal approval and are not manufactured in this framework.
Open decisions
Legal language must match the actual commercial model and environment.
Entity name, address, signing authority, and service territory.
Leadership and legal
Asset ownership, permitted use, republication, and infringement handling.
Brand and legal
Warranty scope, liability limits, and relationship to the pilot agreement.
Product, engineering, and legal
Governing law, venue, notice procedure, and dispute resolution.
Legal
Document governance
A change in availability, price, account access, data reception, service level, or territory triggers review. An effective date appears only after legal approval and publication of equivalent Persian and English versions.