Engagement & contract terms

1. Acceptance & document priority

By ordering on the site, paying a deposit, or signing a contract/quote, you accept these terms. If a written project contract differs, that contract controls. Iranian law governs the engagement.

2. Scope and each party’s duties

We deliver custom-coded work (not generic shared SaaS templates). Exact scope is set by the package page and the written contract.

• Our duties: build to the approved brief, report at agreed milestones, hand over access after settlement, bugfix support during the package support window
• Your duties: provide content, branding, and required domain/hosting/gateway access on time; approve stages within a reasonable time; pay per the milestone schedule
• You warrant you have rights to materials you supply
• Initial consult/estimate follows site policy; production starts after scope approval and deposit

3. Timeline and delays

Indicative delivery windows appear on each package and are finalized in the contract. Delays caused by late content, access, or approvals extend the schedule and are not treated as our default alone. If we delay without a client-caused reason, we update the plan in writing; fixed daily penalties apply only if expressly written in the contract.

4. Staged payments

Catalog prices are transparent; the contract locks the fee for the approved scope.

• Web design (typical): ~50% to start, ~50% before final handover / production cutover
• Apps: deposit + mid-milestone payment(s) + settlement before release/source handover
• SEO: usually monthly subscription; plan changes apply from the next cycle
• Iran: Zarinpal or another method named in the contract; international: crypto per published international pricing
• Overdue milestone payments may pause work until settled

5. Ownership of code and content

After full settlement of the contract fee:

• You own the delivered custom code and project content
• Domain, hosting, and business data accounts remain yours
• We may showcase non-confidential work in our portfolio unless the contract forbids it
• Open-source libraries, third-party licenses (fonts, stock, SDKs), and our internal process templates remain under their own terms — not absolute IP transfer
• Until final settlement, production access and source may remain with us to complete the work

6. Delivery and access

Final handover follows settlement and an agreed checklist:

• Repository access and/or packaged source plus deploy notes (as applicable)
• Admin credentials, environment checklist; for apps, build notes and in-scope store submission help
• Staging during build; production cutover via shared checklist
• SEO: Analytics/Search Console stay under your ownership; on exit we remove our access and provide paid-period report archive

7. Out-of-scope changes

Anything outside the approved brief/package (new features, major redesign, extra integrations, extra content, ads campaigns, etc.) needs a written quote before work starts. Revision rounds follow the package tier; extra rounds are billable.

8. Cancellation and refunds

Either party may end the engagement in writing (email or ticket). Typical notice for active projects is at least 7 days (monthly SEO: usually 30 days before the next cycle unless the contract says otherwise).

• Completed phases remain payable
• Deposits are settled against delivered/completed work; unused remainder is refundable after settlement unless the contract states otherwise
• Third-party fees already paid (licenses, stores, ads, domains) are generally non-refundable through us
• Gateway refunds follow Zarinpal/bank rules and cancellation documentation

9. Support and bug fixes

After handover, the free support window on the package applies (business-hours SLA per tier; see package page).

• Support covers defects from our work and guidance in package scope — not new features
• Production outages caused by our release are prioritized
• After free support: out-of-warranty fixes and new work via hourly quote or monthly retainer
• Bugs from client changes, third-party services, or unsuitable hosting are outside free support unless agreed otherwise

10. Third-party services and limits

Payment gateways, app stores, SMS, CDN, hosting, Enamad, and external APIs are outside our full control.

• Outages, fee changes, or policy limits of those providers are not our direct liability; we suggest alternatives where feasible
• We do not guarantee absolute Google rankings or sales numbers; SEO is based on agreed activity and reporting
• You must comply with third-party license and account terms

11. Confidentiality and liability cap

Business information is confidential except where disclosure is legally required. We are not liable for indirect or consequential damages; contractual liability is typically capped at fees paid for the relevant service, subject to mandatory law.

12. Disputes and contact

Disputes are first handled in good-faith negotiation; otherwise competent Iranian courts apply. Questions: