Terms of Service
The terms that govern every engagement between Akazuki Works Georgia LTD and our clients.
1. Definitions
In these Terms of Service, the following capitalized terms shall have the meanings set out below. These definitions apply equally in singular and plural form unless the context requires otherwise.
"Akazuki Works Georgia LTD", "Agency", "we", "us", or "our" means Akazuki Works Georgia LTD, a company duly incorporated under the laws of Georgia, providing enterprise-grade digital, software development, and related professional services.
"Client", "you", or "your" means any individual, company, organization, or other legal entity that enters into an agreement with the Agency for the provision of Services.
"Services" means all professional services provided by the Agency, including but not limited to software engineering, web development, system architecture, UI/UX design, technical consulting, infrastructure setup, maintenance, support, and any other services expressly agreed in writing between the parties.
"Deliverables" means all work product, outputs, materials, documentation, software, source code, configurations, designs, reports, or other items created, developed, or delivered by the Agency in the course of performing the Services under a Project.
"Project" means a defined engagement between the Agency and the Client, including agreed scope of work, specifications, timelines, milestones, acceptance criteria, pricing, and Deliverables, whether set out in a statement of work, proposal, order form, or similar document.
"Third-Party Services" means any services, software, platforms, APIs, cloud infrastructure, libraries, tools, or components provided or operated by entities other than the Agency that are used directly or indirectly in connection with the Services or Deliverables, whether or not integrated into the final output.
"Statement of Work" or "SOW" means a written document, mutually executed by both parties, that defines the specific scope, objectives, technical requirements, timelines, milestones, pricing, payment schedule, and Deliverables for a given Project, and which forms a binding part of these Terms upon execution.
"Change Request" means a formal written request submitted by either party to modify the scope, specifications, timeline, pricing, or any other agreed terms of an active Project after the relevant SOW has been executed. No Change Request shall be binding until reviewed, costed, and accepted in writing by both parties.
"Intellectual Property Rights" or "IPR" means all present and future intellectual property rights of any kind anywhere in the world, including but not limited to copyrights, patents, trademarks, trade secrets, database rights, moral rights, design rights, and any applications or registrations thereof, whether registered or unregistered.
"Background IP" means any Intellectual Property Rights owned or licensed by a party prior to the commencement of a Project, or developed independently outside the scope of any Project, including pre-existing frameworks, libraries, tools, methodologies, know-how, or proprietary components that a party brings to or incorporates into the Services or Deliverables.
"Foreground IP" means any Intellectual Property Rights created, developed, or arising directly as a result of the performance of Services under a Project, excluding Background IP.
"Confidential Information" means any non-public information, technical data, trade secrets, business strategies, financial data, source code, system architecture, credentials, client data, or other proprietary information disclosed by one party to the other in connection with the Services, whether disclosed in writing, orally, electronically, or by any other means, and whether or not marked as confidential, provided that a reasonable person would understand such information to be confidential given its nature and the circumstances of disclosure.
"Personal Data" means any information relating to an identified or identifiable natural person as defined under applicable data protection laws, including but not limited to the General Data Protection Regulation (EU) 2016/679 ("GDPR") and any equivalent national legislation, which is processed by either party in connection with the Services.
"Acceptance" means the formal written confirmation by the Client that a Deliverable or milestone satisfies the agreed acceptance criteria as set out in the applicable SOW. Acceptance shall not be unreasonably withheld or delayed, and where no written objection is raised within the acceptance period defined in the SOW, Deliverables shall be deemed accepted.
"Acceptance Period" means the number of calendar days following delivery of a Deliverable within which the Client must either formally accept or raise documented objections in accordance with the agreed acceptance criteria. Unless otherwise specified in the SOW, the default Acceptance Period shall be seven (7) calendar days.
"Defect" means a reproducible failure of a Deliverable to materially conform to the agreed specifications or acceptance criteria documented in the applicable SOW, excluding any failure caused by misuse, unauthorized modification, incompatible Third-Party Services, or Client-side infrastructure issues.
"Maintenance and Support Services" means post-delivery services provided by the Agency, if separately agreed in writing, including bug fixes, security patching, performance monitoring, minor updates, and technical assistance relating to Deliverables, as further defined in the applicable SOW or support agreement.
"Force Majeure Event" means any circumstance beyond a party's reasonable control that prevents or delays the performance of its obligations, including but not limited to acts of God, natural disasters, war, civil unrest, governmental actions, pandemics, cyberattacks by third parties, critical failures of internet infrastructure, or failure of Third-Party Services not attributable to the affected party's negligence.
"Fees" means the amounts payable by the Client to the Agency for the Services and Deliverables as specified in the applicable SOW, proposal, or invoice, including any applicable taxes, disbursements, or agreed expenses unless otherwise stated.
"Retainer" means a recurring fixed payment arrangement under which the Agency reserves a defined allocation of time, capacity, or resources for the Client over a specified period, as detailed in a separate written agreement or SOW.
"Environment" means a distinct deployment context used in the development lifecycle, including but not limited to development, staging, user acceptance testing (UAT), and production environments, each serving a defined purpose in the testing, validation, and release of Deliverables.
"Credentials" means any usernames, passwords, API keys, tokens, certificates, access codes, or other authentication or authorization data required to access systems, platforms, repositories, or services in connection with a Project.
"Effective Date" means the date on which these Terms of Service, or a specific SOW referencing them, become legally binding between the parties, as indicated in the relevant agreement or, in its absence, the date of the Client's first written acceptance of a proposal or commencement of Services.
2. Scope of Services
2.1 Services Overview
The Agency provides professional software development services and operates software-as-a-service ("SaaS") products offered directly to Clients under separate subscription or license terms.
Services may include:
- Custom web and software development
- Front-end and back-end engineering
- UI/UX design and product implementation
- System architecture and technical consulting
- API development and third-party integrations
- Infrastructure setup, deployment, and maintenance
- Ongoing technical support and maintenance services
The exact scope of Services for each engagement shall be defined in a written agreement, including proposals, statements of work, order forms, or similar documents. No verbal representations, preliminary discussions, or informal communications shall constitute a binding commitment to deliver any specific service or outcome unless confirmed in a duly executed written agreement.
2.2 SaaS Products
The Agency may offer proprietary SaaS products ("SaaS Products") made available on a subscription or license basis.
- SaaS Products are standardized software services provided "as is" or as updated from time to time.
- Access to SaaS Products is granted under a subscription plan, license agreement, or other applicable terms.
- The Agency retains all rights, title, and interest in and to the SaaS Products, including software, infrastructure, design, and intellectual property.
- Features, functionality, and availability of SaaS Products may be modified, updated, or discontinued at the Agency's discretion, subject to applicable contractual obligations.
- Service availability, support levels, and uptime commitments (if any) shall be governed by separate service level terms or product-specific documentation.
- The Client acknowledges that SaaS Products may rely on Third-Party Services, and that the Agency's ability to maintain certain features or integrations may be subject to the continued availability and terms of such Third-Party Services.
- The Client shall not attempt to reverse engineer, decompile, disassemble, sublicense, resell, or otherwise exploit the SaaS Products or any component thereof beyond the access rights expressly granted under the applicable subscription or license terms.
2.3 Exclusions
Unless expressly agreed in writing, the Agency does not provide:
- Marketing, advertising, or growth services
- Search engine optimization (SEO)
- Content writing, copywriting, or editorial services
- Legal, financial, or business advisory services
- Third-party software licenses, hosting fees, or subscription costs not explicitly included in the agreement
- Procurement, negotiation, or management of third-party vendor relationships on behalf of the Client
- Data migration services beyond those expressly defined in the applicable SOW
- Regulatory compliance assessments, audits, or certifications (including but not limited to GDPR compliance reviews, accessibility audits, PCI-DSS assessments, or penetration testing) unless separately agreed in writing
- Training, onboarding, or documentation beyond what is expressly included in the agreed scope
- Any services not expressly included in the agreed scope or SaaS subscription terms
Where the Client requires any excluded service, the parties may negotiate a separate written agreement or addendum to address such requirements. The Agency's agreement to perform any previously excluded service in one engagement shall not create any obligation or precedent to provide such service in future engagements.
2.4 Change Requests (Project Services Only)
For custom development or consulting engagements (not SaaS Products), any request that modifies or expands the agreed scope shall be treated as a Change Request:
- All Change Requests must be submitted in writing, with sufficient detail to allow the Agency to assess the nature, complexity, and impact of the requested change.
- The Agency will evaluate the impact on cost, resources, timeline, and technical architecture and shall provide a written assessment within a reasonable timeframe.
- Changes are not binding unless confirmed in writing by both parties. The Agency shall not be obligated to commence work on any Change Request prior to such written confirmation.
- Approved changes may result in revised pricing, milestones, delivery schedules, or modifications to previously agreed acceptance criteria.
- Where a Client-initiated Change Request materially expands the scope of a Project, the Agency reserves the right to require a revised or supplementary SOW before proceeding.
- Emergency or expedited change requests, where agreed by both parties, may be subject to additional fees reflecting the priority resourcing required.
2.5 Client Responsibilities
The Client acknowledges that the timely and satisfactory delivery of Services is contingent upon the Client fulfilling certain responsibilities throughout the engagement. The Client shall:
- Provide the Agency with timely access to all information, materials, systems, Credentials, and personnel reasonably required for the performance of the Services, including but not limited to design assets, brand guidelines, existing codebases, third-party API documentation, and infrastructure access.
- Designate a primary point of contact with sufficient authority to make decisions on behalf of the Client in a timely manner, and notify the Agency promptly of any change in that designation.
- Review and respond to Agency deliverables, questions, proposals, and requests for approval within the timeframes agreed in the applicable SOW or, where no timeframe is specified, within a reasonable time not to exceed five (5) business days.
- Ensure that all information and materials provided to the Agency are accurate, complete, and do not infringe upon the intellectual property rights or other rights of any third party.
- Promptly notify the Agency in writing of any changes to the Client's requirements, technical environment, or business context that may affect the scope, delivery, or performance of the Services.
- Be responsible for the configuration, administration, and security of any systems, platforms, or environments under the Client's control, including user account management and access permissions.
- Obtain and maintain all necessary licenses, consents, and authorizations required for the Agency to lawfully access and use any Client-provided data, systems, software, or third-party services in connection with the performance of the Services.
The Agency shall not be liable for any delays, defects, cost overruns, or failure to meet agreed milestones arising directly or indirectly from the Client's failure to fulfill the responsibilities set out in this clause. Where such failure causes the Agency to incur additional costs or resource allocation, the Agency reserves the right to charge for such additional effort as a Change Request.
2.6 Subcontracting
The Agency reserves the right to engage qualified subcontractors, freelancers, or specialist third parties to assist in the performance of Services, provided that:
- The Agency remains fully responsible to the Client for the quality and delivery of all Services and Deliverables, regardless of whether any portion is performed by a subcontractor.
- Subcontractors are bound by confidentiality and data protection obligations no less protective than those applicable to the Agency under these Terms.
- The Agency shall not disclose Client Confidential Information to any subcontractor beyond what is strictly necessary for the performance of the relevant Services.
- The Client's prior written consent shall be required before engaging any subcontractor who will have access to the Client's production systems, Personal Data, or Confidential Information of a particularly sensitive nature, as reasonably determined by the Client.
2.7 Service Delivery Standards
The Agency shall perform all Services with reasonable care, skill, and diligence in accordance with generally accepted professional standards in the software development industry. The Agency shall:
- Assign appropriately qualified personnel to each Project and endeavor to maintain continuity of key personnel throughout an engagement, subject to operational requirements.
- Notify the Client promptly of any material risk to delivery timelines, technical feasibility, or agreed milestones as soon as such risk becomes apparent.
- Maintain appropriate version control, documentation practices, and code quality standards in line with industry norms, as further specified in the applicable SOW where relevant.
- Comply with all applicable laws and regulations in the performance of the Services, including those relating to data protection, employment, and professional conduct.
The Agency does not warrant that Services or Deliverables will be entirely free from errors or defects, but shall use commercially reasonable efforts to identify and remediate Defects reported by the Client in accordance with the applicable support or maintenance terms.
2.8 Acceptance of Deliverables
Upon delivery of any Deliverable or completion of a milestone, the following acceptance process shall apply:
- The Client shall review the Deliverable against the agreed acceptance criteria within the Acceptance Period defined in the applicable SOW.
- Where the Client identifies a material Defect, the Client shall provide the Agency with a written notice specifying the nature of the Defect with sufficient detail to allow the Agency to reproduce and assess it.
- The Agency shall use commercially reasonable efforts to remediate confirmed Defects within an agreed timeframe, following which the Deliverable shall be resubmitted for review.
- If the Client does not provide written acceptance or a documented Defect notice within the Acceptance Period, the Deliverable shall be deemed accepted as of the final day of that period.
- Acceptance shall not be withheld on grounds not included in the originally agreed acceptance criteria, nor on the basis of new requirements introduced after the relevant SOW was executed.
- Partial acceptance of a Deliverable is permitted where the non-conforming elements are clearly isolated and the Agency agrees in writing to remediate them within a defined period.
3. Project Engagement Model
3.1 Engagement Structures
The Agency may engage with Clients under one or more of the following models, as agreed in writing:
- Fixed-Price Model: A predefined total price for a clearly defined scope of work and Deliverables. This model is suitable where requirements are well-defined and unlikely to change materially during the course of the Project. Any modification to the agreed scope shall be subject to the Change Request process set out in Section 2.4. The Agency shall not be obligated to perform work beyond the agreed scope under a fixed-price arrangement without a duly executed Change Request.
- Hourly Model: Services billed based on actual time spent at agreed hourly rates. Time is recorded in good faith and in reasonable increments, and the Agency shall provide itemized time records upon request. The Client acknowledges that the total cost under this model is not capped unless a separate written budget ceiling is agreed. The Agency shall notify the Client if cumulative hours are projected to materially exceed any agreed budget estimate.
- Retainer Model: Ongoing Services provided on a recurring basis (e.g., monthly), typically subject to a defined capacity or allocated hours. Unless otherwise agreed in writing, unused retainer hours or capacity within a given billing period shall not roll over to subsequent periods and will be forfeited without refund or credit. The Agency shall endeavor to provide reasonable advance notice of any proposed changes to retainer terms, including pricing or capacity adjustments.
- Milestone-Based Model: Payment and delivery structured around predefined project milestones and associated Deliverables. Each milestone shall have clearly defined deliverables and acceptance criteria as set out in the applicable SOW. Payment obligations tied to a milestone shall become due upon the Client's formal acceptance of that milestone or upon deemed acceptance in accordance with Section 2.8, whichever occurs first.
- Hybrid Model: Where operationally appropriate, the Agency and Client may agree on a combination of the above engagement structures within a single Project or across different workstreams. In such cases, the applicable model for each workstream or phase shall be clearly specified in the relevant SOW, and the terms applicable to each model shall apply independently to the corresponding portion of the engagement.
3.2 Estimates and Pricing
- Any estimates provided by the Agency — including time, cost, resource, or complexity estimates — are based on the information, requirements, and assumptions available at the time of preparation and represent the Agency's good-faith professional assessment.
- Estimates are non-binding unless expressly stated as fixed or guaranteed in a duly executed written agreement.
- The Agency reserves the right to revise estimates where there are changes to scope, requirements, assumptions, technical constraints, or third-party dependencies. Where a revision is material, the Agency shall provide a written explanation of the factors necessitating the change.
- Revised estimates will be communicated to the Client as soon as reasonably practicable and, where applicable, shall be formalized as a Change Request prior to additional work commencing.
- Where the Client has been provided with a cost range rather than a fixed figure, the Agency's obligation is to perform the Services within that range under the stated assumptions. Material deviations beyond the upper bound of a stated range shall require prior written notification and Client approval.
- All pricing quoted by the Agency is exclusive of applicable taxes, levies, duties, or government-imposed charges (including but not limited to VAT or equivalent) unless explicitly stated otherwise. Any such taxes shall be added to invoices and are the Client's responsibility to pay.
- Pricing set out in an SOW or proposal shall remain valid for the period specified therein, or where no period is specified, for thirty (30) calendar days from the date of issue. The Agency reserves the right to revise pricing for engagements commencing after the validity period has lapsed.
3.3 Project Phases and Approvals
Projects may be structured into phases — including but not limited to discovery, design, development, testing, quality assurance, and deployment — depending on complexity, engagement type, and the needs of the Client.
- Each phase may require Client review and formal written approval before the Agency proceeds to the next stage. The applicable approval requirements for each phase shall be defined in the SOW.
- Approval may be required for project specifications, wireframes, design mockups, architectural decisions, prototypes, milestone outputs, or final Deliverables, as applicable.
- The Agency is not obligated to proceed to subsequent phases until prior phase outputs have been approved by the Client or deemed accepted in accordance with Section 2.8. Any instruction to proceed to a subsequent phase without formal approval of the prior phase shall be provided in writing by the Client and shall constitute the Client's acknowledgment that the preceding phase output is accepted.
- Delays in Client feedback, review, or approval beyond the timeframes specified in the SOW — or, where no timeframe is specified, beyond five (5) business days — may impact agreed delivery schedules and timelines. The Agency shall not be held responsible for downstream delays arising from Client-side approval bottlenecks, and any resulting schedule adjustments shall be communicated in writing.
- Where a Client requests that a phase be bypassed, abbreviated, or compressed, the Client acknowledges and accepts the associated risks, including but not limited to increased likelihood of Defects, rework, or scope misalignment. The Agency shall document any such instructions and may record a formal objection where it considers the risk materially significant.
- Where a phase involves the production of design assets, technical specifications, or architectural documentation, those outputs shall be deemed Deliverables subject to the acceptance process defined in Section 2.8, unless otherwise agreed in the applicable SOW.
3.4 Discovery and Requirements Definition
Where a Project includes a discovery phase or requirements definition engagement, the following terms shall apply:
- The purpose of the discovery phase is to define, validate, and document the Client's requirements, technical constraints, and project assumptions in sufficient detail to support accurate scoping, estimation, and planning.
- Outputs of the discovery phase may include, but are not limited to, technical specifications, system architecture documentation, user story libraries, data flow diagrams, wireframes, or project roadmaps, as agreed in the applicable SOW.
- Discovery phase outputs shall constitute the basis for any subsequent fixed-price or milestone-based engagement. The Agency's post-discovery estimates and proposals are contingent on the accuracy and completeness of information provided by the Client during the discovery phase.
- Where material discrepancies are identified between Client-provided information during discovery and the actual state of the Client's systems, data, or requirements at the commencement of delivery, the Agency reserves the right to revise its estimates and, where necessary, issue a Change Request to address the additional scope or complexity.
- Fees for the discovery phase are payable regardless of whether the Client proceeds to a subsequent delivery engagement, unless otherwise agreed in writing.
3.5 Timelines and Delivery Schedules
- Project timelines and delivery schedules agreed in the applicable SOW are estimates made in good faith based on the information and resource availability known at the time of planning.
- The Agency shall use commercially reasonable efforts to meet agreed timelines and shall notify the Client promptly in writing of any risk to scheduled delivery dates as soon as that risk becomes apparent.
- Delivery timelines are contingent upon the Client fulfilling its responsibilities as set out in Section 2.5, including timely provision of materials, access, decisions, and approvals. The Agency shall not be liable for delays attributable to the Client's failure to meet those responsibilities, and any such delay shall entitle the Agency to a reasonable extension of the affected delivery dates.
- Timelines may also be affected by Force Majeure Events, third-party dependencies outside the Agency's reasonable control, or undisclosed technical complexity in the Client's existing systems. The Agency shall notify the Client as soon as practicable upon identifying any such factor and shall propose a revised schedule in writing.
- Where the Client requires an accelerated delivery schedule that deviates from the timeline agreed in the SOW, such acceleration shall be subject to the Agency's capacity and may attract additional fees, to be agreed in writing as a Change Request.
- Time is not of the essence in relation to delivery dates under these Terms unless expressly stated as such in the applicable SOW.
3.6 Resource Allocation and Personnel
- The Agency shall allocate appropriately skilled personnel to each Project based on the agreed scope and engagement structure.
- The Agency reserves the right to reassign internal personnel across Projects in accordance with its operational requirements, provided that such reassignment does not materially impact the quality or continuity of the Services being delivered to the Client.
- Where a Client requests the assignment of specific named individuals to a Project, such requests shall be documented in the applicable SOW. The Agency shall use reasonable efforts to honor such requests but does not guarantee the continuous availability of any specific individual throughout the engagement.
- In the event of unplanned personnel changes — including resignation, illness, or operational reassignment — the Agency shall use commercially reasonable efforts to minimize disruption to the Project and shall provide a suitably qualified replacement within a reasonable timeframe.
- The Client shall not directly solicit, recruit, or engage any current employee, contractor, or subcontractor of the Agency who has been involved in the performance of Services, for a period of twelve (12) months following the conclusion of the relevant engagement, without the Agency's prior written consent. Any breach of this clause may entitle the Agency to seek compensation equivalent to a placement fee of no less than twenty-five percent (25%) of the relevant individual's annual compensation.
3.7 Project Suspension
Either party may request a temporary suspension of an active Project under the following conditions:
- Client-Initiated Suspension: The Client may request a suspension of Services by providing written notice to the Agency. The Agency shall use commercially reasonable efforts to pause active work within a reasonable timeframe following receipt of such notice. Any costs reasonably incurred by the Agency up to the point of suspension — including work completed, resources committed, and third-party obligations entered into — shall remain payable by the Client. Where a suspension exceeds thirty (30) calendar days, the Agency reserves the right to reallocate dedicated resources to other engagements, and resumption of the Project may be subject to revised scheduling and, where applicable, revised pricing.
- Agency-Initiated Suspension: The Agency may suspend Services in the event of the Client's material breach of these Terms, including non-payment of overdue invoices, failure to provide required access or approvals, or conduct that materially impedes the Agency's ability to perform. The Agency shall provide written notice prior to suspension where reasonably practicable, and shall specify the grounds for suspension and the steps required to remedy the situation.
- Resumption of Services: Upon resolution of the circumstances giving rise to a suspension, the parties shall agree in writing on a revised project schedule, resource plan, and where applicable, any adjusted fees or milestones before work resumes.
3.8 Project Termination
Either party may terminate an engagement in accordance with the termination provisions set out in Section 9 of these Terms. Upon termination:
- The Client shall pay for all Services rendered and costs incurred up to the effective date of termination, including any non-cancellable third-party commitments entered into by the Agency in connection with the Project.
- Under a fixed-price or milestone-based model, fees for completed milestones shall be payable in full, and fees for partially completed milestones shall be assessed on a pro-rata or time-and-materials basis, as reasonably determined by the Agency based on work completed.
- The Agency shall deliver to the Client all Deliverables completed as of the termination date, in their then-current state, subject to receipt of all outstanding payments.
- Where termination is initiated by the Client without cause prior to Project completion, a termination fee may apply as specified in the applicable SOW. Where no such fee is specified, the Client shall pay for all work completed and all costs reasonably committed by the Agency as of the termination date.
- Termination shall not affect any rights or obligations that have accrued prior to the effective date of termination, nor shall it affect any provisions of these Terms that are expressed or intended to survive termination.
3.9 Clarifications and Pre-Execution Queries
If any part of the scope, estimates, engagement model, or approval process is unclear or requires further definition prior to execution:
- The Agency shall raise clarifications in writing before commencing work on the affected portion of the Project.
- The Client shall respond to clarification requests within the timeframes specified in the applicable SOW or, where no timeframe is specified, within five (5) business days.
- Where a clarification reveals a material ambiguity in the agreed scope or assumptions, the parties shall resolve the ambiguity in writing before proceeding. Any resolution that expands or modifies the scope shall be treated as a Change Request in accordance with Section 2.4.
- The Agency shall not be held liable for errors, delays, or Defects arising from proceeding on the basis of Client-provided information that is later found to be incomplete, inaccurate, or materially different from the actual requirements.
4. Payment Terms
4.1 Billing Structure
Payments shall be made in accordance with the billing model agreed between the Agency and the Client, unless otherwise agreed in writing. Available billing structures include:
- Upfront Payment: Full or partial payment required before commencement of Services or Project initiation. Where an upfront deposit is required, the Agency shall not be obligated to allocate resources, begin work, or make any third-party commitments on behalf of the Client until such deposit has been received and cleared. The deposit amount and its application against the total project fee shall be specified in the applicable SOW or proposal.
- Milestone-Based Billing: Payments issued upon completion and/or approval of predefined project milestones. Each milestone payment shall become due upon the Client's formal acceptance of the associated Deliverable or upon deemed acceptance in accordance with Section 2.8, whichever occurs first. The Agency shall not be obligated to commence work on a subsequent milestone until the invoice associated with the preceding milestone has been paid in full, unless otherwise agreed in writing.
- Monthly Retainer: Recurring payments for ongoing Services, billed in advance for each billing cycle. Retainer fees are payable regardless of whether the Client utilizes the full allocated capacity within the relevant billing period, and unused capacity shall not accrue or carry forward unless expressly agreed in writing. The Agency reserves the right to adjust retainer fees upon no less than thirty (30) days' written notice prior to the commencement of the affected billing cycle.
- Hourly Billing: Payments based on actual hours worked, invoiced periodically as agreed between the parties. Time records shall be maintained by the Agency in reasonable detail and made available to the Client upon written request. Where the Client has agreed to a maximum budget or hour cap under an hourly engagement, the Agency shall notify the Client in writing when cumulative hours reach eighty percent (80%) of the agreed cap, and shall not exceed the cap without the Client's prior written authorization.
- Hybrid Billing: Where multiple billing structures apply within a single engagement or across workstreams, each structure shall apply independently to its respective scope as defined in the applicable SOW, and the payment obligations arising from each shall be treated separately.
The applicable billing structure for each engagement shall be defined in the relevant agreement, proposal, or order form. In the absence of an expressly agreed billing structure, the Agency's default billing terms shall apply as notified to the Client in writing.
4.2 Invoicing and Payment Due Dates
- Invoices will be issued electronically to the billing contact or email address designated by the Client, unless otherwise agreed in writing. The Client is responsible for ensuring that accurate and up-to-date billing contact information is provided to the Agency at all times.
- Payment terms shall be specified on the invoice or in the applicable agreement. Where no payment term is expressly stated, invoices shall be due and payable within fourteen (14) calendar days of the invoice date.
- All payments must be made in full by the due date stated on the invoice, without deduction, withholding, or set-off of any kind, unless otherwise agreed in writing or expressly required by applicable law.
- The Agency reserves the right to issue interim invoices for work in progress on engagements of extended duration, at intervals agreed in the applicable SOW or, where no interval is specified, on a monthly basis.
- Invoices shall be deemed received on the date of electronic transmission, provided no delivery failure notification is received by the Agency. The Client shall promptly notify the Agency if an invoice is not received within a reasonable time following the expected issue date.
- The Agency shall issue a final invoice upon Project completion, retainer termination, or the end of an engagement, reflecting all outstanding amounts owed by the Client as of that date.
- Where a Client requires specific purchase order numbers, vendor registration, or internal procurement procedures to be followed prior to invoice processing, the Client is responsible for communicating these requirements to the Agency in advance. Any resulting delays in invoice processing caused by the Client's internal procedures shall not affect the payment due date as calculated from the invoice date, unless otherwise agreed in writing.
4.3 Payment Methods
- Accepted payment methods shall be communicated to the Client at the time of invoicing or set out in the applicable agreement, and may include bank transfer, credit or debit card, or other methods as offered by the Agency from time to time.
- All bank transfer or wire transfer fees, intermediary bank charges, and currency conversion costs shall be borne by the Client. The Agency must receive the full invoiced amount net of any such charges.
- The Agency does not accept payment in cryptocurrency, barter, or non-monetary consideration unless expressly agreed in writing.
- Where the Client makes payment via a third-party payment processor, the transaction shall be subject to the terms and conditions of that processor, and the Agency shall not be liable for any failure, error, or delay attributable to the processor.
- Payments shall be applied to the oldest outstanding invoice first, unless the Client provides written instructions specifying otherwise and the Agency agrees to such allocation in writing.
4.4 Currency and Taxes
- All fees are denominated in the currency specified in the applicable agreement or invoice. Where no currency is specified, the default currency shall be United States Dollars (USD).
- Where a Client makes payment in a currency other than the invoiced currency, any exchange rate loss, conversion fee, or shortfall arising from the conversion shall be borne by the Client, and the Agency reserves the right to issue a supplementary invoice for any resulting shortfall.
- Unless otherwise stated, all fees quoted by the Agency are exclusive of applicable taxes, levies, duties, or government-imposed charges, including but not limited to value-added tax (VAT), goods and services tax (GST), withholding tax, or equivalent charges arising in any jurisdiction.
- The Client is solely responsible for all applicable taxes, duties, or government charges arising in connection with the Services, with the exception of taxes assessed on the Agency's net income in the Agency's jurisdiction of incorporation.
- Where the Agency is required by applicable law to collect or remit any tax on behalf of the Client, such tax shall be added to the relevant invoice and paid by the Client in addition to the stated fees.
- Where a Client is located in a jurisdiction that imposes withholding tax on payments to foreign service providers, the Client shall be responsible for grossing up payments such that the Agency receives the full invoiced amount after any required withholding deduction. The Client shall provide the Agency with appropriate withholding tax certificates or official receipts upon request.
- The Agency reserves the right to revise its pricing in response to changes in applicable tax legislation or regulatory requirements, and shall provide reasonable written notice of any such revision.
4.5 Late Payments
- Invoices not paid in full by the due date shall be considered overdue. The Agency reserves the right to charge interest on overdue amounts at a rate of one and a half percent (1.5%) per month, or the maximum rate permitted under applicable law, whichever is lower, calculated from the due date until the date of full payment.
- Interest shall accrue daily on the outstanding balance and shall be invoiced separately. The Client's obligation to pay accrued interest shall survive termination or expiration of the engagement.
- The Agency reserves the right to suspend or pause all Services, including access to Deliverables, work-in-progress environments, repositories, or SaaS Products, with immediate effect upon a payment becoming overdue, and without incurring any liability to the Client for such suspension.
- Where a discounted rate was applied to any Services subject to timely payment, and that payment is delayed by more than seven (7) calendar days beyond the due date or is defaulted upon, the Agency reserves the right to revoke the applicable discount retroactively and issue a revised invoice at the full standard rate for all affected Services.
- All reasonable costs incurred by the Agency in recovering overdue amounts — including but not limited to legal fees, collection agency fees, court costs, and administrative expenses — shall be recoverable from the Client to the fullest extent permitted by applicable law.
- The Agency's decision to accept late payment on any occasion shall not constitute a waiver of its right to enforce strict payment terms on any subsequent invoice or in relation to any other amounts outstanding.
- Where the Client is experiencing genuine financial difficulty and communicates this to the Agency in advance of a payment due date, the parties may discuss in good faith a temporary payment arrangement or revised schedule. Any such arrangement shall be recorded in writing and signed by both parties before it becomes effective, and shall not affect the Agency's right to charge interest on amounts that remain outstanding beyond the originally agreed due date, unless expressly waived in writing.
4.6 Disputed Invoices
- Any questions, objections, or disputes regarding an invoice, charge, or billing record must be raised by the Client in writing within seven (7) calendar days of the invoice date, specifying in reasonable detail the nature of the dispute and the amounts contested.
- Disputes raised after this period shall be considered waived, and the invoiced amount shall be treated as accepted and due in full.
- Where a Client raises a valid dispute within the required timeframe, the parties shall engage in good faith discussions to resolve the matter within ten (10) business days of the dispute being raised.
- Disputed amounts shall not entitle the Client to withhold payment of any undisputed portion of the same invoice or any other outstanding invoices. Undisputed amounts remain due and payable on their original due dates regardless of any pending dispute.
- If a dispute is resolved in the Client's favor, the Agency shall issue a credit note or revised invoice within a reasonable timeframe. If resolved in the Agency's favor, the Client shall pay the previously disputed amount, together with any applicable interest accrued from the original due date, within five (5) business days of resolution.
4.7 Refund Policy
- Payments made to the Agency are non-refundable once Services have commenced, resources have been allocated, or Deliverables have been produced in whole or in part, unless otherwise agreed in writing or required by mandatory applicable law.
- Upfront deposits are non-refundable in all circumstances once the Agency has commenced preparatory work, including but not limited to project planning, resource allocation, procurement of third-party tools or licenses, or onboarding activities.
- Where a Project is terminated by the Client before completion, no refund shall be due in respect of work already performed, costs already committed, or milestones already invoiced or deemed accepted. Any overpayment relative to work actually completed shall be assessed by the Agency in good faith and, where applicable, refunded or credited within thirty (30) calendar days of the termination date.
- Where the Agency fails to deliver a Deliverable that materially conforms to agreed specifications and such failure is attributable solely to the Agency, the parties shall in the first instance seek to resolve the matter through the Defect remediation process under Section 2.8. Refunds shall only be considered where remediation is not feasible and where the failure constitutes a material breach of the applicable agreement.
- Any refund granted shall be at the sole discretion of the Agency unless otherwise required by law or expressly agreed in writing, and shall be issued via the same payment method used by the Client unless both parties agree otherwise.
- Subscription fees for SaaS Products shall be governed by the refund terms set out in the applicable product-specific subscription or license agreement, which shall take precedence over this clause in the event of conflict.
4.8 Suspension and Termination for Non-Payment
- Failure to make payment in full by the applicable due date shall entitle the Agency to suspend all Services with immediate effect, without prior notice and without liability to the Client, unless otherwise agreed in writing.
- Upon suspension for non-payment, the Agency may: withhold delivery of completed or in-progress Deliverables; revoke access to repositories, staging environments, and work-in-progress assets; suspend access to any SaaS Products; and cease all active development, support, and maintenance activities.
- Suspension shall remain in effect until all outstanding balances — including principal amounts, accrued interest, and any recovery costs — are paid in full and funds have cleared.
- Where payment remains outstanding for more than thirty (30) calendar days beyond the due date, and no payment arrangement has been agreed in writing, the Agency may treat the non-payment as a material breach of the agreement and terminate the engagement in accordance with Section 9, without prejudice to any other rights or remedies available to the Agency.
- Upon termination for non-payment, the Agency shall have no obligation to deliver, transfer, or make available any Deliverables, source code, assets, or documentation until all amounts owed have been paid in full.
- The Agency's rights under this clause are in addition to, and shall not limit or replace, any other rights or remedies available to the Agency under these Terms, applicable law, or equity.
4.9 Financial Records and Audit Rights
- The Agency shall maintain accurate financial records in connection with hourly and time-and-materials engagements for a minimum period of three (3) years following the conclusion of the relevant Project or engagement.
- Where the Client reasonably suspects a material discrepancy in billed hours or expenses under a time-and-materials arrangement, the Client may, upon no less than ten (10) business days' written notice and no more than once per calendar year, request a review of the relevant time records. Such review shall be conducted at the Client's expense by an independent accountant or auditor mutually agreed by the parties.
- Where a review reveals an overcharge in excess of five percent (5%) of the total amount invoiced for the reviewed period, the Agency shall reimburse the overcharged amount and bear the reasonable cost of the audit. Where no such overcharge is identified, the full cost of the review shall be borne by the Client.
- This clause applies exclusively to hourly and time-and-materials engagements and does not apply to fixed-price, milestone-based, or retainer arrangements.
4.10 Clarifications and General Payment Provisions
- Any questions or uncertainties regarding invoices, charges, billing records, or payment terms must be raised promptly and in writing in accordance with Section 4.6.
- The Agency's failure to enforce any payment obligation on a given occasion shall not constitute a waiver of its right to strictly enforce payment terms at any future time or in relation to any other amounts due.
- Where any provision of this Section 4 conflicts with a specific term set out in a duly executed SOW or separate written agreement, the terms of that SOW or agreement shall prevail to the extent of the conflict.
- The Client's payment obligations under these Terms are independent of any third-party funding, investment, client revenue, or other external financial arrangements. The Agency shall not be required to delay invoicing or adjust payment terms based on the Client's internal cash flow position except where expressly agreed in writing.
5. Intellectual Property
5.1 Ownership of Code and Deliverables
All Intellectual Property Rights in and to the Deliverables — including all source code, object code, Foreground IP, Background IP, software architecture, designs, configurations, documentation, and work in progress — are and shall at all times remain the sole and exclusive property of the Agency. This applies before, during, and after every Project, regardless of whether a Deliverable was created specifically for the Client, and regardless of whether the Client has paid, or at any later time pays, any Fees or other consideration in respect of it.
- No payment of Fees, purchase of Deliverables, purchase or receipt of a copy of the source code, completion of a Project, Acceptance, termination, or any other act or omission shall operate as, or be construed as, an assignment, sale, or transfer of ownership of any Intellectual Property Rights to the Client, whether such payment or purchase occurs before, during, or after the relevant Project.
- Delivery or disclosure of source code to the Client, including by providing access to code repositories, hosting accounts, or Environments, grants possession of a copy only and does not transfer any Intellectual Property Rights.
- To the extent that any Intellectual Property Rights in the Deliverables vest in the Client or its personnel by operation of law, the Client hereby assigns, and shall procure the assignment of, all such rights to the Agency immediately upon their creation, and shall execute any documentation reasonably required by the Agency to confirm or register the Agency's ownership.
- Any modifications, adaptations, or derivative works of the Deliverables made by or on behalf of the Client shall, to the extent they incorporate or are based on the Agency's code, be owned by the Agency and shall be included in the license granted below.
- Notwithstanding Section 20.6, ownership of any Intellectual Property Rights in the Deliverables may only pass to the Client under a separate written deed of assignment that expressly refers to and overrides this Section 5.1 and is signed by an authorized director of the Agency. No SOW, proposal, invoice, purchase order, email, or conduct shall have that effect.
Client License
Subject to satisfaction of the conditions set out in Section 5.5, the Agency grants the Client a non-exclusive, worldwide, perpetual, royalty-free, non-transferable license to use and operate the Deliverables specifically created for the Client under the relevant Project, in the form deployed by the Agency, solely for the Client's own business purposes, including making the Client's own products or services built on the Deliverables available to its end users.
- The license covers use and operation only. It does not include any right to access, receive, copy, edit, modify, adapt, or create derivative works of the Deliverables or their source code, except as set out below.
- The Fees paid for a Project cover the Services and this license only. The source code is not included in the Fees and shall not be delivered or made available to the Client unless the Client pays a separate source code fee agreed in writing with the Agency (the "Source Code Fee"). Source code provided after payment of the Source Code Fee remains the exclusive property of the Agency under this Section 5.1.
- All edits, updates, and changes to the Deliverables shall be carried out by the Agency against a fee in accordance with Section 5.10. The Client shall not edit or modify the Deliverables itself, nor engage or permit any third party to do so, unless it has paid the Source Code Fee, in which case this license extends to modifying the Deliverables for the Client's own business purposes.
- Nothing in this Section 5.1 prevents the Client from updating its own content, such as text, images, product or property listings, and other data, through any content management system or admin interface provided by the Agency as part of the Deliverables, within the functionality that interface offers.
- The Client shall not sell, resell, sublicense, distribute, rent, or otherwise make the Deliverables or their source code available to any third party as a standalone product or for that party's own use, nor use them to build a product or service for any third party, without the Agency's prior written consent.
- Where the Client has paid the Source Code Fee, it may permit its employees and contractors to access and work on the source code solely on the Client's behalf, provided they are bound by confidentiality obligations no less protective than Section 10, and the Client remains responsible for their compliance with this license.
- The license is limited to the Agency's own contributions to the Deliverables. Client-provided materials remain governed by Section 5.3, and Third-Party Components remain governed by Section 5.4.
- The Agency may terminate this license by written notice if the Client materially breaches its restrictions and fails to remedy the breach within thirty (30) calendar days of written notice, or where the conditions in Section 5.5 cease to be satisfied.
5.2 Agency Retained Rights
Without limiting Section 5.1, and for the avoidance of doubt, the Agency's ownership expressly includes the following categories of intellectual property, which shall under no circumstances be assigned or exclusively licensed to the Client:
- Pre-existing materials, frameworks, methodologies, tools, know-how, and proprietary processes developed by or belonging to the Agency prior to or independently of any Client engagement.
- Reusable code components, libraries, modules, boilerplates, templates, and utilities developed or owned by the Agency, including those that may be incorporated into or underpin the Deliverables.
- Generic or non-client-specific software architecture patterns, design systems, development workflows, and technical approaches that represent the Agency's accumulated expertise and professional methodology.
- Internal development tools, automation scripts, deployment pipelines, testing frameworks, and infrastructure configurations used by the Agency in the course of performing Services.
- Any improvements, enhancements, or derivative works made to the Agency's Background IP in the course of performing Services, even where such improvements arise in connection with a specific Client Project.
- Conceptual approaches, technical solutions, and implementation patterns identified or developed during the course of a Project that are of general applicability and not specific to the Client's business, data, or unique requirements.
Where Agency Retained Rights are incorporated into or are necessary for the use of the Deliverables, the Agency hereby grants the Client a non-exclusive, worldwide, perpetual, royalty-free, non-transferable license to use such components solely as embedded in or as necessary to operate the Deliverables for the Client's internal business purposes, subject to full payment of all amounts due. This license does not permit the Client to extract, isolate, sublicense, redistribute, or commercialize the Agency's Retained Rights independently of the Deliverables in which they are embedded.
The Agency may freely reuse, repurpose, improve, or commercialize its Retained Rights in connection with other clients, projects, or products, without restriction and without any obligation to account to the Client, provided that no Client Confidential Information is disclosed or incorporated in violation of Section 6, and no client-specific data or identifying information is included in any reused component.
5.3 Client-Provided Materials
Where the Client provides the Agency with any materials, assets, data, content, branding, existing code, or other intellectual property for incorporation into the Deliverables or for use in connection with the Services:
- The Client represents and warrants that it owns or has obtained all necessary rights, licenses, and permissions to provide such materials to the Agency and to authorize their use in the manner required by the applicable Project.
- The Client grants the Agency a non-exclusive, royalty-free license to use, reproduce, modify, and incorporate such materials solely for the purpose of performing the Services during the term of the engagement.
- The Agency shall not use Client-provided materials for any purpose other than the performance of the Services, and shall not disclose such materials to any third party except as strictly necessary for the performance of the Services and in accordance with Section 6.
- The Agency makes no representation as to the legality, accuracy, completeness, or fitness for purpose of any Client-provided materials, and the Client assumes full responsibility for ensuring that such materials do not infringe upon the intellectual property rights or other rights of any third party.
- Where the Agency identifies a potential intellectual property conflict arising from Client-provided materials, it shall notify the Client promptly in writing. The Agency shall not be obligated to proceed with any work that it reasonably believes may expose it to third-party intellectual property claims, and shall not be liable for any claim, loss, or liability arising from the Agency's use of Client-provided materials in good faith in accordance with the Client's instructions.
5.4 Third-Party Components
Deliverables may include, rely upon, or be built using third-party components, including but not limited to:
- Open-source software governed by applicable open-source licenses, including but not limited to the MIT License, Apache License 2.0, GNU General Public License (GPL), GNU Lesser General Public License (LGPL), and similar permissive or copyleft licenses.
- Paid or licensed APIs, SDKs, platforms, and services provided by third-party vendors.
- Third-party libraries, frameworks, design systems, or services integrated at the Client's direction or as necessary to fulfill the agreed specifications.
- Commercially licensed fonts, icons, stock assets, or media components procured for inclusion in the Deliverables.
Such components are not owned by the Agency and are expressly excluded from the ownership and license provisions of Section 5.1. They remain subject exclusively to their respective third-party license terms, which govern permissible use, distribution, modification, and attribution obligations.
The Agency shall, upon reasonable request and to the extent practicable, provide the Client with a list of material third-party components incorporated into the Deliverables, together with the applicable license type for each.
The Client agrees to:
- Independently review and comply with all applicable third-party license conditions as a condition of using the Deliverables.
- Obtain and maintain, at its own cost, any commercial licenses or subscriptions required for the continued use of third-party components in the Client's production environment beyond any trial or development-phase access arranged by the Agency.
- Indemnify and hold harmless the Agency from any claim, liability, cost, or penalty arising from the Client's failure to comply with applicable third-party license terms, where such failure occurs after delivery of the Deliverables.
Where the use of a third-party component with copyleft or reciprocal licensing obligations — such as the GPL — may affect the licensing of the Deliverables as a whole, the Agency shall notify the Client in writing prior to incorporating such a component. If the Client objects to the licensing implications, the parties shall agree on an alternative approach before the component is incorporated. The Agency shall not be liable for any licensing consequences arising from the Client's decision to proceed with a component despite having been notified of its licensing implications.
5.5 Client License — Conditions Precedent
The license granted to the Client under Section 5.1 is strictly conditional upon the concurrent and complete satisfaction of all of the following conditions:
- Full and final payment of all invoices, fees, and expenses related to the applicable Project, including any interest, penalties, or additional costs accrued in accordance with Section 4, with no amounts remaining outstanding or in dispute.
- Substantial completion of the agreed scope of work as defined in the applicable SOW, unless a partial license has been expressly agreed in writing by both parties.
- The Client's full compliance with these Terms and with the terms of the applicable Project agreement, including timely performance of all Client responsibilities under Section 2.5.
- Execution of any additional documentation reasonably required by the Agency to give effect to the license, where applicable.
Until all such conditions are fully satisfied, the Client shall acquire no license (except as expressly provided in this Section 5) or other right or interest in the Deliverables, and the Agency shall have no obligation to deliver or make available any Deliverables, work in progress, source code, design files, or documentation. For the avoidance of doubt, satisfaction of these conditions entitles the Client to the license only; ownership of all Deliverables remains with the Agency in accordance with Section 5.1.
Where the Client is in breach of any payment obligation, or uses the Deliverables outside the scope of the license, the Agency may, in addition to its rights under Section 4.8, seek injunctive or other equitable relief to prevent unauthorized use, reproduction, or distribution of the Deliverables.
5.6 Moral Rights
To the fullest extent permitted by applicable law, the Agency agrees not to assert, and shall procure that individual creators do not assert, any moral rights, rights of attribution, rights of integrity, or equivalent rights in connection with the Deliverables against the Client, to the extent the Client's use of the Deliverables is within the scope of the license granted under Section 5.1.
Nothing in this Section 5.6 transfers or waives any Intellectual Property Rights of the Agency, which remain governed by Section 5.1.
5.7 SaaS Products — No Transfer of IP
For the avoidance of doubt, nothing in this Section 5 shall operate to transfer, assign, or license to the Client any intellectual property rights in or to any SaaS Product offered by the Agency.
- All intellectual property rights in SaaS Products — including software, interfaces, underlying architecture, databases, algorithms, documentation, and branding — are and shall remain the exclusive property of the Agency.
- The Client's access to and use of SaaS Products is governed solely by the applicable subscription, license, or product-specific agreement, which grants a limited, non-exclusive, non-transferable right to use the SaaS Product for the Client's internal purposes during the subscription term.
- The Client shall not reverse engineer, decompile, disassemble, copy, adapt, or create derivative works based on any SaaS Product, in whole or in part, without the Agency's prior written consent.
- Termination or expiration of a SaaS subscription shall immediately revoke all access rights granted thereunder. The Client shall have no claim to any underlying source code, infrastructure, or proprietary components of the SaaS Product upon termination.
5.8 Portfolio and Attribution Rights
Unless the Client expressly objects in writing prior to Project completion, the Agency reserves the right to:
- Reference the Client's name, brand, and a general description of the Project in the Agency's portfolio, website, case studies, pitch materials, and marketing collateral.
- Display screenshots, mockups, or general visual representations of publicly accessible Deliverables (such as public-facing websites or applications) for promotional purposes.
The Agency shall not disclose any Confidential Information, commercially sensitive details, proprietary business logic, or non-public Deliverables in any such attribution without the Client's prior written consent.
Where the Client objects to any form of portfolio attribution, such objection must be communicated to the Agency in writing before Project completion or, where applicable, before the relevant Deliverable is made publicly accessible. The Agency shall honor all reasonable objections received in a timely manner.
5.9 Representations and Warranties
Each party represents and warrants to the other that:
- It has full authority to enter into these Terms and to grant the rights set out herein.
- Its performance of the Services or use of the Deliverables, as applicable, shall not infringe upon the intellectual property rights or other proprietary rights of any third party.
- In the case of the Agency: the Deliverables produced by the Agency shall, to the best of the Agency's knowledge, be original works or works for which the Agency has obtained the necessary rights, and shall not knowingly incorporate any third-party intellectual property without appropriate licensing or attribution.
- In the case of the Client: all Client-provided materials, data, and instructions shall, to the best of the Client's knowledge, be provided with lawful authority and shall not require the Agency to infringe upon any third-party rights in order to perform the Services.
These warranties do not extend to third-party components, open-source software, or any materials provided by or at the direction of the Client.
5.10 Post-Deployment Edits
From one (1) month after the date on which a page or other Deliverable is deployed to the production Environment, the Client may request edits, updates, or changes to that page or Deliverable, which the Agency shall carry out for a fee.
- Edit requests must be submitted to the Agency in writing and shall describe the requested changes in reasonable detail.
- The Agency shall provide a written quote or time estimate before starting work. Edits shall be charged at the Agency's then-applicable hourly rate, or at a fixed price where agreed in writing, and are payable in accordance with Section 4.
- Where the requested changes are material in scope, the Agency may require them to be handled as a Change Request under Section 2.4 or under a separate SOW.
- Where the Client has a Maintenance and Support Services agreement or Retainer in place, edits shall be handled under that agreement to the extent it covers them.
- The Agency shall use reasonable efforts to carry out edits within a timeframe agreed with the Client, subject to its availability and capacity.
- All edits, and all Intellectual Property Rights in them, are Deliverables owned by the Agency in accordance with Section 5.1 and are included in the Client's license once the fee for them has been paid in full.
- This Section 5.10 does not affect the Agency's obligations to remedy Defects under any applicable warranty.
6. Client Responsibilities
6.1 Provision of Materials and Information
The Client is responsible for providing all necessary materials, content, data, credentials, and access required for the Agency to perform the Services in a timely and complete manner. This includes, where applicable:
- Text, images, media, branding assets, and other content required for the development or population of Deliverables, provided in formats reasonably specified by the Agency.
- System access credentials, API keys, environment configurations, third-party service accounts, and any other authentication or authorization data necessary for the Agency to access relevant platforms, infrastructure, or integrations.
- Technical specifications, functional requirements, business logic documentation, existing system architecture documentation, and any other background materials relevant to the Project scope.
- Timely responses to requests for clarification, approval, or direction from the Agency throughout the engagement.
- Access to relevant internal stakeholders, subject matter experts, or technical personnel where required to gather requirements, validate assumptions, or resolve ambiguities.
- Any third-party software licenses, platform subscriptions, or vendor accounts that the Client is responsible for procuring under the applicable SOW, activated and accessible in advance of the relevant phase of work.
The Client acknowledges that the Agency's ability to deliver Services on time and to the agreed standard is materially dependent on the timely, accurate, and complete provision of the above. The Client shall use reasonable efforts to anticipate the Agency's requirements and provide materials proactively, rather than reactively upon request.
Where the Client provides materials in formats or conditions that require the Agency to perform additional work to render them usable — including but not limited to format conversion, data cleaning, restructuring of content, or resolution of access issues — such additional work may be subject to a Change Request and associated additional fees under Section 2.4.
Delays in providing required inputs, or the provision of incomplete or materially inaccurate materials, may result in delays to agreed project timelines, additional costs, or scope adjustments, none of which shall give rise to any liability on the part of the Agency. The Agency shall notify the Client promptly in writing upon identifying any material gap or deficiency in Client-provided materials that is likely to affect delivery.
6.2 Timely Feedback and Approvals
The Client shall provide feedback, approvals, or documented rejections within the timeframes specified in the applicable SOW or, where no timeframe is specified, within five (5) business days of the Agency's written request.
- Feedback provided by the Client must be sufficiently specific, consolidated, and actionable to allow the Agency to proceed without further clarification. The Agency shall not be obligated to commence revisions based on vague, contradictory, or incomplete feedback.
- Where multiple stakeholders within the Client's organization are involved in the review and approval process, it is the Client's sole responsibility to coordinate internally and provide the Agency with a single, unified response. The Agency shall not be required to manage conflicting instructions from multiple Client representatives.
- Failure to respond within agreed or reasonable timeframes may be treated as deemed acceptance of the relevant Deliverable or milestone, where this is expressly stated in the applicable SOW or Project agreement, in accordance with Section 2.8.
- Where the Client provides approval and subsequently requests changes to an approved Deliverable, such changes shall be treated as a Change Request under Section 2.4 and may be subject to additional time and cost.
- Project schedules, milestones, and delivery dates shall be adjusted to reflect delays attributable to late or absent Client feedback, and the Agency shall communicate any resulting timeline impact in writing as soon as it becomes apparent.
- The Agency shall not be liable for any downstream consequences arising from the Client's delay in providing required approvals, including but not limited to missed market windows, delayed product launches, or third-party contractual obligations of the Client.
6.3 Accuracy and Completeness of Requirements
The Client is responsible for ensuring that all requirements, specifications, and instructions provided to the Agency are accurate, complete, and reflective of the Client's actual needs at the time of the relevant SOW execution.
- Where requirements are provided in stages or evolve during the course of a Project, the Client shall notify the Agency promptly of any changes and acknowledge that such changes may affect scope, cost, and timelines.
- The Agency shall be entitled to rely on the requirements as provided and shall not be held responsible for Deliverables that conform to stated requirements but do not meet the Client's unstated or subsequently revised expectations.
- Where the Client's requirements are incomplete or ambiguous at the time of SOW execution, the Agency shall document any assumptions made in proceeding, and such assumptions shall be treated as agreed unless the Client raises a written objection within five (5) business days of being notified of them.
- Where material requirements gaps are identified during delivery that were not apparent at the time of SOW execution, the parties shall assess the impact in good faith. Requirements additions or revisions that expand the agreed scope shall be subject to a Change Request under Section 2.4.
6.4 Legality of Provided Materials
The Client is solely responsible for ensuring that all materials, content, data, and instructions provided to the Agency:
- Do not infringe upon any third-party intellectual property rights, including copyrights, trademarks, patents, database rights, or rights of publicity or privacy.
- Comply with all applicable laws and regulations in the jurisdiction(s) in which the Client operates or intends to deploy the Deliverables, including but not limited to consumer protection laws, advertising standards, data protection legislation, and sector-specific regulatory requirements.
- Are lawful, accurate, and authorized for use in connection with the Project or Services, including any materials licensed from third parties where the Client is responsible for securing appropriate licensing rights.
- Do not contain any harmful, defamatory, obscene, discriminatory, or otherwise unlawful content that could expose the Agency to legal liability.
- Where applicable, comply with the terms and conditions of any third-party platforms, marketplaces, or distribution channels through which the Client intends to deploy or distribute the Deliverables.
The Client shall indemnify, defend, and hold harmless the Agency and its officers, employees, contractors, and subcontractors from and against any and all claims, losses, damages, liabilities, costs, and expenses (including reasonable legal fees) arising from or relating to any breach of the warranties in this clause, including any third-party claim that Client-provided materials infringe upon that party's intellectual property or other legal rights.
Where the Agency identifies materials provided by the Client that it reasonably believes to be potentially unlawful, infringing, or otherwise problematic, the Agency shall notify the Client in writing and shall be entitled to withhold or refuse to incorporate such materials pending the Client's satisfactory resolution of the issue. The Agency shall not be liable for any delay or failure arising from its reasonable refusal to use materials that it in good faith believes to be non-compliant.
6.5 System Access and Security
Where the Client grants the Agency access to its systems, infrastructure, platforms, or data environments in connection with the Services:
- The Client shall ensure that access permissions are appropriately scoped and limited to what is strictly necessary for the performance of the Services, in accordance with the principle of least privilege.
- The Client remains solely responsible for the security, integrity, and administration of its own systems, including user account management, access control policies, network security configurations, and data backup procedures.
- The Client shall promptly revoke or modify the Agency's access credentials upon completion of the relevant engagement or phase, or upon request by the Agency.
- The Agency shall use Client systems only for the purpose of performing the Services and shall not access, copy, modify, or disclose any data or system content beyond what is strictly necessary for that purpose.
- The Client shall notify the Agency promptly in writing if it becomes aware of any unauthorized access to or use of its systems that may affect the Agency's personnel or the performance of the Services.
- The Client acknowledges that the Agency cannot guarantee the security of Client systems accessed remotely and that the Agency shall not be liable for any security breach, data loss, or unauthorized access affecting Client systems, except to the extent directly and demonstrably caused by the Agency's negligence or willful misconduct.
- Where the Agency is required to handle Client system Credentials, both parties shall agree on a secure method of transmission and storage. The Agency shall treat all Client Credentials as Confidential Information in accordance with Section 7.
6.6 Decision-Making Authority
The Client shall designate a primary authorized representative (the "Decision-Maker") who shall serve as the principal point of contact between the Client and the Agency throughout the engagement. The Decision-Maker shall be responsible for:
- Providing clear, binding, and timely instructions, decisions, and approvals on behalf of the Client.
- Consolidating all internal Client feedback, priorities, and directional decisions into a single coherent response before communicating them to the Agency.
- Escalating and resolving internal disagreements or competing priorities within the Client's organization without delay, so as not to impede the progress of the Project.
- Receiving and distributing Agency communications, deliverables, and documentation within the Client's organization as appropriate.
The Client shall notify the Agency in writing of the identity and contact details of the designated Decision-Maker prior to or at the commencement of each engagement, and shall promptly notify the Agency in writing of any change in that designation, including the identity and contact details of the replacement representative.
The Agency shall be entitled to rely upon and act in accordance with instructions, approvals, and representations made by the designated Decision-Maker as if they were made by the Client itself, without further verification. The Agency shall not be responsible for any loss, delay, or adverse outcome arising from instructions provided by the Decision-Maker that are later disputed or retracted by the Client.
Delays, cost overruns, or quality issues arising from internal Client misalignment, indecision, conflicting instructions, or absence of decision-making authority shall be solely the responsibility of the Client and shall not give rise to any liability on the part of the Agency.
6.7 Compliance with Applicable Laws
The Client is solely responsible for ensuring that its use of the Services and Deliverables complies with all applicable laws, regulations, industry standards, and regulatory requirements in the jurisdiction(s) where the Client operates or intends to deploy the Deliverables. This includes but is not limited to:
- Data protection and privacy laws applicable to the Client's business, including any obligations arising in connection with the collection, storage, processing, or transfer of Personal Data via the Deliverables.
- Consumer protection, e-commerce, and distance selling regulations applicable to the Client's products or services.
- Sector-specific regulatory requirements applicable to the Client's industry, including but not limited to financial services regulation, healthcare compliance, telecommunications law, and export control legislation.
- Accessibility standards and obligations applicable to the Client's digital products, including but not limited to WCAG guidelines or equivalent national standards, where required by law or agreed in the applicable SOW.
- Any licensing, permit, or registration requirements applicable to the Client's business operations or to the deployment of the Deliverables in specific markets or jurisdictions.
The Agency does not provide legal, regulatory, or compliance advice, and nothing in these Terms or any SOW shall be construed as a representation that the Deliverables are compliant with any specific regulatory requirement applicable to the Client's business. The Client is responsible for obtaining independent legal or regulatory advice where required, and for communicating any compliance requirements to the Agency in sufficient detail and in advance to allow them to be incorporated into the agreed scope.
6.8 Prohibited Conduct
The Client shall not, and shall ensure that its employees, agents, and authorized users do not:
- Use the Services, Deliverables, or SaaS Products for any unlawful, fraudulent, or abusive purpose, or in a manner that violates any applicable law, regulation, or third-party rights.
- Interfere with, disrupt, or attempt to gain unauthorized access to the Agency's systems, infrastructure, personnel, or proprietary tools.
- Use the Deliverables to develop, distribute, or deploy malicious software, engage in phishing, facilitate unauthorized data collection, or conduct any activity that could harm third parties.
- Misrepresent the origin, nature, or authorship of any Deliverable, including representing Agency-developed work as the Client's own independent creation in any context that could mislead third parties.
- Attempt to reverse engineer, decompile, or extract proprietary components of the Agency's tools, frameworks, or methodologies embedded in the Deliverables, beyond the license rights expressly granted under Section 5.2.
- Circumvent, disable, or interfere with any security, access control, or usage tracking mechanisms implemented by the Agency in connection with the Services or SaaS Products.
Any breach of this clause shall constitute a material breach of these Terms and may result in immediate suspension of Services, termination of the engagement, and pursuit of any available legal remedies, without prejudice to any other rights or obligations of the parties.
6.9 Cooperation and Good Faith
The Client shall engage with the Agency in good faith throughout the duration of the engagement, including by:
- Participating constructively in project kick-off sessions, planning workshops, review meetings, and other collaborative activities as reasonably requested by the Agency.
- Raising concerns, objections, or dissatisfaction with the Services promptly and in writing, so that the Agency has a reasonable opportunity to address them before they escalate.
- Notifying the Agency promptly of any material change to the Client's business, technical environment, regulatory context, or project priorities that may affect the scope, delivery, or strategic direction of the Services.
- Treating Agency personnel with professional courtesy and respect, and ensuring that its own employees, contractors, and representatives do the same throughout the engagement.
The Client acknowledges that the successful delivery of Services is a collaborative endeavor and that the Agency's performance is materially contingent upon the Client's active and constructive participation. Where the Client's failure to cooperate in good faith directly contributes to a failure of delivery, quality shortfall, or cost overrun, the Agency shall not be held liable for the resulting impact.
6.10 Clarifications and Pre-Commencement Obligations
If any responsibility, requirement, dependency, or obligation set out in this Section 6 is unclear, the Client must raise a written clarification request promptly and before the relevant phase of work commences, so as to avoid delays, misalignment, or abortive work during execution.
Where a clarification request reveals an ambiguity in the agreed scope, responsibilities, or assumptions, the parties shall resolve the matter in writing before proceeding. Any resolution that modifies the Client's obligations or the Agency's scope of work in a material way shall be documented as a Change Request under Section 2.4 or as an amendment to the applicable SOW, as appropriate.
The Client's failure to raise clarifications in a timely manner shall not relieve it of its obligations under this Section 6 or entitle it to claim that any resulting delay or cost is attributable to the Agency.
7. Revisions and Acceptance
7.1 Included Revisions
Each milestone or Deliverable may include a defined number of revision rounds as specified in the applicable SOW or Project agreement. Revision entitlements are intended to allow the Client to refine Deliverables within the agreed scope and shall be subject to the following conditions:
- Revisions are limited to refinements of Deliverables that fall within the originally agreed scope, specifications, and design direction as documented in the applicable SOW. Revisions do not constitute an entitlement to introduce new requirements, expand functionality, or alter agreed design direction.
- The number of included revision rounds, where not expressly stated in the SOW, shall default to two (2) rounds per Deliverable unless otherwise agreed in writing prior to commencement of that Deliverable.
- Each revision round is defined as a single consolidated set of feedback submitted by the Client in writing following the Agency's delivery of the Deliverable or a revised version thereof. Multiple fragmented or sequential feedback submissions made outside of a formal revision round shall not be treated as a single round and may be counted as additional revision cycles at the Agency's reasonable discretion.
- Additional revision rounds beyond the agreed limit may be scoped and billed as a Change Request under Section 2.4, at the Agency's then-applicable hourly rate or as otherwise agreed in writing.
- Revision requests must be submitted within the Acceptance Period defined in Section 7.4. Revision requests submitted after the expiry of the Acceptance Period, or after a Deliverable has been deemed accepted, shall be treated as new requirements and subject to separate scoping and pricing.
- The Agency reserves the right to decline revision requests that it reasonably considers to be materially inconsistent with the agreed scope, technically unfeasible within the current architecture, or likely to compromise the quality or integrity of the Deliverable. In such cases, the Agency shall provide a written explanation and, where possible, propose an alternative approach.
7.2 How to Submit Revision Requests
To ensure revisions are processed efficiently and without ambiguity, the Client shall adhere to the following submission standards:
- All revision requests must be submitted in writing via the communication channel designated in the applicable SOW (e.g., project management platform, email, or ticketing system).
- Each revision request must clearly identify: the specific Deliverable or component to which it relates; a precise description of the change requested; the reason or business justification for the change where applicable; and, where relevant, any reference materials, examples, or annotated screenshots that support the request.
- Feedback must be consolidated and submitted as a single unified communication per revision round. The Agency shall not be required to process feedback submitted in piecemeal or sequential messages as part of the same revision round.
- Verbal revision requests, including those made during calls or meetings, shall not be actioned by the Agency unless confirmed in writing by the Client within twenty-four (24) hours of the relevant communication. The Agency may, but is not obligated to, document verbal instructions on behalf of the Client for written confirmation.
- Where revision requests are unclear, insufficiently detailed, or internally contradictory, the Agency shall request written clarification before commencing work. Time spent resolving ambiguous feedback shall count toward the billable effort of the relevant revision round where applicable.
7.3 Minor vs. Major Changes
For the purposes of these Terms, revisions shall be categorized as either Minor Changes or Major Changes, as follows:
- Minor Changes are adjustments that do not materially alter the core scope, structure, architecture, functionality, or agreed specifications of the Deliverable. Examples include: textual corrections or copy amendments; minor visual adjustments such as color, spacing, or typographic refinements within an established design system; small layout modifications that do not affect information architecture or user flow; correction of Defects identified during the Acceptance Period; and configuration or content updates within an already-built component.
- Major Changes are modifications that affect or alter the agreed scope, system architecture, core functionality, design direction, data model, user experience flows, or agreed specifications of the Deliverable, or that introduce new features, integrations, or capabilities not included in the original SOW. Examples include: addition of new pages, screens, or application modules; changes to the technology stack or infrastructure decisions; redesign of information architecture or navigation structure; introduction of new third-party integrations or API dependencies; changes to business logic, data processing rules, or core algorithms; and visual redesigns that depart materially from approved design direction.
- Where there is a dispute as to whether a requested change constitutes a Minor or Major Change, the Agency's reasonable professional assessment shall prevail, subject to the Client's right to raise a written objection within five (5) business days. In the event of a persistent disagreement, the parties shall seek to resolve the matter in good faith, and work on the disputed change shall not commence until the classification has been agreed.
- All Major Changes shall be treated as Change Requests under Section 2.4 and shall not be actioned until a written Change Request has been approved by both parties, setting out the revised scope, timeline, and pricing implications. The Agency shall not be obligated to absorb the cost of Major Changes within included revision rounds, regardless of the number of revision rounds remaining.
7.4 Acceptance Criteria
Deliverables shall be considered accepted when one of the following conditions is met:
- The Client provides formal written approval confirming that the Deliverable materially conforms to the agreed specifications and acceptance criteria as defined in the applicable SOW; or
- The Acceptance Period expires without the Client having submitted a written rejection notice specifying documented, reasonable, and scope-consistent grounds for rejection, in which case the Deliverable shall be deemed accepted in full as of the final day of the Acceptance Period; or
- The Client makes productive use of the Deliverable in a live, staging, or production environment, which shall constitute implied acceptance regardless of whether formal written approval has been issued or the Acceptance Period has expired.
Where acceptance criteria are not fully defined in the applicable SOW, the standard for acceptance shall be whether the Deliverable materially fulfills the requirements as documented and agreed at the commencement of the relevant phase, interpreted in light of generally accepted professional standards in the software development industry.
Acceptance criteria shall be specific, objective, and verifiable. The Client shall not withhold acceptance on the basis of subjective aesthetic preferences not reflected in the agreed specifications, requirements introduced after SOW execution, or Minor Changes that can be addressed within a subsequent revision round. Acceptance shall not be made conditional upon the completion of items outside the agreed scope of the relevant Deliverable.
Partial acceptance of a Deliverable is permitted where the non-conforming elements are clearly identified in writing, are genuinely isolated from the conforming elements, and the Agency agrees in writing to remediate the non-conforming elements within a defined timeframe. Partial acceptance shall not affect the Client's payment obligations in respect of the accepted portions of the Deliverable.
7.5 Acceptance Period and Deemed Acceptance
Unless otherwise specified in the applicable SOW, the following default Acceptance Period terms shall apply:
- Upon delivery of a Deliverable, the Agency shall notify the Client in writing that the Deliverable is available for review, specifying the commencement date of the Acceptance Period.
- The default Acceptance Period shall be seven (7) business days from the date of such notification, unless a different period is specified in the applicable SOW.
- During the Acceptance Period, the Client shall review the Deliverable against the agreed acceptance criteria and either: provide formal written acceptance; or submit a written rejection notice specifying in reasonable detail each ground for rejection, the specific criteria alleged not to be met, and sufficient supporting information to allow the Agency to reproduce and assess the issue.
- Rejection notices that do not specify concrete, scope-consistent grounds shall not constitute a valid rejection for the purposes of this clause, and the Deliverable shall be treated as deemed accepted unless the deficiencies are documented with reasonable particularity within the Acceptance Period.
- If the Client fails to provide either written acceptance or a valid written rejection notice within the Acceptance Period, the Deliverable shall be automatically deemed accepted as of the final day of the Acceptance Period, and the associated payment obligations shall become immediately due.
- Deemed acceptance shall have the same legal effect as express written acceptance for all purposes under these Terms, including the triggering of payment obligations and the commencement of any applicable warranty or support period.
- The Acceptance Period shall be paused if the Agency fails to deliver a Deliverable in a reasonably usable or reviewable state. The Acceptance Period shall recommence from the point of interruption upon delivery of a corrected or complete version, unless the parties agree otherwise in writing.
- Extension of the Acceptance Period shall only be granted upon the Client's written request submitted before the expiry of the original period, and shall be at the Agency's sole discretion. Any extension shall be confirmed in writing and shall specify the revised expiry date.
7.6 Defect Remediation Following Rejection
Where the Client submits a valid rejection notice within the Acceptance Period:
- The Agency shall review the documented objections and, within a reasonable timeframe (to be communicated to the Client in writing), confirm whether each ground for rejection constitutes a Defect as defined in Section 1.
- Confirmed Defects shall be remediated by the Agency using commercially reasonable efforts within an agreed timeframe. Upon remediation, the Deliverable shall be resubmitted to the Client for review, and a new Acceptance Period shall commence from the date of resubmission.
- Grounds for rejection that do not constitute Defects — including items outside the agreed scope, aesthetic preferences not reflected in agreed specifications, or requirements introduced after SOW execution — shall be communicated to the Client in writing, with a clear explanation. Such items may be addressed as Minor or Major Changes in accordance with Section 7.3.
- Where the Agency disputes a rejection on the grounds that the Deliverable materially conforms to the agreed specifications, the parties shall attempt to resolve the disagreement in good faith within ten (10) business days. If no resolution is reached, either party may escalate the matter in accordance with the dispute resolution provisions of Section 10.
- The number of remediation cycles following a valid rejection shall not be unlimited. Where a Deliverable has undergone two (2) or more remediation cycles and the Client continues to raise objections that the Agency considers inconsistent with the agreed acceptance criteria, the Agency reserves the right to request independent technical review or to escalate to dispute resolution under Section 10.
7.7 Post-Acceptance Defects
Following formal or deemed acceptance of a Deliverable:
- The Client shall remain entitled to report Defects identified after acceptance, provided that such Defects were present in the Deliverable at the time of delivery and were not reasonably identifiable during the Acceptance Period through ordinary review.
- Post-acceptance Defects shall be reported in writing with sufficient detail to allow the Agency to reproduce the issue. The Agency's obligation to remediate post-acceptance Defects shall be governed by the applicable Maintenance and Support terms, if any, or by separate written agreement.
- Where no Maintenance and Support agreement is in place, the Agency shall have no automatic obligation to remediate post-acceptance Defects, but may agree to do so at its applicable rates as a separate engagement.
- Defects introduced or caused by the Client's modification of Deliverables, use of incompatible third-party services, environmental changes outside the Agency's control, or failure to maintain agreed infrastructure shall not be the Agency's responsibility to remediate.
- Issues arising from the Client's failure to update, maintain, or properly configure third-party dependencies following delivery shall not constitute Defects attributable to the Agency.
7.8 Sign-Off and Go-Live Authorization
Where a Project includes a deployment or go-live phase:
- The Agency shall not deploy Deliverables to a production environment without the Client's prior written authorization, except where the Client has expressly delegated deployment authority to the Agency in the applicable SOW.
- The Client's written authorization to proceed with deployment shall constitute final acceptance of all Deliverables included in the relevant release, and shall be treated as formal sign-off for the purposes of triggering any associated payment milestones.
- Where the Client requests deployment before formal acceptance has been granted, such deployment shall be treated as implied acceptance of the Deliverables in their then-current state, and the Agency shall document this in writing. Any Defects identified after an early deployment authorized by the Client shall be subject to the post-acceptance Defect provisions of Section 7.7.
- The Agency shall not be liable for any issues, disruptions, data loss, or adverse consequences arising from a go-live deployment that was authorized by the Client, including where the Client elected to proceed despite documented warnings or outstanding items communicated by the Agency.
8. Timeline and Delays
8.1 Estimated Timelines
All project timelines, delivery schedules, and milestone dates provided by the Agency are estimates made in good faith, based on the information, requirements, resource availability, and assumptions known at the time of planning. Unless a timeline is expressly stated as fixed and guaranteed in a duly executed SOW, all dates and durations are indicative only and subject to change.
- Timeline estimates are prepared on the basis of the scope, specifications, and Client-provided information available at the time of planning. Material changes to any of these factors may necessitate a revision of the estimated timeline, which shall be communicated to the Client in writing as soon as reasonably practicable.
- The Agency shall use commercially reasonable efforts to meet agreed estimated timelines and shall proactively communicate any identified risk to a scheduled date as soon as that risk becomes apparent, together with a proposed revised schedule where possible.
- Where a timeline is stated as fixed in the applicable SOW, such commitment is expressly contingent upon the Client fulfilling all of its responsibilities under Section 6 on time and in full, and upon the absence of any of the delay-causing factors described in Sections 8.2 and 8.3. A fixed timeline shall not be treated as an absolute guarantee where it is materially impacted by factors outside the Agency's reasonable control.
- Timelines agreed in a SOW reflect the Agency's resource planning at the time of execution. Where a Project is delayed at the Client's request or due to Client-side factors, the Agency cannot guarantee that the same resources will be available upon resumption, and revised timelines shall be agreed in writing before work recommences.
- Time is not of the essence in relation to any delivery date under these Terms unless expressly stated as such in the applicable SOW, and any failure to meet an estimated timeline shall not entitle the Client to terminate the agreement, withhold payment, or claim damages except where a fixed, guaranteed deadline has been expressly agreed and the Agency's failure to meet it constitutes a material breach.
8.2 Client-Caused Delays
The Agency shall not be held responsible or liable for any delay, cost overrun, or failure to meet agreed timelines arising from factors attributable to the Client, including but not limited to:
- Late, incomplete, or inaccurate provision of materials, content, assets, credentials, or access required by the Agency to perform the Services, as set out in Section 6.1.
- Delayed, absent, or insufficiently specific feedback, approvals, or decisions at any stage of the Project, including during design reviews, milestone sign-offs, or Acceptance Periods.
- Changes to requirements, scope, priorities, or specifications introduced after SOW execution, whether formalized as Change Requests or otherwise.
- Internal Client misalignment, change of personnel, reorganization, or delay in designating or replacing the authorized Decision-Maker under Section 6.6.
- Failure by the Client to procure, activate, or provide timely access to required third-party licenses, platform accounts, or vendor services that the Client is responsible for under the applicable SOW.
- Technical issues, outages, or configuration problems within the Client's own systems, infrastructure, or environments that impede the Agency's access or ability to perform.
- Delay in executing required documentation, including SOWs, Change Requests, or written authorizations that are a prerequisite to commencing or continuing a phase of work.
Where a Client-caused delay occurs, the following consequences shall apply:
- The Agency shall notify the Client in writing of the delay, its cause, and the estimated impact on the project schedule.
- Agreed timelines and milestones shall be automatically extended by a period at least equal to the duration of the Client-caused delay, plus any reasonable additional time required by the Agency to remobilize resources and resume work.
- Where a Client-caused delay results in the Agency's resources being redeployed to other engagements, the Agency shall not be obligated to resume the delayed Project immediately upon the Client's readiness to proceed. Resumption shall be subject to the Agency's resource availability, and the parties shall agree a revised schedule in writing before work recommences.
- Where a Client-caused delay results in the Agency incurring additional costs — including costs of standing down resources, rescheduling third-party commitments, or extended project administration — such costs may be charged to the Client as a Change Request or separate invoice, as applicable.
- The Agency's right to charge for completed work and committed costs shall not be affected by any Client-caused delay, and all amounts that have become due and payable shall remain so regardless of the delay.
8.3 Third-Party and Infrastructure Delays
The Agency shall not be held liable for delays attributable to third-party services, platforms, infrastructure providers, or external dependencies, including but not limited to:
- Failures, outages, degraded performance, or unexpected changes to third-party APIs, SDKs, cloud platforms, or SaaS services integrated into or relied upon by the Deliverables.
- Delays in provisioning, configuration, or support responses from external hosting providers, domain registrars, CDN providers, or payment processors.
- Changes to third-party platform terms, APIs, or functionality that require unplanned rework or redesign of components previously built to a prior specification.
- Delays in approval processes, review queues, or policy enforcement by app stores, marketplace operators, or regulatory submission portals.
- Unavailability or performance degradation of development tools, version control platforms, cloud services, or communication infrastructure relied upon by the Agency in the normal course of performing Services.
Where a third-party delay materially affects the Project, the Agency shall:
- Notify the Client in writing as soon as the delay is identified, including the nature of the third-party issue and its anticipated impact on the delivery schedule.
- Use commercially reasonable efforts to identify and propose a workaround, alternative approach, or interim solution where one exists.
- Adjust the affected timeline and milestones accordingly, and communicate a revised schedule to the Client in writing.
The Client acknowledges that the Agency has no control over third-party platforms and cannot guarantee their continued availability, performance, or compatibility. The Agency's obligation is to act promptly and professionally in response to third-party disruptions, not to guarantee outcomes dependent on factors beyond its control.
8.4 Force Majeure
Neither party shall be in breach of these Terms or liable to the other for any delay or failure in performance of its obligations to the extent that such delay or failure is caused by a Force Majeure Event, as defined in Section 1.
Force Majeure Events include, without limitation:
- Server infrastructure failures or widespread internet or telecommunications outages not caused by the affected party's negligence.
- Cyberattacks, ransomware incidents, or security breaches perpetrated by third parties that materially disrupt the affected party's operations.
- Natural disasters, including earthquakes, floods, fires, storms, or other acts of God.
- War, armed conflict, invasion, terrorism, civil unrest, riot, or insurrection.
- Governmental actions, sanctions, embargoes, trade restrictions, or changes in law that materially impede performance.
- Strikes, labor disputes, or industrial action affecting the affected party or its critical suppliers.
- Epidemics, pandemics, or public health emergencies declared by a competent authority that materially affect the affected party's ability to perform.
- Failures of critical third-party providers or infrastructure upon which the affected party reasonably relies, where such failures are beyond the affected party's reasonable control.
The following procedural requirements shall apply in the event of a Force Majeure Event:
- The party seeking to invoke Force Majeure shall notify the other party in writing as soon as reasonably practicable after becoming aware of the Force Majeure Event, describing the nature of the event, its anticipated duration, and the obligations affected.
- Failure to provide timely notice shall not preclude a party from invoking Force Majeure, but may be taken into account in assessing any resulting liability for delay.
- Upon notification, the affected party's performance obligations shall be suspended for the duration of the Force Majeure Event to the extent they are materially prevented or impaired, without liability to the other party.
- The affected party shall use commercially reasonable efforts to mitigate the effects of the Force Majeure Event and to resume performance as soon as reasonably possible following its cessation.
- Both parties shall cooperate in good faith during the period of suspension to agree on appropriate interim measures, revised timelines, and any necessary adjustments to the scope or cost of the engagement.
If a Force Majeure Event continues for a period exceeding sixty (60) consecutive calendar days, either party may terminate the affected engagement upon written notice to the other, without liability to either party except in respect of amounts already due and payable for work completed prior to the suspension.
Force Majeure shall not excuse the Client's obligation to pay any amounts already due and payable at the time the Force Majeure Event occurs, nor shall it entitle the Client to a refund of fees paid for Services already performed.
8.5 Agency-Initiated Delays and Proactive Communication
Where the Agency anticipates or encounters a delay attributable to its own operations, resourcing, or capacity — including personnel absence, unexpected technical complexity, or internal scheduling conflicts — the Agency shall:
- Notify the Client in writing as soon as the delay is identified, and in any event before the originally agreed delivery date or milestone date is missed.
- Provide a revised delivery estimate with as much specificity as reasonably practicable, together with a brief explanation of the cause of the delay.
- Propose and, where agreed, implement mitigation measures to minimize the impact of the delay on the overall Project schedule.
- Where the delay is likely to affect a critical path milestone or the Client's own downstream obligations, prioritize proactive communication and resolution accordingly.
The Agency's obligation under this clause is one of prompt and transparent communication; it does not constitute a guarantee that all delays attributable to internal factors will be avoidable. The Agency shall not be liable for reasonable operational delays that are promptly communicated, appropriately mitigated, and do not constitute a material breach of the applicable agreement.
8.6 Revised Schedules and Mutual Agreement
Where a delay occurs for any reason, the parties shall cooperate in good faith to agree on a revised project schedule in writing before work resumes on the affected phase. The following principles shall apply:
- Revised schedules shall be documented in writing and signed or confirmed by both parties before they become effective. Informal verbal agreements regarding revised timelines shall not be binding on either party.
- Where a delay affects multiple interdependent milestones, the revised schedule shall address the impact on the full downstream delivery plan, not merely the immediately affected milestone.
- Agreement on a revised schedule shall not constitute a waiver of either party's rights in respect of the cause of the original delay, unless expressly stated in writing.
- Where the parties are unable to agree on a revised schedule within ten (10) business days of a delay being notified, either party may escalate the matter in accordance with the dispute resolution provisions of Section 10.
- In cases where a revised schedule results in a material extension of the overall Project duration, the Agency reserves the right to review and adjust its resource allocation, and where applicable, to propose revised pricing reflecting the extended engagement period, which shall be subject to written agreement by both parties.
8.7 Liquidated Damages and Penalty Clauses
Unless expressly agreed in a duly executed SOW and subject to the conditions set out therein:
- No liquidated damages, penalty clauses, service credits, or financial remedies for delay shall apply to the Agency's performance under these Terms.
- Where a SOW expressly provides for liquidated damages for delay, such damages shall only apply where: the affected timeline is expressly stated as fixed and guaranteed; the delay is solely and directly attributable to the Agency's own failure to perform; and the Client has fulfilled all of its obligations under Section 6 in full and on time.
- Any liquidated damages provision agreed in a SOW shall represent the Client's sole and exclusive financial remedy for delay, and shall operate as a cap on the Agency's liability for delay-related losses, not as a floor or minimum entitlement.
- Liquidated damages shall not apply to delays caused in whole or in part by Client-side factors, Force Majeure Events, third-party dependencies, or any other circumstances described in Sections 8.2, 8.3, or 8.4.
9. Third-Party Services
9.1 External Dependencies
The Services and Deliverables may rely upon, integrate with, or be built upon third-party services, systems, platforms, or providers. Such dependencies are a standard and often necessary feature of modern software development, and their use is subject to the terms set out in this Section 9.
Third-party dependencies may include, without limitation:
- Cloud infrastructure and hosting providers, including but not limited to Amazon Web Services (AWS), Google Cloud Platform (GCP), Microsoft Azure, and equivalent infrastructure-as-a-service providers.
- Domain name registrars, DNS providers, and content delivery networks (CDNs).
- APIs and external data services, including mapping services, geolocation providers, weather data feeds, financial data providers, and communication APIs.
- Payment gateways, financial processors, and embedded fintech providers, including but not limited to Stripe, PayPal, and equivalent services.
- Authentication and identity providers, including OAuth providers, single sign-on (SSO) platforms, and multi-factor authentication services.
- Content management systems (CMS), headless CMS platforms, and digital asset management systems.
- Email delivery services, SMS gateways, and push notification platforms.
- Analytics, monitoring, logging, and error tracking services.
- Software libraries, frameworks, open-source components, and package registries.
- Artificial intelligence and machine learning APIs, large language model providers, and AI-powered service integrations.
- Any other external platforms, services, or tools required for the functionality, performance, or deployment of the Deliverables as specified in or reasonably inferred from the applicable SOW.
Where the Agency proposes to use a specific third-party service or dependency in connection with the Deliverables, it shall identify material third-party dependencies in the applicable SOW or, where they are identified after SOW execution, notify the Client in writing in advance of their integration where reasonably practicable. The Client's approval of a SOW that references or reasonably implies the use of specific third-party services shall constitute the Client's acceptance of those dependencies and their associated risks and limitations.
9.2 Selection and Recommendation of Third-Party Services
Where the Agency recommends or selects a third-party service for use in connection with the Services or Deliverables:
- Such recommendations are made in good faith based on the Agency's professional experience and the information available at the time, and do not constitute a guarantee of the third-party service's continued suitability, availability, performance, pricing, or compliance with the Client's requirements.
- The Agency shall use reasonable professional judgment in selecting third-party dependencies that are appropriate for the Client's use case, scale, and technical context, but the Client retains the right to request the use of alternative services, subject to the Agency's assessment of technical feasibility and any resulting impact on scope, cost, or timeline.
- Where the Client specifies or mandates the use of a particular third-party service, the Agency shall not be responsible for any limitations, constraints, or adverse outcomes arising from that choice, including compatibility issues, performance degradation, licensing restrictions, or vendor lock-in.
- The Agency shall not receive undisclosed financial incentives, commissions, or referral fees from third-party providers in connection with recommendations made to the Client. Where any commercial relationship exists between the Agency and a recommended third-party provider, the Agency shall disclose this to the Client upon request.
9.3 No Responsibility for Third-Party Services
The Agency assumes no responsibility or liability for the availability, performance, security, reliability, accuracy, or fitness for purpose of any Third-Party Service, whether or not its use was recommended or implemented by the Agency. Specifically:
- Third-Party Services may be modified, updated, degraded, suspended, or discontinued at any time by their respective providers, with or without notice, and the Agency has no control over such decisions.
- The Agency shall not be liable for any downtime, outages, data loss, data corruption, service disruptions, latency issues, or errors caused directly or indirectly by Third-Party Services, regardless of whether such services are integrated into the Deliverables.
- Changes in third-party pricing, licensing terms, API rate limits, usage policies, data handling practices, or technical specifications are outside the Agency's control and may affect the functionality, cost, or viability of the Deliverables. The Agency shall not be liable for the consequences of such changes.
- The Agency shall not be liable for any security vulnerability, data breach, or compliance failure originating within a Third-Party Service, including but not limited to unauthorized access to data processed or stored by a third-party platform.
- The Agency does not warrant that any Third-Party Service will remain compatible with the Deliverables following updates or changes made by the third-party provider after delivery. Maintaining such compatibility following third-party-initiated changes is subject to the Maintenance and Support terms, if any, or to a separate written agreement.
Where a Third-Party Service materially fails, is discontinued, or undergoes changes that affect the functionality of the Deliverables, the Agency may, where feasible and upon the Client's written request, assist in adapting the Deliverables to accommodate such changes. Any such adaptation work shall be scoped, priced, and documented as a Change Request under Section 2.4, at the Agency's then-applicable rates, unless a Maintenance and Support agreement expressly covers such scenarios.
9.4 Client Responsibility for Third-Party Compliance
The Client is solely responsible for:
- Reviewing, understanding, and complying with all applicable terms of service, acceptable use policies, privacy policies, licensing terms, and usage restrictions imposed by any Third-Party Service used in connection with the Deliverables, whether selected by the Agency or the Client.
- Ensuring that its use of Third-Party Services does not exceed applicable usage limits, rate limits, or geographic restrictions imposed by the relevant provider.
- Maintaining active subscriptions, licenses, and billing arrangements with all Third-Party Service providers required for the ongoing operation of the Deliverables following delivery, and ensuring timely renewal of such arrangements to avoid service disruption.
- Promptly notifying the Agency of any material changes to Third-Party Service terms, pricing, or availability that may affect an active Project or the ongoing use of a Deliverable.
- Obtaining all necessary consents, authorizations, and regulatory approvals required to integrate or use any Third-Party Service in the Client's jurisdiction or industry sector, including compliance with sector-specific data localization, financial regulation, or healthcare data requirements.
- Ensuring that the use of any Third-Party Service in connection with the Deliverables does not violate any contractual obligations the Client owes to its own customers, partners, or regulators.
The Client acknowledges that the Agency's ability to integrate with and support Third-Party Services is contingent upon the Client maintaining valid and active accounts, credentials, and access arrangements with the relevant providers. Where the Client's account is suspended, restricted, or terminated by a Third-Party Service provider for any reason, the Agency shall not be liable for any resulting impact on the Deliverables or Services, and any remediation work required may be subject to additional charges.
9.5 Open-Source Components
Where the Deliverables incorporate open-source software components:
- The Agency shall use open-source components that are, to the best of its knowledge at the time of integration, licensed under terms compatible with the Client's intended use of the Deliverables.
- The Client acknowledges that certain open-source licenses — including copyleft or reciprocal licenses such as the GPL, LGPL, or AGPL — may impose obligations on the Client with respect to the distribution, modification, or disclosure of source code. The Agency shall notify the Client in advance where it intends to incorporate a component subject to such a license, in accordance with Section 5.4.
- The Agency shall, upon request and to the extent reasonably practicable, provide the Client with a software bill of materials (SBOM) or equivalent list of material open-source components incorporated into the Deliverables, together with their applicable license identifiers.
- The Client is responsible for independently assessing and ensuring its compliance with all open-source license obligations applicable to its use, distribution, and commercialization of the Deliverables, and for obtaining independent legal advice where the licensing implications are material to the Client's business.
- The Agency does not warrant that open-source components are free from security vulnerabilities, defects, or incompatibilities that may emerge following delivery. The Client is responsible for monitoring and applying security updates to open-source dependencies in the production environment, either directly or through a Maintenance and Support arrangement with the Agency.
9.6 Vendor Lock-In and Portability
Where the use of a specific Third-Party Service creates a dependency that may affect the Client's ability to migrate, switch providers, or operate the Deliverables independently in the future:
- The Agency shall, where reasonably practicable and upon the Client's written request, identify material vendor lock-in risks associated with the proposed architecture or technology choices at the time of planning.
- The Client's acceptance of an SOW that incorporates a specific Third-Party Service shall constitute the Client's informed acceptance of any associated portability limitations, unless the SOW expressly requires the Agency to implement a vendor-agnostic or portable architecture.
- Where the Client subsequently requests a migration away from a Third-Party Service, such migration shall be treated as a separate engagement, scoped and priced accordingly, and shall not be considered a Defect or warranty obligation of the Agency.
- The Agency shall not be liable for the cost, complexity, or feasibility of migrating from a Third-Party Service that was selected in good faith at the time of the Project, where that migration becomes necessary due to third-party pricing changes, policy changes, service discontinuation, or the Client's evolving business requirements.
9.7 Third-Party Accounts and Credentials
Where the Agency is required to create, configure, or access third-party accounts on behalf of the Client in connection with the Services:
- All such accounts shall be registered in the Client's name and under the Client's billing and ownership details, unless otherwise expressly agreed in writing. The Agency shall not register third-party services or infrastructure in its own name on the Client's behalf, except as a temporary measure during development and with the Client's prior written consent.
- Upon Project completion or at the Client's written request, the Agency shall transfer administrative access, ownership credentials, and all relevant account details to the Client or its designated representative in a timely and orderly manner.
- The Client shall be solely responsible for the ongoing billing, renewal, security, and administration of all third-party accounts following handover.
- Where the Agency temporarily holds Credentials for third-party accounts in connection with the Services, it shall treat such Credentials as Confidential Information in accordance with Section 7, and shall securely delete or return them upon Project completion or upon the Client's written request.
- The Agency shall not be liable for any service disruption, data loss, or adverse consequence arising from the Client's failure to maintain, renew, or administer third-party accounts following handover.
9.8 AI and Machine Learning Services
Where the Deliverables incorporate or integrate artificial intelligence, machine learning, or large language model services provided by third parties:
- The Client acknowledges that such services are subject to the terms, usage policies, content restrictions, and data handling practices of the relevant AI provider, and that these terms may change materially over time.
- The Agency makes no warranty as to the accuracy, reliability, consistency, or fitness for purpose of outputs generated by third-party AI services, and shall not be liable for any decision, loss, or adverse outcome arising from the Client's reliance on AI-generated outputs in its products or operations.
- The Client is solely responsible for assessing and ensuring the suitability of AI-generated outputs for its intended use case, including compliance with applicable regulatory requirements governing the use of automated decision-making, AI transparency, or algorithmic accountability in the Client's jurisdiction or industry.
- Where the integration of AI services involves the processing of Personal Data or other sensitive information, the Client is responsible for ensuring that such processing complies with applicable data protection laws, including any obligations relating to international data transfers, data minimization, or purpose limitation.
- The Agency shall notify the Client of any material changes to the AI services integrated into the Deliverables that come to its attention during the course of an active engagement. Post-delivery changes to AI service terms or behavior are outside the Agency's reasonable control and shall be addressed in accordance with Section 9.3.
10. Confidentiality
10.1 Confidential Information
Each party (the "Disclosing Party") may, in the course of the engagement, disclose to the other party (the "Receiving Party") information that is confidential or proprietary in nature. For the purposes of these Terms, "Confidential Information" includes, without limitation:
- Business plans, strategies, forecasts, roadmaps, competitive intelligence, and financial information, including revenue figures, pricing structures, cost models, and investment plans.
- Technical documentation, source code, algorithms, system architecture, database schemas, API specifications, infrastructure configurations, and proprietary software.
- Access credentials, API keys, authentication tokens, encryption keys, and any other security-sensitive data.
- Personal data, user databases, customer records, and any data relating to identified or identifiable individuals processed in connection with the Services.
- Internal processes, methodologies, workflows, frameworks, tools, and operational know-how of either party.
- Project-specific information, including SOW contents, deliverable specifications, milestone structures, pricing, and negotiated terms.
- Commercial arrangements, vendor relationships, partnership terms, and supplier contracts.
- Any information disclosed by either party that a reasonable person in the relevant industry would understand to be confidential given the nature of the information and the circumstances of its disclosure, regardless of whether it is expressly marked, labeled, or identified as "confidential" at the time of disclosure.
Confidential Information shall be deemed to encompass both information disclosed intentionally and information that comes to the Receiving Party's attention incidentally in the course of the engagement.
10.2 Exclusions from Confidentiality
The obligations set out in this Section 10 shall not apply to information that the Receiving Party can demonstrate, by clear and contemporaneous written evidence:
- Was already in the public domain at the time of disclosure, or subsequently enters the public domain through no act or omission of the Receiving Party or any person to whom the Receiving Party has disclosed it.
- Was already lawfully known to the Receiving Party prior to its disclosure by the Disclosing Party, free of any obligation of confidence.
- Was independently developed by the Receiving Party without reference to or use of the Disclosing Party's Confidential Information, as evidenced by contemporaneous written records.
- Was lawfully received from a third party who had the right to disclose it without restriction and without breach of any obligation owed to the Disclosing Party.
- Is required to be disclosed by applicable law, regulation, court order, or the direction of a competent governmental or regulatory authority, subject to the conditions set out in Section 10.5.
The burden of establishing that any of the above exclusions applies shall rest with the Receiving Party asserting the exclusion.
10.3 Obligations of Confidentiality
Each party, in its capacity as Receiving Party, agrees to:
- Hold all Confidential Information of the Disclosing Party in strict confidence and treat it with at least the same degree of care as it applies to its own confidential information of a comparable nature, and in any event no less than a reasonable standard of care.
- Use Confidential Information solely for the purpose of performing its obligations or exercising its rights under the applicable agreement, and for no other purpose whatsoever.
- Not disclose, transfer, publish, or otherwise make available any Confidential Information to any third party without the prior written consent of the Disclosing Party, except as expressly permitted under these Terms.
- Limit internal access to Confidential Information to those of its employees, contractors, and authorized representatives who have a genuine need to access such information for the purposes of the engagement, and who are bound by written confidentiality obligations no less protective than those set out in this Section 10.
- Implement and maintain reasonable and appropriate technical, organizational, and physical safeguards to protect Confidential Information against unauthorized access, use, disclosure, alteration, or destruction, commensurate with the sensitivity of the information and the risks involved.
- Promptly notify the Disclosing Party in writing upon becoming aware of any actual or suspected unauthorized access to, disclosure of, or use of Confidential Information, and cooperate fully with the Disclosing Party in investigating and mitigating the consequences of such an event.
- Not copy, reproduce, reverse engineer, or otherwise exploit Confidential Information beyond what is strictly necessary for the agreed purpose.
- Not use Confidential Information for competitive purposes, to develop competing products or services, or in any manner that is adverse to the Disclosing Party's legitimate business interests.
10.4 Permitted Disclosures to Subcontractors and Advisors
Each party may disclose Confidential Information to its subcontractors, professional advisors (including legal counsel and auditors), and other authorized third parties where strictly necessary for the performance of the agreement, subject to the following conditions:
- Prior to any such disclosure, the Receiving Party shall ensure that the relevant third party is bound by written confidentiality obligations that are no less protective than those set out in this Section 10.
- The Receiving Party shall remain fully liable to the Disclosing Party for any breach of confidentiality by any third party to whom it has disclosed Confidential Information, as if the breach had been committed by the Receiving Party itself.
- The Receiving Party shall disclose only the minimum amount of Confidential Information necessary to enable the relevant third party to fulfill their specific function, and shall not provide access to Confidential Information beyond that scope.
- The Agency shall not disclose Client Confidential Information to any subcontractor who will have access to Client production systems, Personal Data, or particularly sensitive business information without the Client's prior written consent, as provided in Section 2.6.
10.5 Legally Compelled Disclosure
Where the Receiving Party is required by applicable law, regulation, court order, or the direction of a competent governmental, regulatory, or judicial authority to disclose any Confidential Information of the Disclosing Party, the Receiving Party shall, to the extent permitted by law:
- Provide the Disclosing Party with prompt written notice of the requirement to disclose, sufficiently in advance of the required disclosure to allow the Disclosing Party a reasonable opportunity to seek a protective order, injunction, or other appropriate legal remedy.
- Cooperate reasonably with the Disclosing Party in any effort to resist, limit, or obtain confidential treatment of the required disclosure.
- Disclose only that portion of the Confidential Information that is strictly required by the applicable legal obligation, and use reasonable efforts to ensure that any such disclosure is subject to appropriate confidentiality protections.
- The Receiving Party's compliance with a legally compelled disclosure, conducted in accordance with this clause, shall not constitute a breach of its confidentiality obligations under these Terms.
10.6 Agency Internal Materials
All internal tools, proprietary frameworks, development methodologies, codebases, workflow systems, internal documentation, and operational know-how of the Agency are and shall remain strictly confidential and the exclusive proprietary property of the Agency. Specifically:
- Such materials do not constitute Client Deliverables and are not subject to any assignment or transfer to the Client, irrespective of whether they are used in the course of performing Services for the Client.
- The Client shall have no right to access, copy, reverse engineer, reproduce, or disclose the Agency's internal materials, and no license to use them is granted except as strictly necessary for the Client's use of the Deliverables as described in Section 5.2.
- The Agency's internal materials retain their confidential character even where elements of them are embedded in or underpin the Deliverables, and the Client's rights in relation to any such embedded components shall be limited to the license granted under Section 5.2.
- The Client shall immediately notify the Agency upon becoming aware of any unauthorized access to or disclosure of the Agency's internal materials, and shall cooperate fully with the Agency in addressing such an event.
10.7 Return or Destruction of Confidential Information
Upon termination or expiration of the engagement, or upon the Disclosing Party's written request at any time:
- The Receiving Party shall, at the Disclosing Party's election, promptly return or securely destroy all Confidential Information in its possession or control, including all copies, extracts, summaries, and derivative materials, whether held in physical or electronic form.
- Where destruction is elected, the Receiving Party shall provide the Disclosing Party with written confirmation that destruction has been completed in accordance with this clause within a reasonable timeframe.
- The Receiving Party may retain copies of Confidential Information to the extent required by applicable law or its bona fide internal compliance, audit, or regulatory obligations, provided that: such retained copies remain subject to the confidentiality obligations of this Section 10 for as long as they are retained; access to such copies is restricted to personnel with a legitimate compliance need; and the Receiving Party notifies the Disclosing Party of the categories of information retained and the basis for retention upon request.
- Where the Receiving Party retains Confidential Information in backup systems or archived formats in the ordinary course of its IT operations, it shall use reasonable efforts to purge such information in accordance with its standard data retention schedule, and shall in the interim ensure that such information remains subject to the protections required under this Section 10.
10.8 Injunctive Relief
Each party acknowledges that:
- A breach or threatened breach of the confidentiality obligations under this Section 10 may cause the Disclosing Party irreparable harm for which monetary damages would be an inadequate remedy.
- Accordingly, in the event of an actual or threatened breach, the Disclosing Party shall be entitled to seek injunctive relief, specific performance, or other equitable remedies from a court of competent jurisdiction, without the requirement to post a bond or other security and without prejudice to any other rights or remedies available at law or in equity.
- Nothing in this clause shall be construed as limiting either party's right to pursue any other legal remedy available to it in connection with a breach of this Section 10.
10.9 Non-Solicitation of Clients and Contacts
In addition to the obligations set out in Section 3.6 regarding personnel, the following non-solicitation obligations shall apply during the term of the engagement and for a period of twelve (12) months following its conclusion:
- The Client shall not, directly or indirectly, solicit, approach, or engage any client, prospect, or strategic partner of the Agency that the Client became aware of through its engagement with the Agency, for the purpose of obtaining services that are competitive with or similar to those provided by the Agency.
- The Agency shall not, directly or indirectly, solicit the Client's customers or business partners that it became aware of through the performance of the Services for the purpose of offering directly competing services, without the Client's prior written consent.
- Nothing in this clause shall restrict either party from conducting general, non-targeted marketing or advertising activities, or from engaging with any person or entity that independently approaches them without prior solicitation.
10.10 Duration of Confidentiality Obligations
Confidentiality obligations under this Section 10 shall remain in full force and effect:
- During the entire term of the engagement and any renewal or extension thereof; and
- For a period of five (5) years following the date of termination, expiration, or completion of the engagement, unless a longer period is agreed in writing or required by applicable law.
Notwithstanding the foregoing, the following categories of information shall remain subject to confidentiality obligations indefinitely, without time limitation:
- Trade secrets of either party, for so long as such information retains its character as a trade secret under applicable law.
- Personal Data, which shall remain subject to the data protection obligations set out in Section 11 for as long as it is retained by either party.
- Security credentials, API keys, encryption keys, and similar security-sensitive information, for as long as such information remains active or in use.
The expiration of the confidentiality period shall not affect any right or obligation that has accrued prior to that date, including any right to seek remedies for a breach that occurred during the confidentiality period.
10.11 Relationship to Separate NDA
Where the parties have executed a separate non-disclosure agreement (NDA) prior to or concurrently with these Terms:
- The provisions of this Section 10 shall apply in addition to, and shall not supersede or replace, any separate NDA unless the separate NDA expressly states otherwise or the parties agree in writing that these Terms shall govern exclusively.
- In the event of any conflict between the provisions of this Section 10 and a separately executed NDA, the terms that provide the greater level of protection to the Disclosing Party shall prevail, unless the parties have expressly agreed otherwise in writing.
- Where a separate NDA was executed solely for the purposes of pre-contractual discussions and does not expressly address the ongoing engagement, this Section 10 shall govern confidentiality obligations in relation to the performance of the Services.
11. Warranties and Disclaimers
11.1 Agency Warranties
Notwithstanding the disclaimers set out in this Section 11, the Agency makes the following limited warranties in connection with the performance of the Services:
- Skill and Care: The Agency warrants that it shall perform the Services with reasonable skill, care, and diligence, in accordance with generally accepted professional standards prevailing in the software development industry at the time of performance.
- Authority: The Agency warrants that it has full legal authority to enter into these Terms and to perform the Services, and that doing so does not conflict with any existing contractual obligation or applicable law binding upon the Agency.
- Original Work: The Agency warrants that, to the best of its knowledge at the time of delivery, the Deliverables produced by the Agency shall be original works or shall incorporate third-party components for which the Agency has obtained appropriate rights or licenses, and shall not knowingly infringe the intellectual property rights of any third party. This warranty does not extend to Client-provided materials, open-source components, or Third-Party Services incorporated at the Client's direction.
- Compliance with Laws: The Agency warrants that it shall perform the Services in compliance with all applicable laws and regulations governing its operations, including employment law, data protection obligations applicable to the Agency as a data processor, and professional conduct standards.
- No Malicious Code: The Agency warrants that, to the best of its knowledge and having taken reasonable precautions, the Deliverables shall not contain any intentionally introduced malicious code, backdoors, or undisclosed mechanisms designed to disrupt, damage, or gain unauthorized access to the Client's systems or data.
These warranties are personal to the Client and may not be transferred or assigned to any third party without the Agency's prior written consent. They apply solely to Deliverables in the form delivered by the Agency and shall not apply where the Deliverable has been modified, altered, or interfered with by the Client or any third party after delivery.
11.2 Service Warranty Disclaimer
To the maximum extent permitted by applicable law, and except as expressly set out in Section 11.1 or in a separate written agreement between the parties:
- The Services and Deliverables are provided without warranties of any kind, whether express, implied, statutory, or otherwise, including but not limited to implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, or quiet enjoyment.
- The Agency does not warrant that the Deliverables will be entirely free from errors, defects, or bugs following delivery and acceptance, or that their operation will be uninterrupted, fully secure, or compatible with all systems, browsers, devices, or environments not expressly specified in the applicable SOW.
- The Agency does not warrant that any security measures implemented in connection with the Deliverables will be impenetrable or that the Deliverables will be immune from cyberattacks, unauthorized access, or data breaches, particularly where such vulnerabilities arise from Third-Party Services, Client-managed infrastructure, or factors outside the Agency's reasonable control.
- Temporary bugs, performance issues, minor errors, or brief interruptions occurring after delivery and acceptance do not constitute a breach of warranty unless they rise to the level of a material Defect as defined in Section 1, or unless a separate maintenance or support agreement expressly provides otherwise.
- The Agency does not warrant that the Deliverables will remain compliant with applicable laws, regulations, or platform requirements following delivery, where such requirements change after the date of acceptance. The Client is responsible for ensuring ongoing compliance in its production environment.
- The Agency expressly disclaims any warranty in relation to the accuracy, completeness, or fitness for purpose of outputs generated by third-party AI or machine learning services integrated into the Deliverables, as further described in Section 9.8.
Nothing in this Section 11.2 shall limit or exclude any warranty that cannot be lawfully disclaimed under applicable mandatory consumer protection or commercial law in the relevant jurisdiction.
11.3 "As Is" Basis
Except where a separate maintenance or support agreement is in place, and following the Client's formal or deemed acceptance of a Deliverable in accordance with Section 7:
- All Deliverables are provided on an "as is" and "as available" basis from the date of acceptance, without any ongoing warranty as to their performance, security, compatibility, or continued fitness for the Client's evolving purposes.
- The Agency shall have no obligation to update, patch, monitor, or maintain any Deliverable following acceptance, unless such obligations are expressly provided for in a separate written maintenance or support agreement.
- The Client assumes full responsibility for the ongoing operation, security, maintenance, and regulatory compliance of the Deliverables within its production environment following acceptance.
- Where the Client or a third party modifies, extends, or integrates the Deliverables after acceptance without the Agency's involvement, the "as is" disclaimer extends to all such modifications, and the Agency shall not be responsible for any resulting Defects, incompatibilities, or degradation in performance.
- The Client acknowledges that software systems are inherently complex and that the discovery of minor issues or imperfections following acceptance is a normal incident of software delivery, and does not in itself constitute a breach of any obligation by the Agency.
11.4 No Business Outcome Guarantees
The Agency provides technical and professional services and does not make any representation, warranty, or guarantee regarding the commercial, strategic, or operational outcomes that the Client may achieve through its use of the Services or Deliverables. Without limitation, the Agency expressly disclaims any guarantee of:
- Revenue generation, profitability, return on investment, or financial performance attributable to the Deliverables.
- Website traffic, user acquisition, audience growth, engagement metrics, or user retention.
- Conversion rates, lead generation, sales performance, or marketing effectiveness.
- Search engine rankings, organic visibility, domain authority, or any other SEO-related metric.
- App store rankings, download volumes, or platform-specific performance metrics.
- User satisfaction, product adoption, or market reception of the Deliverables.
- Regulatory approval, certification, or compliance outcomes dependent on the actions of third parties or governmental authorities.
- Competitive advantage or market differentiation attributable to the use of the Deliverables.
All strategic, commercial, and operational outcomes remain entirely within the Client's sphere of responsibility. The Agency's obligation is to deliver technically sound Deliverables that conform to the agreed specifications, not to ensure that such Deliverables achieve any particular business result. The Client acknowledges that the success of any digital product or platform depends on numerous factors beyond the Agency's control, including but not limited to market conditions, user behavior, competitive dynamics, operational execution, and the Client's own business decisions.
Where the Agency provides strategic recommendations, technical opinions, or consultative input in the course of performing the Services, such input is provided in good faith as professional guidance only and does not constitute a guarantee of any outcome. The Client retains sole responsibility for all business decisions made in reliance on such guidance.
11.5 Third-Party Service Disclaimer
To the maximum extent permitted by applicable law, the Agency makes no warranty of any kind in relation to any Third-Party Service, whether or not such service was recommended, selected, integrated, or configured by the Agency. This disclaimer includes, without limitation:
- No warranty as to the availability, uptime, performance, or reliability of any third-party platform, API, infrastructure provider, or software component.
- No warranty as to the security, data integrity, or regulatory compliance posture of any Third-Party Service.
- No warranty as to the continued availability, pricing, or terms of any Third-Party Service following delivery of the Deliverables.
- No warranty as to the accuracy, completeness, or legality of content, data, or outputs provided by Third-Party Services integrated into the Deliverables.
The Client's use of Third-Party Services is entirely at its own risk and subject to the terms and disclaimers of the relevant third-party providers. The Agency's sole obligation in respect of Third-Party Service issues is as set out in Section 9.
11.6 Client Warranty
The Client makes the following warranties to the Agency, on a continuing basis throughout the term of the engagement:
- Authority: The Client has full legal authority and capacity to enter into these Terms and the applicable agreement, and the individual accepting these Terms on behalf of the Client has the authority to bind the Client to these obligations.
- Accuracy of Information: All information, materials, requirements, and instructions provided by the Client to the Agency are, to the best of the Client's knowledge, accurate, complete, and sufficient to allow the Agency to perform the Services as agreed.
- Legal Compliance of Materials: All Client-provided materials, data, content, and assets are lawfully owned or licensed by the Client and their use by the Agency in the performance of the Services does not infringe the intellectual property rights or other legal rights of any third party, as further warranted under Section 6.4.
- No Prohibited Use: The Client shall not use the Services, Deliverables, or any SaaS Products for any purpose that is unlawful, fraudulent, abusive, or in violation of these Terms or any applicable law or regulation.
- Regulatory Compliance: The Client has obtained or will obtain all necessary licenses, permits, registrations, and regulatory approvals required for its use and deployment of the Deliverables in its intended markets and jurisdictions.
Any breach of the Client's warranties under this clause shall entitle the Agency to suspend or terminate the engagement in accordance with Section 13, and shall trigger the Client's indemnification obligations under Section 12 to the extent applicable.
11.7 Mutual Disclaimer of Consequential Loss
Subject to Section 12 (Limitation of Liability) and to the extent permitted by applicable law, neither party shall be liable to the other for any indirect, incidental, special, consequential, punitive, or exemplary losses arising out of or in connection with these Terms or any engagement hereunder, including but not limited to loss of profits, loss of revenue, loss of anticipated savings, loss of business opportunity, loss of goodwill, loss of data, or reputational damage, even if the relevant party has been advised of the possibility of such losses.
This mutual disclaimer reflects a fundamental allocation of risk between the parties and is an essential basis upon which the Agency offers its Services at the fees stated. The Client acknowledges that the pricing of the Services reflects this allocation.
11.8 Maintenance Exceptions
Where a separate maintenance or support agreement has been executed between the parties:
- The service levels, warranty obligations, response times, remediation commitments, and support scope applicable to the Deliverables following acceptance shall be governed exclusively by that separate agreement.
- In the event of any conflict between the provisions of this Section 11 and the terms of a separately executed maintenance or support agreement, the maintenance or support agreement shall prevail to the extent of the conflict.
- The existence of a maintenance or support agreement shall not expand the Agency's warranty obligations under Section 11.1 beyond what is expressly stated in that agreement, nor shall it alter the disclaimer of business outcome guarantees under Section 11.4.
- Where a maintenance or support agreement expires or is terminated, the provisions of this Section 11 shall apply in full from the date of such expiration or termination, and all Deliverables shall revert to being provided on an "as is" basis under Section 11.3.
11.9 Acknowledgment
The Client acknowledges that:
- The disclaimers and limitations set out in this Section 11 are reasonable and reflect the commercial basis upon which the Agency offers its Services, including the pricing applied.
- The Client has had a reasonable opportunity to review and obtain independent legal advice in relation to these Terms before entering into any agreement with the Agency.
- In entering into any agreement with the Agency, the Client has not relied upon any representation, warranty, or assurance made by or on behalf of the Agency that is not expressly set out in these Terms or in the applicable written agreement.
- Nothing in these Terms excludes or limits any liability that cannot be excluded or limited by applicable mandatory law, including liability for death or personal injury caused by negligence, fraud, or fraudulent misrepresentation.
12. Limitation of Liability
12.1 Liability Cap
To the maximum extent permitted by applicable law, the total aggregate liability of the Agency to the Client arising out of or in connection with the Services, Deliverables, SaaS Products, or these Terms — whether arising in contract, tort (including negligence), breach of statutory duty, misrepresentation, or otherwise — shall not exceed the total amount of fees actually paid by the Client to the Agency in the six (6) month period immediately preceding the date on which the event or circumstance giving rise to the claim first occurred, unless otherwise expressly agreed in writing in the applicable SOW.
- Where the engagement has been in effect for less than six (6) months at the time the claim arises, the liability cap shall be calculated based on the total fees actually paid by the Client to the Agency from the commencement of the engagement to the date of the relevant event.
- Where multiple claims arise from the same or related events or circumstances, they shall be treated as a single claim for the purpose of applying this liability cap, and the cap shall apply to the aggregate liability arising from all such related claims.
- Where fees are payable on a recurring basis (such as under a retainer or SaaS subscription), only fees actually received and cleared by the Agency during the relevant six (6) month calculation period shall be counted toward the cap. Amounts invoiced but not yet paid shall not be included.
- The parties acknowledge that the liability cap reflects a reasonable and negotiated allocation of commercial risk between them, and that the Agency's pricing for the Services is calibrated in reliance on this cap. The Client confirms that it has had the opportunity to obtain insurance or other financial protection against losses in excess of this cap.
- Where a separate SOW specifies a different liability cap applicable to a specific Project or engagement, the cap stated in the SOW shall prevail over this clause in relation to that Project to the extent of any conflict.
12.2 Exclusion of Indirect and Consequential Damages
To the maximum extent permitted by applicable law, neither party shall be liable to the other for any indirect, incidental, consequential, special, exemplary, or punitive damages arising out of or in connection with the Services, Deliverables, SaaS Products, or these Terms, regardless of the form of action and whether such liability arises in contract, tort (including negligence), breach of statutory duty, or otherwise, and even if the relevant party has been advised of, or ought reasonably to have foreseen, the possibility of such damages.
Excluded categories of loss include, without limitation:
- Loss of actual or anticipated profit or revenue, including lost margin on contracts with third parties.
- Loss of business opportunity, market share, or competitive advantage.
- Loss, corruption, or degradation of data, including costs of data recovery or reconstruction.
- Loss of goodwill, reputation, or brand value.
- Business interruption, downtime losses, or loss of productivity.
- Loss of anticipated savings or wasted expenditure.
- Third-party claims brought against the Client arising from the Client's use or deployment of the Deliverables, except to the extent such claims arise from the Agency's direct breach of warranty under Section 11.1.
- Losses arising from the Client's reliance on any estimate, projection, recommendation, or consultative input provided by the Agency in the course of the engagement.
This exclusion applies irrespective of whether the loss was foreseeable, whether it arose in the ordinary course of events, or whether the Agency had been specifically informed of the circumstances that led to the loss.
12.3 Specific Liability Exclusions
Without prejudice to the generality of Sections 12.1 and 12.2, and to the maximum extent permitted by applicable law, the Agency shall not be liable for:
- Any loss or damage arising from the Client's use of the Deliverables in a manner inconsistent with the Agency's documentation, instructions, or agreed specifications.
- Any loss or damage arising from modifications made to the Deliverables by the Client or any third party after delivery and acceptance, without the Agency's involvement or written consent.
- Any loss or damage arising from the failure, unavailability, or changed terms of any Third-Party Service, including but not limited to cloud infrastructure providers, API providers, payment processors, or open-source dependencies.
- Any loss or damage arising from the Client's failure to maintain, update, or secure its own infrastructure, systems, or third-party service accounts following delivery of the Deliverables.
- Any loss or damage arising from security vulnerabilities, data breaches, or cyberattacks that exploit weaknesses introduced after delivery, or that originate in the Client's environment, third-party services, or factors outside the Agency's reasonable control.
- Any loss or damage arising from the Client's failure to implement recommendations made by the Agency in connection with security, performance, infrastructure, or compliance, where such failure contributed to the loss.
- Any loss or damage arising from the Client's decision to proceed with deployment, go-live, or use of Deliverables against the Agency's documented advice or warnings.
- Any loss or damage arising from the Client's reliance on AI-generated outputs integrated into the Deliverables, as further described in Section 9.8.
- Any loss or damage arising from Force Majeure Events as defined in Section 1 and further described in Section 8.4.
12.4 Exceptions to Liability Limitations
Nothing in this Section 12 or elsewhere in these Terms shall operate to exclude or limit either party's liability for:
- Death or personal injury caused by that party's negligence or the negligence of its employees, contractors, or agents.
- Fraud or fraudulent misrepresentation.
- Any other category of liability that cannot lawfully be excluded or limited under applicable mandatory law in the relevant jurisdiction, including any applicable consumer protection legislation where relevant.
- The Client's obligation to pay all fees, charges, and expenses due and payable to the Agency under these Terms and any applicable SOW.
- Breach of confidentiality obligations under Section 10, where such breach causes demonstrable harm to the Disclosing Party.
- Infringement of intellectual property rights, where the infringement is intentional or the result of willful misconduct.
Where applicable law prohibits the exclusion or limitation of liability for a specific category of loss or damage, the Agency's liability for that category shall be limited to the minimum extent permitted by law.
12.5 Mitigation
Each party shall take all reasonable steps to mitigate any loss or damage it suffers or is likely to suffer as a result of the other party's breach of these Terms or any applicable agreement. Failure to mitigate shall be taken into account in assessing any claim for loss or damage, and the non-mitigating party's recoverable losses may be reduced to the extent that such losses could have been avoided or reduced through reasonable mitigation efforts.
12.6 Time Limitation on Claims
Any claim by the Client against the Agency arising out of or in connection with the Services, Deliverables, or these Terms must be notified to the Agency in writing, with reasonable particularity, within twelve (12) months of the date on which the Client became aware, or ought reasonably to have become aware, of the circumstances giving rise to the claim. Claims notified after this period shall be time-barred, and the Agency shall have no liability in respect of such claims, to the extent permitted by applicable law.
12.7 Allocation of Risk
The parties acknowledge and agree that:
- The limitations and exclusions of liability set out in this Section 12 are a fundamental and essential part of the commercial basis upon which the Agency provides its Services.
- The Agency's pricing reflects the allocation of risk embodied in these limitations, and the Agency would not have entered into the engagement on the same commercial terms without them.
- Each party has had a reasonable opportunity to review these Terms, seek independent legal advice, and negotiate alternative risk allocation arrangements if desired.
- The limitations set out in this Section 12 are reasonable in all the circumstances and represent a fair and proportionate allocation of risk between commercial parties of equivalent standing.
13. Termination
13.1 Termination by Mutual Agreement
The parties may terminate any engagement at any time by mutual written agreement, on such terms — including as to payment, delivery of work in progress, and transition arrangements — as they may agree in writing at the time of termination. A mutual termination agreement shall be documented in writing and signed by authorized representatives of both parties before it takes effect.
13.2 Termination for Convenience
Either party may terminate an engagement for convenience upon the written notice period specified in the applicable SOW. Where no notice period is specified:
- The Client may terminate for convenience upon no less than thirty (30) calendar days' prior written notice to the Agency.
- The Agency may terminate for convenience upon no less than thirty (30) calendar days' prior written notice to the Client, provided that the Agency shall use commercially reasonable efforts to minimize disruption to the Client and to complete or hand over work in progress in an orderly manner during the notice period.
Upon termination for convenience by the Client, the following consequences shall apply:
- The Client shall pay for all Services performed, resources committed, and costs incurred by the Agency up to and including the effective date of termination, including any non-cancellable third-party commitments entered into by the Agency in connection with the Project.
- Where the applicable engagement is on a fixed-price or milestone basis, the Client shall pay for all completed milestones in full, and for partially completed milestones on a pro-rata or time-and-materials basis as reasonably assessed by the Agency.
- A termination fee may apply where specified in the applicable SOW. Where no termination fee is specified, the Client's payment obligations shall be limited to amounts due for work performed and costs committed as of the termination date.
- The Agency shall not be obligated to refund any amounts already paid for work performed, resources allocated, or costs committed prior to the termination date.
Upon termination for convenience by the Agency, the Agency shall:
- Provide the Client with all completed Deliverables and work in progress in their then-current state, subject to receipt of all amounts due and payable as of the termination date.
- Use commercially reasonable efforts to ensure an orderly transition and to minimize disruption to the Client's operations.
- Not be liable to the Client for any loss, cost, or damage arising from a termination for convenience exercised in good faith and in accordance with this clause.
13.3 Termination for Material Breach
Either party may terminate an engagement immediately upon written notice to the other party in the event of a material breach of these Terms or the applicable agreement, subject to the following cure provisions:
- Where the breach is capable of remedy, the non-breaching party shall first provide written notice to the breaching party specifying the nature of the breach in reasonable detail and requiring it to be remedied within fourteen (14) calendar days of the date of such notice (or such longer period as the non-breaching party may specify in writing).
- Where the breach is not remedied within the cure period, the non-breaching party may terminate the engagement with immediate effect by providing a further written notice of termination.
- Where the breach is not capable of remedy — including but not limited to material breach of confidentiality, willful misrepresentation, unauthorized use of intellectual property, or deliberate violation of applicable law — the non-breaching party may terminate with immediate effect without any prior cure notice.
Examples of material breach include, without limitation:
- The Client's failure to pay any undisputed invoice within thirty (30) calendar days of the due date.
- Either party's material breach of its confidentiality obligations under Section 10.
- The Client's unauthorized use, reproduction, or distribution of Deliverables in which intellectual property rights have not yet transferred.
- The Agency's persistent and demonstrable failure to deliver Services in accordance with agreed specifications, where such failure is not remediated within a reasonable timeframe following notice.
- Either party's violation of applicable law in connection with the engagement.
Upon termination for the Client's material breach, the Agency shall be entitled to: retain all fees paid to date; invoice for all work performed and costs committed up to the termination date; and pursue any additional remedies available at law or in equity, including damages for loss arising from the breach.
Upon termination for the Agency's material breach, the Client shall be entitled to: cease further payments for unperformed Services; seek a refund of fees paid for Services that were materially not delivered in accordance with the agreement; and pursue any additional remedies available at law or in equity, subject to the limitations set out in Section 12.
13.4 Termination for Insolvency
Either party may terminate an engagement immediately upon written notice if the other party:
- Becomes insolvent, is unable to pay its debts as they fall due, or suspends or threatens to suspend payment of its debts.
- Enters into voluntary or involuntary liquidation, administration, receivership, or any analogous insolvency proceeding in any jurisdiction.
- Has a receiver, liquidator, administrator, or equivalent officer appointed over its assets or any material part thereof.
- Makes a general assignment for the benefit of its creditors or enters into a formal arrangement or composition with creditors.
- Ceases or threatens to cease carrying on business in the ordinary course.
Upon termination for insolvency of the Client, the Agency shall have no obligation to deliver any further Deliverables or work in progress until all outstanding amounts have been paid or secured to the Agency's reasonable satisfaction, and shall be entitled to pursue all available legal remedies for recovery of amounts owed.
Upon termination for insolvency of the Agency, the Agency shall use reasonable efforts to deliver to the Client all completed Deliverables and work in progress in their then-current state, subject to the Client's payment of all amounts due as of the termination date.
13.5 Payment Upon Termination
Upon termination of any engagement for any reason:
- The Client shall pay all amounts due and payable as of the effective date of termination, including fees for Services performed, costs committed, expenses incurred, and any applicable termination fees, within fourteen (14) calendar days of the termination date or the Agency's final invoice, whichever is later.
- Any non-refundable expenses incurred by the Agency prior to termination — including but not limited to third-party licenses procured, infrastructure costs committed, and subcontractor fees accrued — shall be payable by the Client in full, regardless of the reason for termination.
- Where fees have been paid in advance, any overpayment relative to work actually performed as of the termination date shall be assessed by the Agency in good faith and, where confirmed, refunded or credited to the Client within thirty (30) calendar days, subject to the deduction of any amounts owed by the Client to the Agency.
- The Agency's right to receive payment for work performed and costs committed shall not be affected by the reason for termination, except where termination arises from the Agency's own material breach, in which case the Client's remedies shall be as set out in Section 13.3.
13.6 Handling of Work in Progress Upon Termination
In the event of termination during an ongoing Project:
- The Agency shall, within a reasonable period following the termination date, provide the Client with an inventory of all completed Deliverables, partially completed work, and associated materials held by the Agency in connection with the Project.
- Completed Deliverables in respect of which all associated payment obligations have been satisfied shall be delivered to the Client promptly following termination.
- Partially completed Deliverables may be handed over to the Client in their then-current state, at the Agency's discretion and subject to: full payment of all amounts due as of the termination date; and the Client's written acknowledgment that such materials are incomplete, have not been accepted, and are taken on an "as is" basis without warranty.
- The Agency is not obligated to complete any unfinished milestone, deliverable, or phase following termination, unless both parties expressly agree otherwise in writing following the termination notice.
- The Client assumes full responsibility for any use of incomplete or in-progress work product following handover, including any risks associated with deploying or relying upon work that has not been through the Agency's full quality assurance process, and the Agency shall have no liability for any consequence arising from such use.
- Where the Client requires the Agency to perform structured handover activities — including documentation, knowledge transfer sessions, or transition support — beyond the Agency's standard obligations under this clause, such activities shall be subject to separate agreement and may be charged at the Agency's applicable rates.
13.7 Transition Assistance
Where the Client requests transition assistance following termination — including handover to a replacement development partner, migration of infrastructure, or transfer of repositories and environments — the Agency shall use commercially reasonable efforts to cooperate with an orderly transition, subject to:
- All outstanding amounts owed by the Client having been paid in full prior to the commencement of transition activities.
- The scope, duration, and cost of transition assistance being agreed in writing before it commences, at the Agency's then-applicable rates.
- The Client providing reasonable advance notice of the scope of transition assistance required, and the Agency's ability to resource such activities being subject to its operational capacity at the time.
The Agency shall not be obligated to provide transition assistance beyond what is expressly agreed in writing, and shall have no liability for any delays or difficulties in transitioning to a replacement provider that are attributable to the Client's own systems, internal processes, or the capabilities of the replacement provider.
13.8 Survival
The following provisions shall survive the termination or expiration of any engagement and shall continue in full force and effect in accordance with their respective terms:
- Section 4 (Payment Terms), in respect of all amounts due and payable as of the termination date.
- Section 5 (Intellectual Property), including the conditions governing the transfer of rights and the Agency's retained rights.
- Section 10 (Confidentiality), for the duration specified in Section 10.10.
- Section 11 (Warranties and Disclaimers), to the extent applicable to Deliverables already accepted.
- Section 12 (Limitation of Liability), in respect of all claims arising from or in connection with the engagement.
- Section 13.5 (Payment Upon Termination) and Section 13.6 (Handling of Work in Progress).
- Section 14 (Indemnification), in respect of indemnification obligations arising from events occurring prior to termination.
- Any other provision that by its nature or express terms is intended to survive termination.
Termination of an engagement shall not affect any rights or obligations that have accrued prior to the effective date of termination, nor shall it limit either party's right to pursue remedies for breaches occurring before or giving rise to the termination.
14. Maintenance and Support
14.1 Separate Agreement
Maintenance and support services, where offered by the Agency, are governed by a separate service level agreement (SLA) or written support terms executed between the parties. Such terms are independent from and supplementary to any development or project delivery agreement, unless the parties expressly agree in writing that maintenance and support obligations are incorporated into the primary engagement agreement.
- Where a separate maintenance and support agreement has been executed, its terms shall take precedence over any general provisions in these Terms relating to post-delivery obligations, defect remediation, and service continuity, to the extent of any conflict.
- The absence of a maintenance and support agreement means that the Agency has no ongoing obligation to monitor, update, patch, or support any Deliverable following formal or deemed acceptance, and all Deliverables shall be provided on an "as is" basis as set out in Section 11.3.
- Where a Client requests maintenance or support services in the absence of a formal agreement, the Agency may, at its discretion, provide such services on an ad hoc basis at its then-applicable hourly rates, and any such provision shall not create an implied ongoing support obligation or entitlement on the part of the Client.
- Maintenance and support services may be offered as a standalone engagement following Project completion, or may be bundled with an active development engagement where expressly agreed in the applicable SOW.
- The Agency reserves the right to decline to offer maintenance and support services in respect of Deliverables that have been materially modified by the Client or a third party after acceptance, or where the Agency determines that the technical state of the Deliverable makes responsible ongoing support unfeasible without prior remediation work.
14.2 Scope of Support
The scope of maintenance and support services shall be defined in the applicable support agreement or SLA. Depending on the terms agreed, support services may include some or all of the following:
- Bug Fixes and Issue Resolution: Identification, diagnosis, and remediation of confirmed Defects in the Deliverables that are reported by the Client in accordance with the agreed reporting process, and that are attributable to the Agency's original work product.
- Security Patching: Application of security updates to Agency-developed components within the Deliverables in response to identified vulnerabilities, where such updates are within the scope of the agreed support tier.
- System Monitoring: Proactive or reactive monitoring of application performance, error rates, uptime, and key infrastructure metrics, as specified in the applicable SLA.
- Minor Updates and Improvements: Small enhancements, configuration changes, content updates, or feature adjustments that fall within the definition of Minor Changes under Section 7.3 and are within the agreed support scope and capacity.
- Dependency Management: Routine updates to third-party libraries, frameworks, and package dependencies within the Deliverables to maintain compatibility and security posture, where included in the agreed support scope.
- Performance Optimization: Identification and implementation of performance improvements to address degradation in application speed, resource utilization, or scalability, within the agreed scope.
- Technical Assistance and Advisory Support: Provision of technical guidance, consultation, and advisory input to the Client's internal teams in connection with the operation, administration, or extension of the Deliverables.
- Infrastructure Management: Management, configuration, and maintenance of cloud infrastructure, hosting environments, and deployment pipelines associated with the Deliverables, where included in the agreed support scope.
- Backup and Recovery: Implementation and verification of backup procedures and, where applicable, support for data recovery operations in the event of data loss or system failure, as specified in the SLA.
The precise scope applicable to each Client shall be as set out in the executed support agreement or SLA, and the Agency shall have no obligation to perform support activities beyond that agreed scope without a written amendment or Change Request.
14.3 Support Tiers and Prioritization
Where a tiered support structure is offered, support requests shall be categorized by severity in accordance with the definitions set out in the applicable SLA. Indicative severity levels may include:
- Critical (P1): Complete service outage, data loss, or a failure that renders the Deliverable wholly inoperable or causes material business impact to the Client. Requires immediate response.
- High (P2): Significant functionality impairment affecting a core feature or a substantial portion of users, with no viable workaround. Requires urgent response.
- Medium (P3): Partial functionality impairment or degraded performance affecting a non-critical feature or a limited subset of users, where a workaround is available. Requires timely response.
- Low (P4): Minor issues, cosmetic defects, informational queries, or requests for guidance that have minimal impact on the Client's operations. Addressed in the normal course of support operations.
The specific response time targets, resolution timeframes, and escalation procedures applicable to each severity level shall be defined in the applicable SLA. Where no SLA is in place, the Agency shall use commercially reasonable efforts to address support requests in order of their assessed severity and impact, but no specific response or resolution timeframes shall be guaranteed.
14.4 Response Times and SLAs
Where a formal SLA is in place:
- Response time targets, resolution objectives, and severity classifications shall be as specified in that SLA and shall govern the Agency's performance obligations in respect of support services.
- Service level obligations apply exclusively during the active support term and within the agreed coverage hours specified in the SLA. Support requests submitted outside of agreed coverage hours shall be logged and addressed at the commencement of the next coverage period, unless the applicable SLA expressly provides for out-of-hours emergency support.
- Response time targets represent the Agency's commitment to acknowledge and begin investigation of a reported issue within the stated timeframe, and do not constitute a guarantee of resolution within that period. Resolution timeframes shall be governed by the applicable SLA.
- Service level credits or remedies for failure to meet SLA targets, if any, shall be as specified in the applicable support agreement and shall represent the Client's sole and exclusive remedy for service level failures, subject to Section 12.
- The Agency shall not be in breach of any SLA target where a failure to meet the target is attributable to: the Client's failure to provide timely access, information, or approvals required to investigate or resolve the issue; factors outside the Agency's reasonable control, including Third-Party Service failures or Force Majeure Events; or the issue being outside the agreed support scope.
14.5 Support Request Process
Unless otherwise specified in the applicable support agreement, support requests shall be submitted in accordance with the following process:
- All support requests must be submitted through the designated support channel specified in the applicable SLA (such as a ticketing system, dedicated support email address, or support portal).
- Each support request must include: a clear description of the issue; the severity level as assessed by the Client; steps to reproduce the issue where applicable; the environment in which the issue was observed; and any relevant logs, screenshots, or error messages.
- The Agency shall acknowledge receipt of a support request within the timeframe specified in the applicable SLA, and shall provide an initial assessment of severity and expected next steps.
- Support requests submitted by individuals not designated as authorized contacts under the applicable support agreement may not be actioned until verified by an authorized representative of the Client.
- The Client shall cooperate with the Agency's reasonable requests for additional information, access, or testing assistance required to investigate and resolve reported issues in a timely manner.
14.6 Exclusions from Support
Unless otherwise expressly agreed in writing, maintenance and support services do not include and the Agency shall have no obligation to provide:
- Development of new features, modules, or functionality not present in the accepted Deliverables.
- Major system redesign, architectural restructuring, or platform migrations.
- Support for issues caused by Third-Party Service failures, outages, deprecations, or changes in third-party APIs or platforms, beyond reasonable investigation and advisory assistance.
- Remediation of issues caused by unauthorized modifications, patches, or integrations applied to the Deliverables by the Client or any third party without the Agency's prior written consent.
- Support for Deliverables deployed on infrastructure or environments that do not meet the specifications agreed at the time of delivery, or that have been materially altered after delivery.
- Recovery from data loss or corruption caused by the Client's failure to maintain adequate backups, where backup management was not included in the agreed support scope.
- Training, onboarding, or user education beyond what is expressly included in the support scope.
- Support for issues arising from the Client's failure to apply recommended updates, security patches, or configuration changes within a reasonable timeframe after being notified by the Agency.
- Legal, regulatory, or compliance advisory services in connection with the Deliverables.
- Any activity that would constitute a Major Change under Section 7.3, which shall be separately scoped and engaged as a Change Request.
14.7 Availability and Uptime Commitments
Any uptime guarantee, availability commitment, or service continuity obligation in relation to the Deliverables or infrastructure managed by the Agency shall apply only where expressly stated in a signed SLA and subject to the following conditions:
- Uptime calculations shall be measured over the calendar month in which the relevant period falls, using the methodology defined in the applicable SLA. Scheduled maintenance windows, agreed downtime, and outages attributable to Third-Party Services or Client-managed infrastructure shall be excluded from uptime calculations.
- Where uptime commitments are not met in a given measurement period, the Client's remedy shall be limited to the service credits specified in the applicable SLA, if any, subject to the overall liability limitations in Section 12.
- Uptime commitments apply exclusively to infrastructure and environments under the Agency's direct management and control, and do not extend to the Client's own infrastructure, third-party hosting environments, CDN providers, or services outside the Agency's operational scope.
- Scheduled maintenance required to apply security patches, perform system upgrades, or carry out infrastructure work shall be conducted during agreed maintenance windows defined in the SLA, with reasonable advance notice provided to the Client. Emergency maintenance may be conducted outside of scheduled windows where necessary to address critical security vulnerabilities or prevent service disruption, with notification provided to the Client as soon as reasonably practicable.
- Where no uptime commitment is expressly stated in a signed SLA, the Agency makes no guarantee of availability or continuity of access to the Deliverables, and Section 11.2 shall apply.
14.8 End of Support
Where the Agency decides to discontinue maintenance and support services for a specific Deliverable, platform version, or technology stack:
- The Agency shall provide the Client with no less than ninety (90) calendar days' prior written notice of the end-of-support date, unless the discontinuation is necessitated by a third-party provider's own end-of-life announcement, in which case the Agency shall provide as much notice as reasonably practicable.
- Following the end-of-support date, the Agency shall have no further obligation to provide bug fixes, security patches, or technical assistance in relation to the affected Deliverable or version.
- Where continued support is required beyond the end-of-support date, the parties may negotiate a separate extended support arrangement, which may be subject to different pricing and scope terms.
15. Data Protection and Privacy
15.1 Compliance with Applicable Data Protection Laws
Each party shall comply with all applicable data protection and privacy laws and regulations in connection with the performance of the Services and the processing of Personal Data arising therefrom. Depending on the jurisdiction and nature of the engagement, applicable legislation may include:
- The EU General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679) and any implementing legislation in EU member states.
- The UK General Data Protection Regulation (UK GDPR) and the UK Data Protection Act 2018, where applicable to the Client or to data subjects located in the United Kingdom.
- The California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), where applicable to the Client's operations or to data subjects located in California.
- The Georgian Law on Personal Data Protection, to the extent applicable to the Agency's operations in Georgia.
- Any other national, regional, or sector-specific data protection or privacy legislation applicable to the parties based on their jurisdiction, industry, or the location of the relevant data subjects.
Each party's data protection compliance obligations shall extend only to the extent required by applicable law based on its role in the processing of Personal Data, the nature of the Services, and the jurisdictions in which it operates or in which the relevant data subjects are located. The Agency does not assume compliance obligations under laws that are not applicable to its operations or processing activities.
15.2 Roles: Controller and Processor
The respective roles of the parties in relation to the processing of Personal Data shall be determined by the nature of the engagement and the applicable data protection framework, as follows:
- Client as Data Controller: In the majority of engagements, the Client shall act as the Data Controller in respect of Personal Data that it provides to the Agency or that is collected, stored, or processed by the Deliverables on the Client's behalf. As Data Controller, the Client is responsible for ensuring that it has a lawful basis for processing such Personal Data, that data subjects have been provided with appropriate privacy notices, and that the Client's instructions to the Agency comply with applicable data protection law.
- Agency as Data Processor: Where the Agency processes Personal Data on behalf of the Client in the course of performing the Services, the Agency shall act as a Data Processor. In this capacity, the Agency shall process Personal Data only in accordance with the Client's documented instructions, except where required to do so by applicable law, in which case the Agency shall inform the Client of that legal requirement before processing unless prohibited from doing so by law.
- Agency as Independent Data Controller: In certain circumstances — including where the Agency processes operational data in connection with its SaaS Products, where it processes data for its own billing, compliance, or security purposes, or where it processes aggregated or anonymized usage data — the Agency may act as an independent Data Controller in respect of such data. The Agency's processing of data in its capacity as independent Data Controller shall be governed by its Privacy Policy, as published and updated from time to time.
- Joint Controllers: Where both parties jointly determine the purposes and means of processing Personal Data in connection with the Services, they may be considered Joint Controllers under applicable law. Any joint controller arrangement shall be documented in a separate written agreement setting out each party's respective responsibilities, unless the parties agree that one party's Controller obligations encompass the relevant processing.
The applicable roles shall be specified in the relevant engagement agreement or in a separate Data Processing Addendum (DPA), where required by applicable law or requested by either party.
15.3 Data Processing Addendum
Where the Agency processes Personal Data on behalf of the Client as a Data Processor, the parties shall, upon the Client's request or where required by applicable law, execute a Data Processing Addendum (DPA) that sets out:
- The subject matter, duration, nature, and purpose of the processing.
- The type of Personal Data being processed and the categories of data subjects concerned.
- The obligations and rights of the Client as Data Controller.
- The Agency's obligations as Data Processor, including obligations regarding subprocessors, international data transfers, data subject rights, security measures, and breach notification.
- The applicable legal basis for any international transfer of Personal Data outside the European Economic Area (EEA), United Kingdom, or other relevant jurisdiction.
Where a DPA has been executed between the parties, it shall form part of and be incorporated into the applicable agreement, and shall take precedence over any conflicting data protection provisions in these Terms to the extent of the conflict.
Where no DPA has been executed and applicable law requires one, the Client is responsible for ensuring that one is put in place before the Agency commences processing Personal Data on the Client's behalf. The Agency shall not be liable for any regulatory consequence arising from the Client's failure to initiate or execute a required DPA in a timely manner.
15.4 Agency Obligations as Data Processor
Where acting as a Data Processor, the Agency shall:
- Process Personal Data only on the basis of the Client's documented instructions, and shall promptly notify the Client if it believes any instruction infringes applicable data protection law.
- Ensure that all personnel authorized to process Personal Data are subject to appropriate confidentiality obligations.
- Implement and maintain appropriate technical and organizational measures to protect Personal Data against unauthorized or unlawful processing, accidental loss, destruction, damage, or disclosure, commensurate with the risks presented by the processing and the nature of the data.
- Not engage any subprocessor to process Personal Data on the Client's behalf without the Client's prior written authorization, either specific or general. Where general authorization is provided, the Agency shall notify the Client of any intended changes to its subprocessor arrangements and provide the Client with a reasonable opportunity to object.
- Assist the Client, insofar as reasonably practicable and taking into account the nature of the processing, in fulfilling its obligations to respond to data subject requests under applicable data protection law, including requests for access, rectification, erasure, restriction, portability, and objection.
- Notify the Client without undue delay, and in any event within seventy-two (72) hours where reasonably practicable, upon becoming aware of a Personal Data breach affecting Personal Data processed on the Client's behalf, providing sufficient information to allow the Client to meet its own notification obligations under applicable law.
- Provide the Client with all information reasonably necessary to demonstrate compliance with the Agency's obligations under this Section 15, and cooperate with audits or inspections conducted by the Client or a mandated auditor, subject to reasonable advance notice, confidentiality protections, and agreement on scope and cost.
- Upon termination or expiration of the engagement, at the Client's election, delete or return all Personal Data processed on the Client's behalf, and delete existing copies unless applicable law requires otherwise.
15.5 Data Handling and Security Measures
The Agency shall implement and maintain reasonable and appropriate technical and organizational measures to protect Personal Data and other Client data processed in connection with the Services. Such measures may include, without limitation:
- Encryption of Personal Data in transit using industry-standard protocols (such as TLS) and, where appropriate, encryption of Personal Data at rest.
- Implementation of access control mechanisms ensuring that access to Personal Data is restricted to authorized personnel on a need-to-know basis, in accordance with the principle of least privilege.
- Use of reputable, enterprise-grade infrastructure and cloud service providers with appropriate security certifications and data protection commitments.
- Maintenance of internal data handling policies, security awareness training for relevant personnel, and incident response procedures.
- Regular review of security measures to address emerging threats and vulnerabilities, where within the Agency's reasonable operational capacity.
- Logical separation of Client data from data belonging to other clients of the Agency, where technically feasible and appropriate given the engagement structure.
The Agency does not warrant that its security measures will be impenetrable or that all security incidents will be prevented. The Agency's obligation is to implement measures that are reasonable and appropriate given the nature of the data, the risks involved, and the state of available security technology and practices at the relevant time.
15.6 International Data Transfers
Where Personal Data is transferred from the European Economic Area (EEA), the United Kingdom, or any other jurisdiction with data transfer restrictions to a third country that does not provide an equivalent level of data protection:
- Such transfers shall be subject to appropriate safeguards as required by applicable data protection law, which may include Standard Contractual Clauses (SCCs) approved by the relevant supervisory authority, binding corporate rules, an adequacy decision, or another recognized transfer mechanism.
- The Agency shall notify the Client of any proposed international transfer of Personal Data that falls within the scope of this clause, and shall cooperate with the Client in implementing the appropriate transfer mechanism before the transfer takes place.
- The Client is responsible for ensuring that its own transfer of Personal Data to the Agency complies with applicable data transfer obligations, including executing any required transfer agreements.
- Where the applicable legal framework for international data transfers changes materially — including the invalidation or amendment of previously recognized transfer mechanisms — the parties shall cooperate in good faith to implement an alternative compliant transfer mechanism as soon as reasonably practicable.
15.7 Data Retention and Deletion
- The Agency shall retain Personal Data and Client data only for as long as is necessary for the performance of the Services, or as required by applicable law, regulatory obligation, or legitimate operational necessity (such as audit, dispute resolution, or backup retention requirements).
- Upon termination or expiration of the engagement, the Agency shall, at the Client's written request, delete or return all Client data and Personal Data in its possession or control within a reasonable timeframe, subject to any legal or regulatory retention obligations that prevent immediate deletion.
- Where the Agency is required by applicable law to retain certain data beyond the end of the engagement, it shall notify the Client of the categories of data retained, the legal basis for retention, and the applicable retention period.
- The Agency is not responsible for the long-term archival, backup, or preservation of Client data beyond what is expressly included in the applicable maintenance and support agreement or DPA.
- The Client is solely responsible for ensuring that it retains its own copies of all data, Deliverables, and associated materials prior to the termination of any engagement, and the Agency shall have no liability for any data loss arising from the Client's failure to do so.
- Automated backup systems may retain copies of data for a defined rolling period as part of the Agency's standard disaster recovery procedures. Such retained copies shall be subject to the confidentiality and security obligations of these Terms and shall be purged in accordance with the Agency's standard retention schedule.
15.8 Data Subject Rights
Where the Agency receives a request directly from a data subject in respect of Personal Data processed on the Client's behalf, the Agency shall:
- Promptly redirect the data subject to the Client as the relevant Data Controller, unless the Agency is independently obligated to respond under applicable law.
- Notify the Client of the request without undue delay, so that the Client may fulfill its own obligations to the data subject within the applicable statutory timeframe.
- Provide reasonable assistance to the Client in responding to data subject requests, to the extent that such assistance is within the Agency's technical capability and does not require disproportionate effort, and subject to any agreed additional fees for such assistance.
The Client is solely responsible for ensuring that its own policies, procedures, and technical infrastructure enable it to fulfill data subject rights obligations under applicable law, including rights of access, rectification, erasure, restriction, objection, and data portability.
15.9 Privacy by Design
Where the development of Deliverables involves the collection, storage, or processing of Personal Data, the Agency shall, where technically feasible and within the agreed scope:
- Apply data minimization principles in the design and architecture of relevant components, collecting and processing only the minimum Personal Data necessary for the specified purpose.
- Implement reasonable privacy-protective defaults in the design of relevant features, where this is consistent with the Client's stated requirements.
- Notify the Client during the design phase if the proposed architecture or functionality raises material data protection considerations that the Agency believes should be addressed before implementation.
The Agency's obligations under this clause are advisory and design-oriented in nature and do not extend to providing legal compliance advice, conducting formal privacy impact assessments, or guaranteeing that the Deliverables will satisfy all applicable data protection requirements applicable to the Client's specific business and regulatory context. Such assessments remain the Client's responsibility.
15.10 Agency Privacy Policy
The Agency's collection and use of personal data relating to the Client's authorized users and representatives — including contact details, account information, and communication records — in connection with the administration of the engagement shall be governed by the Agency's Privacy Policy, available at the Agency's website or upon written request.
The Client is responsible for informing its own personnel, authorized users, and representatives of the Agency's Privacy Policy to the extent required by applicable data protection law.
16. Security
16.1 Security Measures
The Agency applies commercially reasonable security practices and standards in the performance of its Services and in the development of Deliverables. Such measures may include, without limitation:
- Secure Development Practices: Application of recognized secure coding standards and guidelines — including but not limited to OWASP Top Ten awareness, input validation, output encoding, and protection against common vulnerability classes such as SQL injection, cross-site scripting (XSS), and cross-site request forgery (CSRF) — in the development of custom Deliverables, where applicable to the technology stack and within the agreed scope.
- Encryption in Transit: Use of industry-standard encryption protocols (such as TLS 1.2 or higher) for the transmission of sensitive data between system components, where technically applicable and within the agreed scope of the Deliverables.
- Encryption at Rest: Application of appropriate encryption mechanisms for the storage of sensitive or Personal Data at rest, where specified in the applicable SOW or required by applicable data protection obligations.
- Access Control and Permission Management: Implementation of role-based access control (RBAC), principle of least privilege, and appropriate authentication mechanisms within the Deliverables, where applicable to the agreed architecture and scope.
- Dependency Management: Use of reasonably current and maintained third-party libraries and frameworks, and application of available security patches to Agency-managed dependencies during the course of active development, within the agreed scope.
- Vulnerability Awareness: Reasonable monitoring of security advisories relevant to the technology stack used in the Deliverables during the active development phase, and incorporation of appropriate mitigations within the agreed scope and timeline.
- Credential Handling: Treatment of all Client-provided credentials, API keys, and access tokens as Confidential Information in accordance with Section 10, use of secure channels for credential transmission, and avoidance of hardcoding credentials in source code or version control systems.
- Internal Security Controls: Maintenance of reasonable internal security policies governing the Agency's own systems, personnel access, and development environment, commensurate with the sensitivity of the data and services involved.
The security measures applied by the Agency are calibrated to the nature, sensitivity, and agreed scope of each engagement. The Client may request specific additional security controls or standards (such as OWASP ASVS compliance levels, penetration testing, or specific encryption requirements) by specifying them in the applicable SOW. Such requirements may affect scope, timeline, and pricing and shall be subject to written agreement before implementation.
16.2 Security in the Development Lifecycle
Where a Project includes a significant software development component, the Agency shall apply the following security considerations within the development lifecycle, to the extent within the agreed scope:
- Threat Modeling: Where appropriate given the complexity and sensitivity of the Deliverables, the Agency shall give reasonable consideration to foreseeable threat vectors during the design and architecture phase, and shall document material security assumptions or constraints in the applicable SOW or technical specification.
- Code Review: The Agency shall apply internal code review practices to identify and address security issues in Agency-developed code prior to delivery, using reasonable professional judgment as to the level of scrutiny appropriate for the relevant component.
- Testing Environments: The Agency shall use development and staging environments that are logically separated from the Client's production environment during development, where this is technically feasible and within the agreed Project structure.
- Secret Management: The Agency shall not store Client credentials, API keys, or secrets in version control repositories, and shall use secure secret management practices appropriate to the deployment environment.
- Third-Party Security: The Agency shall give reasonable consideration to the security posture of third-party components and services integrated into the Deliverables, and shall notify the Client where it identifies a known material security concern with a proposed integration.
The security measures described in this clause represent the Agency's standard professional approach and do not constitute a guarantee of the absence of security vulnerabilities in the Deliverables. Formal security testing — including penetration testing, code security audits, or vulnerability assessments — is outside the scope of standard development Services and must be separately agreed in writing.
16.3 Client Infrastructure and Environment Responsibility
The Client is solely responsible for the security, configuration, and integrity of all systems, infrastructure, and environments under its own control or management, including but not limited to:
- The Client's own servers, virtual machines, containers, hosting environments, and cloud infrastructure accounts, including all security group configurations, firewall rules, network policies, and operating system security settings.
- Third-party platform accounts, API accounts, SaaS subscriptions, and vendor services under the Client's control, including access management and account security settings for such services.
- All credentials, passwords, API keys, tokens, and access codes provided to or generated for the Agency in connection with the Services, including the secure storage, rotation, and revocation of such credentials.
- The configuration and security of the Client's production environment, including SSL/TLS certificate management, domain security settings, DNS configurations, and content delivery network settings.
- User account management within the Deliverables following delivery and acceptance, including the creation, administration, and deactivation of user accounts and access permissions.
- The implementation of recommended security configurations, updates, and patches in the Client's production environment following delivery, including timely application of security advisories communicated by the Agency.
- The security of the Client's internal network, workstations, and personnel devices used to access systems, repositories, or environments shared with the Agency.
The Agency shall not be liable for any security breach, data loss, unauthorized access, or adverse incident resulting from vulnerabilities, misconfigurations, or failures in Client-controlled systems or environments, including incidents that exploit weaknesses introduced or permitted by the Client's own infrastructure decisions, operational practices, or failure to apply recommended security measures.
Where the Client grants the Agency access to its systems or infrastructure in connection with the Services, the Client represents that it has implemented appropriate security measures within its environment and that granting such access is consistent with its own security policies and applicable regulatory requirements.
16.4 Security Incident Notification
In the event that the Agency becomes aware of a confirmed security incident affecting systems or data under its direct management that may have resulted in unauthorized access to, loss of, or compromise of Client data, the Agency shall:
- Notify the Client without undue delay following confirmation of the incident, and in any event within the timeframe required by applicable data protection law where Personal Data is involved.
- Provide the Client with such information as is available at the time of notification regarding the nature of the incident, the data or systems affected, the likely cause, and the steps being taken by the Agency to investigate and mitigate the incident.
- Cooperate with the Client in any investigation, regulatory notification, or remediation effort arising from the incident, to the extent within the Agency's reasonable operational capacity.
- Keep the Client reasonably informed of material developments in the investigation and remediation of the incident until it is resolved.
Where a security incident originates in or is materially contributed to by the Client's own systems, infrastructure, or personnel actions, the Agency's notification and cooperation obligations shall be limited to providing information within the Agency's knowledge and control, and the Agency shall not be responsible for remediation activities that fall within the Client's operational sphere.
The Agency's security incident notification obligations in relation to Personal Data breaches are further governed by Section 15.4 and the applicable DPA, where one has been executed.
16.5 Penetration Testing and Security Audits
Unless expressly agreed in writing in the applicable SOW:
- Penetration testing, vulnerability scanning, security auditing, and red team exercises are not included in the standard scope of development or support Services.
- The Client shall not conduct, or authorize any third party to conduct, any form of penetration testing, vulnerability scanning, or intrusive security testing against infrastructure, systems, or environments managed by the Agency without the Agency's prior written consent, specifying the scope, timing, methodology, and authorized testers.
- Where the Client wishes to commission security testing of the Deliverables or associated infrastructure, the parties shall agree the scope, methodology, timing, and responsible disclosure process in writing before any testing commences.
- The results of any security testing conducted on the Deliverables shall be treated as Confidential Information by both parties, and the Client shall provide the Agency with a copy of any material findings that relate to Agency-developed components within a reasonable timeframe following the conclusion of the testing.
- The Agency shall use commercially reasonable efforts to remediate confirmed, material security vulnerabilities identified in Agency-developed components through agreed security testing, within a timeframe proportionate to the severity of the findings, subject to the applicable support or engagement terms.
16.6 No Absolute Security Guarantee
The Client acknowledges that:
- No software system, network, or infrastructure can be guaranteed to be entirely free from security vulnerabilities or immune from all forms of cyberattack, unauthorized access, or data breach.
- The Agency's security measures, however diligently applied, do not constitute a warranty or guarantee of absolute protection against all security threats, including novel, sophisticated, or zero-day attack vectors.
- Security is a continuous operational discipline that extends beyond the delivery of any Deliverable, and the ongoing security posture of the Deliverables in the Client's production environment is the Client's responsibility following acceptance.
- The Agency shall not be liable for security incidents, data breaches, or unauthorized access events that occur after delivery and acceptance of the Deliverables, except to the extent directly and demonstrably caused by the Agency's gross negligence or willful misconduct in the original development of the affected component.
17. Indemnification
17.1 Client Indemnity
The Client agrees to indemnify, defend, and hold harmless the Agency and its parent company, affiliates, officers, directors, employees, subcontractors, agents, successors, and assigns (collectively, the "Indemnified Parties") from and against any and all third-party claims, actions, proceedings, demands, liabilities, damages, losses, penalties, fines, costs, and expenses (including reasonable legal fees and disbursements) arising out of or relating to:
- Any content, data, materials, assets, or instructions provided by the Client to the Agency in connection with the Services, including any allegation that such materials infringe the intellectual property rights, privacy rights, or other legal rights of any third party.
- Any allegation of intellectual property infringement arising from the Agency's use of Client-provided materials, Client-specified integrations, or Client-mandated technology choices in the performance of the Services.
- The Client's use, deployment, operation, or commercialization of the Deliverables in a manner that: violates any applicable law or regulation; infringes the rights of any third party; or exceeds the scope of any license or permission applicable to third-party components incorporated in the Deliverables.
- Any unlawful, fraudulent, abusive, or non-compliant use of the Services, Deliverables, or SaaS Products by the Client, its employees, agents, contractors, or authorized users.
- The Client's breach of any warranty, representation, or obligation under these Terms or the applicable agreement, including breach of the Client's data protection obligations, the legality of Client-provided materials under Section 6.4, or the Client's compliance obligations under Section 6.7.
- Any claim by a data subject, regulatory authority, or third party arising from the Client's failure to comply with applicable data protection laws in its capacity as Data Controller, or arising from the Client's instructions to the Agency as Data Processor.
- Any claim arising from the Client's modification of the Deliverables after acceptance, or from the Client's integration of the Deliverables with systems, platforms, or content not approved or provided by the Agency.
- Any claim arising from the Client's failure to obtain or maintain required licenses, consents, regulatory approvals, or third-party permissions necessary for the deployment or use of the Deliverables in the Client's intended markets or jurisdictions.
- Any negligent or wrongful act or omission of the Client, its employees, agents, contractors, or authorized users in connection with the Services or Deliverables.
17.2 Agency Indemnity
The Agency agrees to indemnify, defend, and hold harmless the Client and its officers, directors, and employees from and against any and all third-party claims arising from:
- A proven allegation that the Agency-developed components of the Deliverables — excluding Client-provided materials, open-source components, and Third-Party Services — infringe the intellectual property rights of a third party, provided that: the Client notifies the Agency promptly in writing of such a claim; the Client grants the Agency sole control over the defense and settlement of the claim; and the Client cooperates fully with the Agency in the defense of the claim.
- The Agency's gross negligence or willful misconduct in the performance of the Services, to the extent giving rise to a third-party claim against the Client.
The Agency's indemnity obligations under this Section 17.2 shall not apply where the alleged infringement arises from: the Client's modification of the Deliverables after delivery; the combination of the Deliverables with materials, systems, or services not provided or approved by the Agency; the use of Client-provided materials or Client-specified technology choices; or the Client's use of the Deliverables in a manner not authorized under these Terms.
17.3 IP Infringement Remedies
Where a third-party intellectual property infringement claim is brought or threatened in respect of any Agency-developed component of the Deliverables, the Agency shall have the right, at its sole election and expense, to:
- Procure the right for the Client to continue using the affected component on substantially the same terms as under these Terms.
- Modify or replace the affected component so that it becomes non-infringing, while maintaining substantially equivalent functionality.
- If neither of the above options is commercially feasible within a reasonable timeframe, terminate the Client's right to use the affected component upon written notice and refund a pro-rata portion of the fees paid for that component, as reasonably calculated by the Agency.
The remedies set out in this Section 17.3 shall constitute the Agency's entire liability and the Client's sole and exclusive remedy in respect of any third-party intellectual property infringement claim relating to the Deliverables, subject to the indemnity obligations in Section 17.2.
17.4 Indemnification Procedure
The following procedure shall apply to any claim for which indemnification is sought under this Section 17:
- Prompt Notice: The party seeking indemnification (the "Indemnified Party") shall notify the indemnifying party (the "Indemnifying Party") in writing as soon as reasonably practicable after becoming aware of any claim, action, or proceeding for which indemnification may be sought. Failure to provide timely notice shall not relieve the Indemnifying Party of its indemnification obligations except to the extent that the Indemnifying Party is materially prejudiced by such failure.
- Control of Defense: The Indemnifying Party shall have the right, upon written notice to the Indemnified Party, to assume sole control of the defense and settlement of the relevant claim, using legal counsel of its own choosing. The Indemnified Party shall cooperate fully with the Indemnifying Party in the defense of the claim, at the Indemnifying Party's reasonable expense.
- Cooperation: The Indemnified Party shall provide the Indemnifying Party with all reasonable assistance, information, and access required to defend or settle the claim, and shall not take any action that would materially prejudice the Indemnifying Party's defense.
- Settlement: The Indemnifying Party shall not settle any claim in a manner that imposes any obligation, liability, restriction, or admission of fault on the Indemnified Party without the Indemnified Party's prior written consent, which shall not be unreasonably withheld or delayed.
- Participation: The Indemnified Party shall have the right to participate in the defense of any claim at its own expense, using legal counsel of its own choosing, without relinquishing the Indemnifying Party's control of the defense.
17.5 Scope and Limitations of Indemnity
- The indemnification obligations set out in this Section 17 apply to third-party claims only and do not extend to claims brought by one party against the other directly.
- Indemnification under this Section 17 shall include reasonable legal fees, court costs, settlement amounts approved in accordance with Section 17.4, and other reasonable out-of-pocket expenses incurred in connection with the relevant claim, to the extent permitted by applicable law.
- The indemnification obligations of each party are subject to the overall liability limitations set out in Section 12, except where applicable law prohibits the application of such limitations to indemnification obligations.
- Neither party's indemnification obligations shall extend to claims arising from the other party's own negligence, willful misconduct, breach of these Terms, or failure to comply with applicable law.
18. Governing Law and Dispute Resolution
18.1 Governing Law
These Terms of Service, and all agreements, SOWs, and engagements entered into pursuant to or in connection with them, shall be governed by and construed in accordance with the laws of Georgia, without regard to its conflict of law principles that would require the application of the laws of any other jurisdiction, unless otherwise expressly agreed in a duly executed written agreement between the parties.
- The application of the United Nations Convention on Contracts for the International Sale of Goods (CISG) is expressly excluded from these Terms and all related agreements, to the extent permitted by applicable law.
- Where the Client is located in a jurisdiction whose mandatory consumer or commercial protection laws would otherwise apply, those mandatory provisions shall not be displaced by this governing law clause to the extent that applicable law prohibits such displacement.
18.2 Dispute Resolution — Negotiation
In the event of any dispute, controversy, or claim arising out of or in connection with these Terms, any related agreement, or the performance, breach, termination, or validity thereof (a "Dispute"), the parties shall first attempt to resolve the Dispute through good faith negotiation, as follows:
- The party raising the Dispute shall provide the other party with a written notice of Dispute, setting out in reasonable detail the nature of the Dispute, the relief sought, and the factual and legal basis for the claim.
- Upon receipt of a notice of Dispute, the parties shall designate senior representatives with authority to resolve the Dispute and shall engage in good faith discussions within ten (10) business days of the notice being received.
- The parties shall negotiate in good faith for a period of not less than thirty (30) calendar days from the date of the initial notice of Dispute (or such longer period as the parties may agree in writing) before commencing any formal dispute resolution proceedings.
- All negotiations conducted pursuant to this clause shall be confidential and conducted on a without-prejudice basis, and no statement or concession made during negotiations shall be admissible in any subsequent legal or arbitral proceedings.
18.3 Mediation
Where the parties are unable to resolve a Dispute through negotiation within the period specified in Section 18.2, either party may, by written notice to the other, refer the Dispute to mediation before commencing litigation or arbitration proceedings:
- Mediation shall be conducted by a single mediator agreed between the parties, or in the absence of agreement within ten (10) business days of the referral to mediation, appointed by a recognized mediation body or institution as agreed between the parties.
- The costs of the mediator and any mediation venue shall be shared equally between the parties, unless the mediator determines otherwise. Each party shall bear its own legal costs in connection with the mediation.
- Mediation shall be conducted on a confidential and without-prejudice basis. Any settlement reached through mediation shall be recorded in a written settlement agreement signed by both parties, which shall be binding and enforceable as a contract.
- Participation in mediation shall not limit or waive either party's right to pursue formal legal proceedings where mediation is unsuccessful or where urgent interim relief is required.
18.4 Jurisdiction and Courts
Subject to the dispute resolution process set out in Sections 18.2 and 18.3, and without prejudice to either party's right to seek urgent interim or injunctive relief from any court of competent jurisdiction:
- Any Dispute that is not resolved through negotiation or mediation shall be subject to the exclusive jurisdiction of the competent courts of Georgia.
- Each party irrevocably submits to the personal jurisdiction of the courts of Georgia for the purposes of any legal proceedings arising out of or in connection with these Terms or any related agreement.
- Each party waives any objection it may have to the venue of any such proceedings on the grounds of inconvenient forum, provided that this waiver shall not apply where a court determines that enforcement of this clause would be contrary to mandatory applicable law.
18.6 Injunctive and Interim Relief
Notwithstanding any other provision of this Section 18, either party may at any time apply to any court of competent jurisdiction for urgent interim or injunctive relief — including to prevent or restrain an actual or threatened breach of confidentiality, intellectual property infringement, or other irreparable harm — without being required to first complete the negotiation or mediation process set out in Sections 18.2 and 18.3, and without such application constituting a waiver of those processes.
18.7 International Clients
Where Services are provided to Clients located outside of Georgia:
- The governing law and jurisdiction provisions of this Section 18 shall remain applicable and binding unless expressly overridden by a separate written agreement signed by both parties.
- Where mandatory provisions of the Client's local law would otherwise apply and cannot be lawfully excluded, such provisions shall apply only to the minimum extent required, and the remainder of these Terms shall continue in full force and effect.
- The parties acknowledge that the Agency is incorporated and operates in Georgia, and that the choice of Georgian law and jurisdiction reflects a reasonable and agreed allocation of legal risk between the parties, taking into account the international nature of the services offered.
- Clients operating in jurisdictions with mandatory consumer protection regimes should seek independent legal advice as to the interaction between those regimes and these Terms before entering into any engagement with the Agency.
18.8 Language
These Terms and all related agreements, communications, and proceedings shall be conducted in the English language. Where any translation of these Terms is made available for convenience, the English language version shall prevail in the event of any conflict or inconsistency between the English version and any translation.
19. Portfolio and Attribution Rights
19.1 Right to Display Work
Unless expressly restricted by a separately executed non-disclosure agreement (NDA) or a specific written confidentiality restriction agreed between the parties in the applicable SOW, the Agency reserves the right to:
- Display completed Deliverables, project outputs, design work, and development outcomes in the Agency's portfolio, whether published on the Agency's website, social media channels, case study publications, pitch decks, or other promotional materials.
- Reference the Client's name, trading name, and logo in connection with a general description of the Services provided and the nature of the engagement, for the purpose of identifying the Agency's experience and client base.
- Describe the scope, nature, and general technical approach of the Project in non-confidential terms, for use in marketing collateral, award submissions, conference presentations, or business development materials.
- Use screenshots, design mockups, visual representations, and recordings of publicly accessible Deliverables — such as publicly deployed websites, web applications, or publicly available digital products — for portfolio and promotional purposes.
- Reference the engagement in third-party directories, industry listings, partner showcases, and accreditation submissions, where doing so supports the Agency's professional profile and business development activities.
The Agency shall exercise reasonable judgment in how Client work is represented in its portfolio materials, and shall not present any attribution in a manner that is misleading, exaggerated, or likely to damage the Client's reputation.
Where the Client wishes to review and approve the specific content of any portfolio reference or case study before it is published, the Client must communicate this requirement to the Agency in writing before Project completion. The Agency shall accommodate reasonable approval requests where notified in advance, and shall not unreasonably delay publication of approved content.
19.2 Limitations on Portfolio Use
Notwithstanding Section 19.1, the following limitations shall apply to the Agency's portfolio and attribution rights at all times:
- The Agency shall not disclose, reproduce, or publicly reference any element of a Project that constitutes Confidential Information under Section 10, including but not limited to proprietary business logic, non-public product features, internal system architecture, pricing structures, or commercially sensitive strategies.
- The Agency shall not publish or display any non-publicly accessible Deliverables — including internal tools, back-office systems, private dashboards, unreleased products, or staging environments — without the Client's prior written consent.
- The Agency shall not use the Client's name, logo, or brand assets in a manner that implies endorsement, partnership, or affiliation beyond the factual description of the services provided, or in any context that could be misleading to third parties.
- The Agency shall not attribute to the Client any statement, quote, testimonial, or review that the Client has not expressly provided and approved in writing for publication.
- Where the Client has provided a testimonial or reference that has been published by the Agency, the Client may request its removal or amendment at any time by written notice to the Agency, and the Agency shall action such request within a reasonable timeframe.
19.3 Confidential or Restricted Projects
Where a Project is subject to a separately executed NDA, a specific written confidentiality restriction in the applicable SOW, or where the Client has provided written notice of confidentiality requirements prior to Project completion:
- The Agency shall not disclose, publish, display, or publicly reference such work, including any visual representation, technical description, or Client identification, for as long as the applicable confidentiality obligation remains in effect.
- The existence of a confidential engagement may be acknowledged by the Agency in general terms — for example, as an unnamed engagement in a specific industry or technology category — provided that no information is disclosed that would allow a third party to identify the Client or the nature of the work.
- Where a confidentiality restriction applies to some elements of a Project but not others, the Agency shall work with the Client in good faith to agree on what, if any, portfolio reference is permissible within the bounds of the applicable restriction.
- Where a confidentiality restriction has a defined duration, the Agency's portfolio rights under Section 19.1 shall be reinstated upon expiry of that restriction, unless the parties have agreed otherwise in writing.
19.4 Client Attribution and Credit
Where the Client publicly deploys or markets Deliverables developed by the Agency:
- The Client may, but is not obligated to, credit the Agency as the development partner responsible for the relevant work. Where such credit is provided, the Agency's preferred attribution format shall be communicated to the Client upon request.
- The Client shall not represent Agency-developed Deliverables as having been independently developed by the Client's own team in any context where such a representation would be materially misleading to third parties, including but not limited to investor materials, award submissions, regulatory filings, or public procurement processes.
- Where the Client includes a "built by" or similar credit on a publicly deployed Deliverable, such credit shall remain in place for a minimum period agreed between the parties, unless the Client has obtained the Agency's written agreement to its removal.
19.5 Photography, Media, and Case Studies
Where the Agency wishes to produce a formal case study, video testimonial, press release, or media feature in connection with a Project:
- The Agency shall obtain the Client's prior written consent before producing or publishing such content, including consent to the specific details, quotes, and visual materials to be included.
- The Client shall have the right to review and approve the final content of any case study or media feature before it is published, and may request reasonable amendments to factual inaccuracies or commercially sensitive disclosures.
- Where the Client agrees to participate in a case study or media feature, such agreement shall not be construed as a waiver of the Client's confidentiality rights under Section 10 beyond the specific content expressly approved.
- Any media content produced by the Agency in connection with a Client case study shall remain the property of the Agency, subject to the Client's rights in respect of any Client-owned materials incorporated therein, and may be used by the Agency across its marketing channels without further consent unless the parties agree otherwise.
20. Miscellaneous Provisions
20.1 Non-Solicitation
During the term of any engagement and for a period of twelve (12) months following the conclusion of that engagement, the Client shall not, directly or indirectly:
- Solicit, approach, recruit, induce, or encourage any current employee, director, contractor, subcontractor, or freelancer of the Agency who was involved in the performance of the Services, to leave the Agency's employment or engagement or to provide services to the Client independently or through any other entity.
- Engage, hire, or contract with any such individual, whether as an employee, consultant, independent contractor, or through any intermediary, without the Agency's prior written consent.
This restriction shall not apply to:
- General public job postings or recruitment advertising not specifically targeted at or designed to attract Agency personnel.
- Any individual who independently approaches the Client for employment or engagement without having been directly or indirectly solicited by the Client.
- Any individual whose engagement with the Agency has formally ended for a period of more than six (6) months prior to the Client's approach, provided that the Client can demonstrate that it had no prior knowledge of the individual's departure at the time of the approach.
Where the Client is in breach of this clause, the Client shall pay to the Agency a placement fee equivalent to thirty percent (30%) of the relevant individual's annualized compensation (including salary, fees, or day rate as applicable), as a reasonable pre-estimate of the Agency's recruitment and retraining costs, without prejudice to any other remedies available to the Agency. The parties agree that this amount represents a genuine and reasonable estimate of loss and not a penalty.
20.2 Notices
All notices, requests, demands, consents, approvals, and other formal communications required or permitted under these Terms shall be made in writing and delivered by one of the following methods:
- By email to the address designated by each party for formal notices, as specified in the applicable agreement or as notified in writing from time to time. Notices delivered by email shall be deemed received at the time of transmission, provided no delivery failure notification is received by the sender within twenty-four (24) hours.
- By registered post or internationally recognized courier service to the registered address of the receiving party. Notices delivered by post or courier shall be deemed received on the date of confirmed delivery or, where delivery is refused, on the date of the first attempted delivery.
Each party is responsible for maintaining accurate and up-to-date notice contact details and for promptly notifying the other party in writing of any change to such details. Notices sent to the last known address or email address of a party shall be deemed validly delivered even if the party has failed to update its contact information.
Notices sent by instant messaging, social media, or informal communication channels shall not constitute formal notice for the purposes of these Terms unless both parties have expressly agreed in writing that a specific channel may be used for formal communications.
20.3 Relationship of the Parties
Nothing in these Terms or in any engagement entered into pursuant to them shall create, or be construed as creating, any partnership, joint venture, employment relationship, agency relationship, or fiduciary relationship between the Agency and the Client. Each party is an independent contractor acting on its own behalf and for its own account.
- The Agency shall have no authority to enter into any contract, incur any liability, or make any representation on behalf of the Client, and shall not hold itself out as having such authority.
- The Client shall have no authority to enter into any contract, incur any liability, or make any representation on behalf of the Agency, and shall not hold itself out as having such authority.
- The Agency's employees, contractors, and subcontractors are not employees of the Client and are not entitled to any employment benefits, statutory entitlements, or protections from the Client.
- Nothing in these Terms shall be construed to impose any liability on the Agency as an agent of the Client for the purposes of any tax, employment, or regulatory obligation.
20.4 Waiver
- No failure or delay by either party in exercising any right, power, or remedy under these Terms shall constitute a waiver of that right, power, or remedy, or of any other right, power, or remedy.
- No single or partial exercise of any right, power, or remedy shall preclude any further or other exercise of that or any other right, power, or remedy.
- No waiver shall be effective unless made in writing and signed by an authorized representative of the waiving party. A waiver given in relation to a specific breach or circumstance shall not operate as a waiver of any subsequent breach of the same or any other provision.
- The Agency's acceptance of late payment on any occasion shall not constitute a waiver of its right to enforce strict payment terms in respect of any subsequent invoice or outstanding amount.
20.5 Severability
If any provision of these Terms — or any part of a provision — is found by a court or competent authority to be invalid, illegal, void, or unenforceable under applicable law:
- That provision or part shall be deemed severed from these Terms to the minimum extent necessary to render the remaining provisions valid, legal, and enforceable.
- The validity, legality, and enforceability of the remaining provisions shall not be affected or impaired in any way, and shall continue in full force and effect as if the severed provision had never formed part of these Terms.
- Where a severed provision was fundamental to the commercial intention of the parties, the parties shall negotiate in good faith to replace it with a lawful provision that achieves, as closely as possible, the same commercial effect as the original provision.
- If no replacement can be agreed within thirty (30) days of the severance, the parties may terminate the affected engagement upon written notice, without liability except in respect of amounts already accrued and obligations already performed.
20.6 Entire Agreement
These Terms of Service, together with all applicable SOWs, project agreements, order forms, addenda, and any separately executed agreements expressly incorporated by reference (including any DPA, NDA, SLA, or maintenance agreement), constitute the entire agreement between the parties with respect to their subject matter and supersede all prior and contemporaneous discussions, negotiations, representations, understandings, and agreements — whether written or oral — relating to the same subject matter.
- Each party acknowledges that in entering into these Terms and any related agreement, it has not relied upon any representation, warranty, statement, or assurance made by or on behalf of the other party that is not expressly set out in these Terms or the applicable written agreement.
- Each party irrevocably and unconditionally waives any right it may have to claim damages for, or to rescind any agreement on the basis of, any misrepresentation not expressly incorporated into these Terms, unless such misrepresentation was made fraudulently.
- Where there is a conflict between these Terms and the terms of a specific SOW or separately executed agreement, the terms of the SOW or separately executed agreement shall prevail to the extent of the conflict, unless that document expressly states otherwise.
20.7 Amendments
- These Terms may be amended or updated by the Agency from time to time. Where the Agency proposes to amend these Terms in a manner that materially affects the rights or obligations of existing Clients under active engagements, the Agency shall provide no less than thirty (30) calendar days' prior written notice of the proposed changes.
- Amendments to these Terms shall not apply retroactively to SOWs or project agreements already executed and in force at the time of the amendment, unless both parties expressly agree in writing that the amended Terms shall apply.
- Any amendment or modification to a specific SOW, project agreement, or separately executed agreement must be made in writing and signed or confirmed in writing by authorized representatives of both parties before it becomes effective. Verbal amendments, amendments proposed by email without express written confirmation of acceptance, and amendments implied by conduct shall not be binding unless confirmed in writing.
- The Agency's publication of updated Terms on its website or distribution to the Client by email shall constitute valid notice of amendment for new engagements commencing after the effective date of the amendment.
20.8 Assignment
- Neither party may assign, transfer, delegate, sublicense, or otherwise dispose of any of its rights or obligations under these Terms or any related agreement, in whole or in part, without the prior written consent of the other party, which shall not be unreasonably withheld or delayed.
- Notwithstanding the foregoing, the Agency may assign or transfer its rights and obligations under these Terms without the Client's consent in connection with: a merger, acquisition, or change of control of the Agency; a sale of all or substantially all of the Agency's assets or business; or a corporate restructuring within the Agency's group of companies, provided that the assignee assumes all of the Agency's obligations under these Terms and the Client is notified in writing within a reasonable time following the assignment.
- Any purported assignment in breach of this clause shall be null and void. The assigning party shall remain liable for its obligations under these Terms notwithstanding any purported assignment unless the other party has given written consent to a full novation.
- These Terms shall be binding upon and inure to the benefit of the parties and their respective permitted successors and assigns.
20.9 Force Majeure — General
The Force Majeure provisions applicable to project delivery timelines are set out in Section 8.4. For the avoidance of doubt, Force Majeure shall apply equally to all obligations of both parties under these Terms where performance is prevented or materially impeded by circumstances beyond the affected party's reasonable control, subject to the notification and mitigation requirements set out in Section 8.4.
20.10 Counterparts and Electronic Execution
- These Terms and any related agreements may be executed in one or more counterparts, each of which shall constitute an original and all of which together shall constitute one and the same instrument.
- Electronic signatures, digital signatures, and signatures affixed via recognized electronic signature platforms (including but not limited to DocuSign, Adobe Sign, or equivalent services) shall be deemed valid and legally binding to the same extent as original handwritten signatures, to the extent permitted by applicable law.
- Execution of a SOW, agreement, or other document by email confirmation of acceptance — where both parties have agreed in writing that email confirmation constitutes a valid execution method — shall be treated as a binding executed agreement for the purposes of these Terms.
20.11 Language and Interpretation
- These Terms are drafted in the English language, which shall be the governing language for all purposes of interpretation and enforcement.
- Where any translation of these Terms is made available by the Agency for convenience, the English language version shall prevail in all respects in the event of any ambiguity, conflict, or inconsistency between the English version and any translation.
- Headings and section titles used in these Terms are for convenience of reference only and shall not affect the interpretation of any provision.
- References to "including" or "include" shall be construed as meaning "including without limitation" and shall not limit the generality of any preceding words.
- References to "writing" or "written" include email communications where the context so permits, unless these Terms or the applicable agreement expressly require a more formal written instrument.
- Where the context permits, references to a statutory provision include references to that provision as amended, re-enacted, or replaced from time to time.
- Where any period of time is expressed in "days" without further qualification, it shall refer to calendar days unless expressly stated as "business days." Business days means days other than Saturdays, Sundays, and public holidays in Georgia.
20.12 Third-Party Rights
- These Terms do not confer any rights on any person or entity who is not a party to the relevant agreement, and no third party shall have any right to enforce any provision of these Terms under any applicable third-party rights legislation, unless expressly stated otherwise in a specific written agreement.
- The rights of the parties to vary, amend, or terminate these Terms shall not be subject to the consent of any third party.
20.13 Publicity
- Neither party shall issue any press release, public announcement, or media statement referencing the other party or the engagement between the parties without the other party's prior written consent, except as required by applicable law, stock exchange rules, or regulatory obligation.
- Where a party is required by law or regulation to make a public disclosure referencing the other party, it shall, to the extent permitted by law, provide the other party with advance written notice and a reasonable opportunity to review and comment on the proposed disclosure before it is made.
20.14 Survival
In addition to the survival provisions set out in Section 13.8, the following provisions of these Terms shall survive the termination or expiration of any engagement for any reason and shall remain in full force and effect in accordance with their terms: Section 1 (Definitions), Section 5 (Intellectual Property), Section 10 (Confidentiality), Section 11 (Warranties and Disclaimers), Section 12 (Limitation of Liability), Section 17 (Indemnification), Section 18 (Governing Law and Dispute Resolution), and this Section 20 (Miscellaneous Provisions).
Acceptance and Execution
By entering into any agreement with the Agency — including by executing a Statement of Work, submitting a purchase order, providing written confirmation of acceptance, or commencing use of the Services — the Client confirms that it has read, understood, and agrees to be bound by these Terms of Service in their entirety, together with any applicable SOW, addendum, or separately executed agreement.
Where these Terms are accepted on behalf of a company or other legal entity, the individual accepting represents and warrants that they have the authority to bind that entity to these Terms, and that the entity will be responsible for all obligations arising hereunder.
These Terms shall take effect from the Effective Date as defined in Section 1.
Akazuki Works Georgia LTD Registered in England and Wales _These Terms were last updated on: First of january 2026 Version: 1.4