1. Terms

1.1 The following definitions and rules of interpretation apply to these Terms of Business:

“Acceptance”

means acceptance of the Software in accordance with clause 8.6 and “Accepted” will be construed accordingly.

“Application Support Fees”

means the fees payable for the Application Support Services as set out in the Engagement Letter.

“Application Support Period”

means the 3-month period during which Byte9 Delivers the Application Support Services to the Customer (as may be extended in accordance with clause 11).

“Application Support Services”

means the services described in the Application Support Schedule.

“Bespoke Software Deliverables”

means the software and documentation developed by Byte9 specifically for the Customer under this Agreement, but excluding any modifications and the Software, in each case as listed in the Specification agreed between the parties and identified in the Specification and Jira as a “Bespoke Software Deliverable”.

“Blaze Application”

means the Blaze front-end application, the Blaze application programming interface (API) or the Blaze administrative user interface application , as applicable.

“Browser Operating Environment”

means the internet browser software running within the operating systems set out in the Hosting and Operating Environment Schedule.

“Business Hours”

means 9am to 6pm on a Working Day.

“Byte9 Personnel”

means directors, officers, employees, agents or subcontractors of Byte9.

“Blaze Trade Mark”

means the trade mark set out in the Trade Mark Schedule.

“Blaze Features”

means the core functionality of the Software and the Blaze plugins, as set out in the Blaze Features Schedule.

“Customer Materials”

means all materials, content, trademarks data and information provided, or to be provided, by the Customer including any materials described in the Customer Materials Schedule.

“Data Protection Laws”

means all laws relating to data protection and data privacy, including the Data Protection Act 2018, the EU General Data Protection Regulation (2016/679) (“GDPR”), the UK GDPR, the Electronic Communications Data Protection Directive 2002/58/EC, the Privacy and Electronic Communications (EC Directive) Regulations 2003, all as amended from time to time, including, where applicable, guidance and codes of practice.

“Delivery”

means the delivery of, or the granting of access to, the Software or a part of the Software and “Deliver” will be construed accordingly.

“Development Fees”

means the fees for the Development Services, as set out in the Engagement Letter.

“Development Services”

means the development services provided by Byte9 under this Agreement as set out in the Engagement Letter, including the Initial Implementation and the Retained Development Services as applicable.

“Development Schedule”

means the schedule of Development Services set out in the Jira Project Backlog, including the Stories, Estimations and Fees.

“Documentation”

means any documentation necessary to enable a reasonably skilled operator of software to operate the Software.

“Effective Date”

has the meaning set out in the Engagement Letter.

“Fees”

means the sums payable by the Customer to Byte9 for the Software and the Services, including as set out in the Engagement Letter, including the Development Fees, the Application Support Fees, the Hosting Fees, the Hosting Support Fees and the Proprietary Plugin Fees, as applicable.

“Hosting Fees”

means the fees payable by the Customer for the Hosting Services as set out in the Engagement Letter.

“Hosting Services”

means the hosting services provided by cloud services provider (which might include Amazon Web Services) under this Agreement, and as set out in the Hosting Schedule.

“Hosting Support Period”

means the 3-month period during which Byte9 Delivers the Hosting Support Services to the Customer (as may be extended in accordance with clause 12).

“Hosting Support Services”

means the support package as agreed to be provided by Byte9 in accordance with the Engagement Letter.

“Initial Implementation”

means the initial Development Services Delivered by Byte9 to the Customer in accordance with the Development Schedule.

“Jira Project Backlog”

means the backlog of tasks and deliverables to be developed in relation to the Services as documented on Jira, as agreed between the parties in accordance with the Status Update Meetings.

“IPRs”

means all copyright and related rights, patents, rights to inventions, utility models, trademarks, service marks, trade, business and domain names, rights in trade dress or get-up, rights in goodwill or to sue for passing off, unfair competition rights, rights in designs, rights in computer software, database right, topography rights, moral rights, rights in confidential information (including know-how and trade secrets) and any other intellectual property rights, in each case whether registered or unregistered and including all applications for and renewals or extensions of such rights, and all similar or equivalent rights or forms of protection.

“Malware”

means any software designed to maliciously infiltrate, interfere with, intercept, expropriate or damage a computer system, data or other information.

“Operating Environment”

means the operating system, integrated applications environment, cloud service provider services (which might include AWS) and the Browser Operating Environment, set out in the Hosting and Operating Environment Schedule.

“Developer Day”

means the amount of development work performed by an average developer in approximately one calendar day.

“Product Owner”

means the individual nominated by the Customer as its key representative for liaising with Byte9 with regard to the provision of Development Services under this Agreement.

“Proprietary Plugins”

means Blaze plugins provided by Byte9 which Byte9 may license to the Customer in accordance with clause 4.

“Proprietary Plugin Fees”

means the fees payable by the Customer for the Proprietary Plugins (if applicable) as set out in the Engagement Letter.

“Quality Assurance Tests”

means the tests to be performed on the Software, in respect of its operation in the Browser Operating Environment only, in accordance with clause 8.

“Retained Development Services”

means the amount of development services to be provided by Byte9 under this Agreement on a retained basis (if any), and as set out in the Engagement Letter.

"Retained Development Period”

means the 3-month period during which Byte9 Delivers the Retained Development Services to the Customer (as may be extended in accordance with clause 14).

“Services”

as applicable and in accordance with the services set out in Engagement Letter, means the Retained Development Services, the Hosting Services, the Proprietary Plugins, the Development Services, the Application Support Services and Hosting Support Services.

“Software” or “Blaze” (as applicable)

means the software provided by Byte9 under this Agreement, including the software known as “Blaze” comprising the Blaze Applications, any Blaze Features, Blaze plugins, the Documentation and any parts of the Operating Environment provided or on which any of the foregoing runs (or, as the context requires, any part of any of them).

“Specification”

means the document containing technical specifications for the Delivery of the Services, as agreed from time to time.

“Status Update Meeting”

means the meeting between Byte9 and the Customer as set out in clause 6.1.2 where development Story priorities are reviewed and any new Stories are added and priorities assessed with the Product Owner.

“Story”

means the description of the objectives and intended benefits of a particular function of the Software as required by a user of the Software, but excluding the Initial Implementation, each as set out in the Jira Project Backlog.

“Working Day”

means any day other than a Saturday or Sunday on which banks are open for trading in London.

“Updates”

an update to the Software which enhances the functionality of the Software.

1.1 A “person” includes a natural person, corporate or unincorporated body.

1.2 Unless the context otherwise requires, words in the singular include the plural and in the plural include the singular.

1.3 The words “include” and “including” (or similar) will be deemed to have the words “without limitation” after them.

1.4 A reference to “writing” or “written” includes e-mail, instant messaging services (including Slack) and/or comments in project management software (including Jira or Confluence).

1.5 The terms “data controller”, “data processor”, “data subject”, “personal data”, “process” and “processing” will have the meanings ascribed to them under the Data Protection Laws.

2. Services and repository

2.1 Subject to the Customer’s payment of the Fees to Byte9, for the term of this Agreement Byte9 will Deliver the Services to the Customer as set out in the Engagement Letter.

2.2 Byte9 will grant access to the Customer to use the repository containing the Blaze Features in accordance with the Blaze Features Schedule for the terms of this Agreement. For clarity, the Customer may use the Blaze Features to carry out its own development work, subject to the terms of this Agreement.

2.3 If Byte9 grants the Customer a separate repository or environment within the Software, the Customer will use all reasonable endeavours to prevent any unauthorised access to, or use of, the Software or the Services and will notify Byte9 promptly in writing of any such unauthorised access or use. Byte9 will not be liable to the Customer for any loss or damage suffered by the Customer from such unauthorised access or use.

2.4 The Customer acknowledges that some parts of the Operating Environment will form part of the Software. Ownership of the Operating Environment will remain vested in its proprietor. The Operating Environment may only be used by the Customer on the terms of the licence granted by the proprietor of Operating Environment (as applicable).

3. Bespoke Software Deliverables

3.1 If the parties agree to the Delivery of any Development Services in the Engagement Letter, Byte9 will Deliver Bespoke Software Deliverables to the Customer in accordance with Specification and the Jira Project Backlog.

3.2 For clarity, either party may carry out development work on Bespoke Software Deliverables (known as “co-sourcing”). If either party makes a change to the Bespoke Software Deliverables, regression testing will have to be completed by whoever introduces those changes. In the event those changes are made by Byte9, the warranties given by Byte9 in clause 23.2 will continue to apply. In the event those changes are made by the Customer, the warranties given by Byte9 in clause 23.2 will no longer apply.

3.3 Byte9 will deposit anyBespoke Software Deliverables in a private shared code repository on GitHub that both parties have full unfettered access to. Byte9 will Deliver the Bespoke Software Deliverables to the shared code repository, with unit tests and appropriate Documentation.

4. Proprietary Plugins

4.1 If the Customer opts to purchase access to the Proprietary Plugins in accordance with the Engagement Letter, Byte9 grants, subject to the terms of this Agreement, to the Customer the non-exclusive, non-sublicensable right to access and use the Proprietary Plugins for the term of this Agreement. The Customer will not, and will ensure that its users will not:

4.1.1 use the Software or the Services in a manner that may violate any applicable law or regulation;

4.1.2 except as expressly authorised by Byte9 in writing or except as permitted by applicable law, attempt to decompile, disassemble or reverse engineer the Software; or

4.1.3 except as expressly authorised by Byte9 in writing or except as permitted by applicable law, attempt to copy, modify, transmit or distribute the Software.

5. Stories and Initial Implementation

5.1 Byte9 will Deliver the Initial Implementation as soon as practicable after the Effective Date but in all cases in accordance with the Development Schedule. The Customer, or Byte9 at the Customer’s request, will undertake the Quality Assurance Tests in respect of the Initial Implementation as soon as practicable following Delivery.

5.2 Byte 9 will Deliver the subsequent Stories in accordance with the Development Schedule. The Customer, or Byte9 at the Customer’s request, will undertake the Quality Assurance Tests in respect of the Stories as soon as practicable following Delivery.

5.3 The Customer will cooperate with Byte9 at all times and will use all reasonable endeavours to promptly provide Byte9 such:

5.3.1 Customer Materials;

5.3.2 access to its computer systems and other facilities; and

5.3.3 other assistance,

as Byte9 may reasonably request to enable it to Deliver the Software and provide the Services in accordance with this Agreement.

5.4 The Customer will ensure the Product Owner is available to attend all Status Update Meetings and is reasonably familiar with the process of agile software development. The Customer may replace the Product Owner on notice to Byte9, but will use all reasonable endeavours to ensure any such replacements are kept to a minimum.

5.5 Byte9 will not be liable for any delay in the Delivery of any part of the Software if such delay is caused by the Customer, including any failure of the Customer to supply Byte9 with Customer Materials or approvals, or any instructions requested by Byte9.

5.6 Time is not of the essence of this Agreement and any dates are estimates only.

6. Changes to the Development Schedule

6.1 The Product Owner will, on behalf of the Customer:

6.1.1 agree with Byte9 the initial order of priority of the undeveloped Stories forming the Jira Project Backlog;

6.1.2 attend all Status Update Meetings and ,throughout the provision of the Development Services, in agreement with Byte9, revise and reprioritise the undeveloped Stories forming the Jira Project Backlog on an ongoing basis. The Jira Project Backlog will not be revised and reprioritised without the agreement of both parties;

6.1.3 correspond with Byte9 on a regular basis, including as requested by Byte9 and as necessary to Deliver the Stories in accordance with the Jira Project Backlog; and

6.1.4 meet with Byte9 to review the Stories to be developed in the Jira Project Backlog and agree with Byte9 which Stories will be submitted to Quality Assurance Testing. Stories will be submitted to Quality Assurance Testing only if they constitute a potentially useful increase in functionality of the Software and are reasonably considered to be capable of passing the Quality Assurance Tests.

6.2 The Customer may request revisions or reprioritisations in accordance with clause 6.1 that change the number of Developer Days required to Deliver a Story (“Change Request”).

6.3 Any changes to the number of Developer Days attributable to a Story subject to a Change Request, and the number of Developer Days attributable to a new Story subject to a Change Request, will be notified to the Customer by Byte9.

6.4 The Customer will confirm to Byte9 in writing whether or not to implement the Change Request.

6.5 Byte9 will be under no obligation to implement any Change Request which would cause the aggregate number of Developer Days to exceed the number of Developer Days agreed in the Development Schedule and Retained Development Services in the Engagement Letter.

6.6 The parties will seek to reach the agreements referred into in this clause 6 acting reasonably and in good faith.

7. Hosting

7.1 Subject to the Customer paying the Hosting Fees to Byte9, The Software will be hosted by a third party cloud services provider in accordance with the Hosting Schedule.

8. Quality Assurance Testing

8.1 The parties will cooperate to devise appropriate Quality Assurance Tests for the Initial Implementation and each Story. All Quality Assurance Tests will be subject to Byte9’s written approval.

8.2 Each Quality Assurance Test will be sufficient to determine whether or not (as applicable):

8.2.1 the Initial Implementation provides the functionality described in the respective part of the Development Schedule within the Operating Environment; or

8.2.2 the relevant Stories provide the functionality described in the respective Story within the Operating Environment.

8.3 Each of the parties will provide the other with all access, assistance and information reasonably requested by the other in order to ensure the Quality Assurance Tests are performed promptly.

8.4 If the relevant Software fails to pass the Quality Assurance Tests, the Customer will provide Byte9 with a notice specifying each instance of failure in reasonable detail. On receipt of such notice, Byte9 will use its reasonable endeavours to carry out any development works necessary (in its opinion) to enable the relevant Software to pass the Quality Assurance Tests. The relevant Software will then be Delivered to the Customer and the Quality Assurance Tests will be performed again. This process will be repeated until the Quality Assurance Tests are passed.

8.5 If the Quality Assurance Tests:

8.5.1 are not commenced within 5 Working Days of Delivery of the relevant Software due to the acts or omissions of the Customer; or

8.5.2 are performed and no notice of failure of the Quality Assurance Test is provided by the Customer within 5 Working Days of the completion of the Quality Assurance Tests,

the Quality Assurance Tests will be deemed to have been passed.

8.6 Software will be deemed to have been Accepted on passing the respective Quality Assurance Tests.

9. Updates

9.1 Subject to payment by the Customer to Byte9 of the Fees, Byte9 will supply and install Updates issued generally by Byte9 to users of the Software after the Effective Date, including physical documentation detailing all changes that are contained within the Updates.

10. Software Releases

10.1 Byte9 may provide  updates to the Jira backlog, outlining any developments and software releases and other development relating to the Software expected to be released.

10.2 Byte9 will notify the Customer in writing of key details relating to each proposed major software release as early as possible in the development process.

11. Application Support Services

11.1 Subject to payment by the Customer to Byte9 of the Fees, Byte9 will provide the Customer with the Application Support Services for the Application Support Period, in accordance with the terms of the Agreement.

11.2 Unless otherwise agreed in writing between the parties, the Application Support Period will begin on the date of the Customer’s Acceptance of the Initial Implementation and will automatically renew for consecutive 3-month periods until this Agreement is terminated.

11.3 Either party may terminate the Application Support Services for any reason on 30 days’ written notice to the other party, such notice not to expire prior to the end of the Application Support Period then in effect.

12. Hosting Support Services

12.1 Subject to payment by the Customer to Byte9 of the Fees, Byte9 will provide the Customer with the Hosting Support Services for the Initial Hosting Support Period and any Extended Hosting Support Periods, in accordance with the terms of the Agreement.

12.2 Unless otherwise agreed in writing between the parties, the Hosting Support Period will begin on the date of the Customer’s Acceptance of the Initial Implementation and will automatically renew for consecutive 3-month periods until this Agreement is terminated.

12.3 Either party may terminate the Hosting Support Services for any reason on 30 days’ written notice to the other party, such notice not to expire prior to the end of the Hosting Support Period then in effect.

13. On-Site Support

13.1 In the event that on-site support is requested the Customer will at its own expense permit such access to their premises as may be required for the purposes of providing the Application Support Services.

13.2 When visiting Customer premises Byte9 employees or agents will comply at all relevant times with any reasonable instructions of the Customer and will in any event comply at all times with the reasonable safety and security procedures of the Customer.

13.3 Travel and all other incidental expenses in providing on-site support must be notified to the Customer and agreed in advance in writing by the Customer unless they amount in total to less than £500. The Customer will reimburse within 30 days of receipt of an invoice from Byte9 in respect of agreed expenses incurred in providing on-site support save in the case of manifest error.

14. Retained Development Services

14.1 If agreed in the Engagement Letter and subject to payment by the Customer to Byte9 of the Fees, Byte9 will provide the Customer with the Retained Development Services for the Retained Development Period , in accordance with the terms of the Agreement.

14.2 Unless otherwise agreed in writing between the parties, the Retained Development Period will begin on the date of the Customer’s Acceptance of the Initial Implementation and will automatically renew for consecutive 3-month periods until this Agreement is terminated.

14.3 Either party may terminate the Retained Development Services for any reason on 30 days’ written notice to the other party, such notice not to expire prior to the end of the Retained Development Period then in effect

15. Meetings

15.1 Separately to the Status Update Meetings, during the term of this Agreement:

15.1.1 If required the parties will meet at regular intervals (at times and places to be agreed) to discuss the development of the Software and any issues relating to performance of the Services.

15.1.2 The Customer may notify Byte9 of the relevant personnel the Customer reasonably consider desirable to attend each meeting subject to the availability of our relevant personnel on the relevant date(s).

15.2 Nothing in this Clause 15 will take effect nor be deemed to take effect so as to restrict or limit the discretion of Byte9 in the development of major software releases.

16. Obligations of the Customer

16.1 During the continuance of this Agreement the Customer will at its own expense:

16.1.1 at the reasonable request of Byte9 allow Byte9 access to the Software and if necessary any other Hosting Services or equipment belonging to the Customer and make available to Byte9 any facilities information and services which are reasonably required by Byte9 to enable it to provide the Services;

16.1.2 provide such telecommunication facilities as are reasonably required by Byte9 for testing and diagnostic purposes;

16.1.3 keep Byte9 informed of an e-mail address through which all communications relating to the Services can be made during the term of this agreement;

16.1.4 install and test a Critical Update (as defined in the Application Support Schedule) in a timely period in the manner specified by the Byte9; and

16.1.5 operate the Software, maintain data and the database in accordance with the user manual and operator manual.

16.2 The Customer warrants that it will comply in all material respect with all applicable laws, regulations and codes of conduct (whether statutory or otherwise) of the United Kingdom, and that all licenses, permissions and consents required for carrying on its business have been obtained and are in full force and effect.

17. Payment

17.1 Byte9 will issue invoices in accordance with the Engagement Letter.

17.2 The Customer will pay Byte9 undisputed Fees that are properly due and payable (together with any applicable VAT) within 30 days of issue of a valid invoice.

17.3 In the event of any good faith dispute with regard to a portion of an invoice, the undisputed portion will be paid as set out above. Upon resolution of the disputed portion, any amounts owed to Byte9 will be paid by the Customer.

17.4 Byte9 will be entitled to charge interest on any overdue payment at the rate of 4% over base rate of the Barclays Bank from time to time.

17.5 Byte9 will invoice and be paid in GBP Sterling.

18. Intellectual Property Rights and Licence

18.1 All IPRs in the Bespoke Software Deliverables will upon full payment of the Fees immediately on their creation vest in the Customer. To the extent that any such IPRs vest in the Byte9, Byte9 assigns, and by way of future assignment will assign, such IPRs to the Customer with full title guarantee. Byte9 will at the Customer’s cost immediately take any action or do any thing (including executing documents) necessary to perfect the assignment in this clause 18.1.

18.2 The Customer grants, subject to the terms of this Agreement, to Byte9 the worldwide, non-exclusive right to use the Customer Materials, Jira Project Backlog, and the Bespoke Software Deliverables for the purpose of exercising Byte9’s rights or performing its roles, responsibilities, duties and obligations under this Agreement during the term hereof.

18.3 The Blaze Features will be subject to one of the license terms of the open-source GNU GPLv3 (available at: https://www.gnu.org/licenses/gpl-3.0.en.html) or MIT (available at: https://opensource.org/license/mit/) licenses, as labelled in the relevant repository. All IPRs in the Blaze Features will remain the exclusive property of Byte9 and the Customer will acquire no ownership right, title or interest in or to the Blaze Features.

18.4 Except as expressly set out in this Agreement, no other right, title or interest in or to the IPRs will be transferred between the parties as a result of this Agreement. Except where Byte9 grants prior written approval to the Customer, the Customer agrees that it does not have right, title or interest in or to the Blaze Trade Mark and the Customer will not use the Blaze Trade Mark for any purpose.

19. Indemnity

19.1 Byte9 will defend the Customer, its officers, directors and employees against any claim that the Customer's use of the Software infringes any Intellectual Property Rights (excluding patents) (a “Byte9 Claim”) and will indemnify the Customer for any amounts awarded against the Customer in judgment or settlement of the Byte9 Claim or otherwise reasonably incurred by the Customer in connection with a Byte9 Claim.

19.2 The Customer will defend Byte9, its officers, directors and employees against any claim that the Byte9’s use of the Customer Materials infringes any Intellectual Property Rights (a “Customer Claim” and together with a Customer Claim, a “Claim”) and will indemnify the Customer for any amounts awarded against Byte9 in judgment or settlement of the Customer Claim or otherwise reasonably incurred by Byte9 in connection with a Customer Claim.

19.3 The above indemnities are given subject to:

19.3.1 the indemnified party given the indemnifying party prompt notice of any Claim or potential Claim;

19.3.2 the indemnifying party being given sole authority to defend or settle the Claim; and

19.3.3 the indemnified party providing reasonable co-operation to the indemnifying party in the defence and settlement of such Claim, at the indemnifying party’s expense.

19.4 In the defence or settlement of a Byte9 Claim, Byte9 may obtain for the Customer the right to continue using the Software, replace or modify the Software so that it becomes non-infringing or, if such remedies are not reasonably available, terminate this Agreement without liability to the Customer.

19.5 Byte9 will have no liability if the alleged infringement is based on:

19.5.1 a modification of the Software by person other than Byte9;

19.5.2 the Customer’s use of the Software in breach of this Agreement or in a manner contrary to the instructions given to the Customer by Byte9; or

19.5.3 the Customer’s use of the Software after becoming aware of any potential Claim.

19.6 The provisions of this clause 19 are the Customer’s sole and exclusive rights and remedies, and Byte9’s entire obligations and liability, for Intellectual Property Rights infringement.

20. Confidentiality

20.1 In this clause, “Confidential Information” means the Software, the Documentation, the Customer Materials and any other information that is clearly labelled or identified as confidential or that ought reasonably be treated as being confidential. Confidential Information excludes any information which:

20.1.1 is or becomes publicly known other than through a breach of this Agreement;

20.1.2 was in the receiving party’s lawful possession before the disclosure;

20.1.3 is lawfully disclosed to the receiving party by a third party without restriction on disclosure;

20.1.4 is independently developed by the receiving party and that independent development can be shown by written evidence; or

20.1.5 is required to be disclosed by law, by any court of competent jurisdiction or by any regulatory or administrative body.

20.2 Each party will hold the other’s Confidential Information in confidence and not make the other’s Confidential Information available to any third party, or use the other’s Confidential Information for any purpose other than the implementation of this Agreement.

20.3 Each party will take all reasonable steps to ensure that the other’s Confidential Information to which it has access is not disclosed or distributed by its employees, agents or independent contractors in breach of the terms of this Agreement.

20.4 This clause 20 will survive termination of this Agreement for a period of 5 years.

21. Promotion

21.1 Byte9 may refer to its provision of services to the Customer under this Agreement in press, articles, awards and other media, subject to the Customer’s prior written approval as to the form, content and timing of all such references (such approval not to be unreasonably withheld or delayed).

22. Data Protection

22.1 Each party will comply with the Data Protection Laws.

22.2 It is not the intention of the parties that either party will process personal data for or on behalf, or on the instructions, of the other party. To the extent that either party processes personal data for or on behalf, or on the instructions, of the other party, the parties will enter into an addendum to this agreement to govern such processing arrangements, as required by Data Protection Laws.

22.3 Subject to clause 22.2, it is acknowledged that to the extent that the Customer, in connection with the provision of the Services, provides Byte9 with personal data, each party will be an independent data controller in respect of such personal data (as such terms are defined in the Data Protection Laws.

23. Warranties

23.1 Each of the parties warrants that:

23.1.1 it has the requisite power and authority to enter into this Agreement and to perform fully its obligations under this Agreement;

23.1.2 it has not entered into and will not enter into any arrangement which would restrict or inhibit the exercise by the other party of its rights under this Agreement; and

23.1.3 it will fulfil its obligations under this agreement in accordance with all applicable laws, regulations and codes of practice.

23.2 Byte9 warrants that:

23.2.1 it will supply the Software and the Services with reasonable skill and care;

23.2.2 it will use reasonable skill and care in estimating the Developer Days attributable to any Story and use reasonable endeavours to ensure that all estimated Developer Days are consistent and accurate in accordance with good industry practice;

23.2.3 the Initial Implementation will provide the functionality described in the respective part of the Development Schedule within the Operating Environment for a period of 30 days from its Acceptance;

23.2.4 each of the Stories will provide the functionality described in the Jira Project Backlog for a period of 30 days from its Acceptance;

23.2.5 it will engage adequate numbers of Byte9 Personnel and that such Byte9 Personnel will:

(a) have the necessary skills and expertise to develop the Software;

(b) perform the Services at a standard generally observed in the industry for similar services;

23.2.6 the Software will be compatible with the Customer’s existing computer systems (solely to the extent such systems are notified to Byte9), without material modification, loss of use or performance;

23.2.7 so far as Byte9 is aware, the Software will be free from all Malware; and

23.2.8 the Documentation will be accurate and sufficiently detailed to enable a reasonably skilled operator of software to operate the Software.

23.3 The Software and Services are provided "as is" to the fullest extent permissible pursuant to applicable law. Save as set out in this Agreement, Byte9 disclaims all warranties express or implied, including, but not limited to, implied warranties of satisfactory quality and fitness for a particular purpose, in relation to the Software and Services, their use and the results of such use. Byte9 specifically disclaims any warranty:

23.3.1 that the Software and Services will be uninterrupted or error-free;

23.3.2 that defects will be corrected;

23.3.3 that there are no viruses or other harmful components;

23.3.4 that the security methods employed will be sufficient; and

23.3.5 regarding correctness, accuracy, or reliability.

24. Warranty Period

24.1 If:

24.1.1 the Initial Implementation fails to materially conform with the respective part of the Development Schedule; or

24.1.2 any Story fails to materially conform with its respective part of the Development Schedule,

(in each case a “Defect”) the Customer will notify Byte9 in writing, providing reasonable detail of the Defect. Byte9 will use its reasonable endeavours to correct any Defects which are notified to it, provided that such notice is served within 30 days of the respective date of Acceptance.

24.2 Byte9 will have no obligation to correct Defects which are caused by:

24.2.1 any modification of the Software not made by Byte9;

24.2.2 the Customer’s use of the Software in breach of this Agreement or in a manner contrary to the instructions given to the Customer by Byte9;

24.2.3 use of the Software with other software or hardware which is incompatible or inadequate, as determined by Byte9 in its sole discretion; or

24.2.4 failure of the Hosting Services.

24.3 The provision of the clauses 24.1 and 24.2 will be the Customer's only remedy for Defects.

25. Limitation of Liability

25.1 This clause 25 sets out Byte9's entire financial liability (including any liability for the acts or omissions of its employees, agents and sub-contractors) to the Customer:

25.1.1 arising under or in connection with this Agreement;

25.1.2 in respect of any use made by the Customer of the Software or Services or any part of them; and

25.1.3 in respect of any representation, misrepresentation (whether innocent or negligent), statement or tortious act or omission (including negligence) arising under or in connection with this Agreement.

25.2 Nothing in this Agreement excludes the liability of Byte9:

25.2.1 for death or personal injury caused by Byte9’s negligence;

25.2.2 for fraud or fraudulent misrepresentation; or

25.2.3 any statutory liability not capable of limitation.

25.3 Except as expressly and specifically provided in this Agreement, the Customer assumes sole responsibility for its use of the Software or Services, and for the results of such use. Byte9 will have no liability for any damage caused by:

25.3.1 errors or omissions in any information or instructions provided to Byte9 by the Customer; or

25.3.2 any actions taken by Byte9 at the Customer’s direction.

25.4 Subject to clause 25.2, Byte9 will not be liable whether in tort (including for negligence or breach of statutory duty), contract, misrepresentation (whether innocent or negligent), restitution or otherwise for:

25.4.1 any loss of profits, loss of data or information, loss of business, loss of anticipated savings, depletion of goodwill and/or similar losses, or pure economic loss, or for any special, indirect or consequential loss costs, damages, charges or expenses however arising under this Agreement (even if such loss was reasonably foreseeable or if Byte9 had been advised of the possibility of such loss arising);

25.4.2 any losses which are not notified to Byte9 within 1 year of the date on which the events giving rise to the losses occurred; or

25.4.3 any losses which are caused by:

(a) any modification of the Software not made by Byte9;

(b) the Customer’s use of the Software in breach of this Agreement or in a manner contrary to the instructions given to the Customer by Byte9;

(c) use of the Software with other software or hardware (including in respect of software hosting services) which is incompatible or inadequate, as determined by Byte9 in its sole discretion;

(d) the failure of the Hosting Services; or

(e) any content provided or generated by any user of the Software.

25.5 Subject to clause 25.2, Byte9’s total aggregate liability in contract (including in respect of the indemnity at clause 19.1), tort (including negligence or breach of statutory duty), misrepresentation (whether innocent or negligent), restitution or otherwise, arising in connection with the performance or contemplated performance of this Agreement will be limited to the total monies actually received by Byte9 from the Customer under this Agreement during the 12 months preceding the date on which the claim arose.

26. Termination

26.1 This Agreement will commence on Effective Date and continue until the terminated in accordance with this clause 26.

26.2 Without prejudice to either party’s other rights or remedies, either party may terminate this Agreement for any reason on 90 days’ written notice to the other party, such notice not to expire prior to the end of the later of any Application Support Period, Retained Development Period, or Hosting Support Period then in effect.

26.3 Without prejudice to either party’s other rights or remedies, this Agreement can be terminated by:

26.3.1 either party immediately on written notice if the other party:

(a) commits a material breach of any of the terms of this Agreement and (if such a breach is remediable) fails to remedy that breach within 30 days of that party being notified in writing of the breach; or

(b) to the extent permitted by law, ceases trading (or threatens to cease trading); is subject to an order for winding up; has an administrator or liquidator appointed (or such appointment is entitled or is requested in good faith); becomes insolvent; is incapable of paying its debts as they fall due; or makes any arrangement with its creditors for the payment of its debts.

26.3.2 Byte9 immediately on written notice if the Customer fails to pay any invoice within 14 days of its due date.

26.4 On termination of this Agreement for any reason:

26.4.1 the Customer will no longer have a right to access, and will stop accessing, the Proprietary Plugins;

26.4.2 any licenses granted by Byte9 under this Agreement will terminate;

26.4.3 any Application Support Period, Hosting Support Period or Retained Development Period then in effect will terminate;

26.4.4 other than Byte9’s material breach, all outstanding Fees will become immediately due and payable;

26.4.5 each party will return any property (and any copies) belonging to the other party; and

26.4.6 at the Customer’s request Byte9 will return or destroy of any Customer Material it possesses.

26.5 The accrued rights and remedies of the parties, and any clause intended to survive termination will survive termination of this Agreement for any reason.

27. Notices

27.1 Any notice required to be given under this Agreement will be in writing and will be:

27.1.1 delivered by hand or sent by pre-paid first-class post or recorded delivery post to the other party at its notice address set out on the Engagement Letter (or such other address as may have been notified); or

27.1.2 sent by email to the other party’s notice email address set out on the Engagement Letter.

27.2 A notice delivered by hand will be deemed to have been received when delivered (or if delivered outside Business Hours, at 9 am on the first Working Day following delivery). A correctly addressed notice sent by pre-paid first-class post or recorded delivery post will be deemed to have been received 2 Working Days after posting. A notice sent by email will be deemed to have been received on acknowledgement or demonstration of receipt by the receiving party.

28. Non-Competition

28.1 During the term of this Agreement and for 12 months after its expiry or termination, the Customer will not:

28.1.1 solicit, or seek to solicit, any Byte9 Personnel; or

28.1.2 entice, or seek to entice, any staff of Byte9 Personnel to transfer their services away from Byte9.

28.2 For the purposes of clause 28.1, the terms “solicit” and “entice” do not include searches for employees though general recruitment efforts or that are not otherwise focused on persons employed by Byte9.

29. Entire Agreement

29.1 This Agreement constitutes the whole agreement between the parties and supersedes any previous agreement between them.

29.2 Each party acknowledges that, in entering into this Agreement, it has not relied and does not rely on any statement, representation (whether innocent or negligent), assurance or warranty (a “Representation”) of any person (whether a party to this Agreement or not) other than as expressly set out in this Agreement.

29.3 Each party agrees that the only rights and remedies available to it arising out of or in connection with a Representation will be for breach of contract.

29.4 Nothing in this clause will limit or exclude any liability for fraud.

30. Arbitration

30.1 Any dispute arising out of or in connection with this contract, including any question regarding its existence, validity or termination, will be referred to and finally resolved by arbitration under the rules of the London Court of International Arbitration, which are deemed to be incorporated by reference into this clause 30.

30.2 The number of arbitrators will be one. The seat, or legal place, of arbitration will be London. The language to be used in the arbitral proceedings will be English and the governing law of the contract will be the substantive law of England and Wales.

31. General

31.1 No party will be in breach of this Agreement nor liable for any failure to perform its obligations under this Agreement if that failure results from circumstances beyond its reasonable control (a “Force Majeure Event”). If a Force Majeure Event continues for six months, the unaffected party may terminate this Agreement by giving 30 days’ written notice to the other party.

31.2 Byte9 may assign the benefit and subcontract the burden of this Agreement. The Customer may not assign the benefit or subcontract the burden of this Agreement without Byte9’s consent (not be withheld or delayed).

31.3 No variation of this Agreement will be effective unless it is in writing or as set out in the Engagement Letter.

31.4 If any provision (or part of a provision) of this Agreement is found to be invalid, unenforceable or illegal, the other provisions (or parts of any provisions) will remain in force.

31.5 A waiver of any right under this Agreement is only effective if it is in writing. Unless specifically provided otherwise, rights arising under this Agreement are cumulative and do not exclude rights provided by law.

31.6 Each party confirms it is acting on its own behalf and not for the benefit of any other person.

31.7 Nothing in this Agreement will be deemed to establish any partnership or joint venture between the parties, constitute a party the agent of the other party, nor authorise a party to make or enter into any commitments for or on behalf of the other party.

31.8 This Agreement may be signed in any number of counterparts but all counterparts will together constitute the same agreement.

31.9 This Agreement does not give rise to any rights under the Contracts (Rights of Third Parties) Act 1999 to enforce any term of this Agreement.

APPLICATION SUPPORT SCHEDULE

1 Terms

1.1 The following definitions apply to this Application Support Schedule and any other defined terms will have the meaning given to them elsewhere in the Agreement:

“Corrective Maintenance”

any amendments that are required to be made to the Software in order to resolve an Error and to ensure that the Software performs substantially in accordance with the Documentation and/or the Story.

“Critical Updates”

an update to the Software which is essential to the use of the Software or as required under the terms of this Agreement.

“Equipment”

any computer equipment on which the Software is installed and in operational use either in a test or production environment.

“Error”

any failure of the Software to perform in accordance with the Documentation and/or the Story.

“High Priority Fatal Error”

an issue which means a critical business function cannot be used causing potential revenue loss to the Customer, or which causes the Customer to breach any obligations they might have to customers as to service availability.

“Initial Response Time”

the period during the hours of 9.30 to 18.00 on a Working Day within which Byte9 will acknowledge receipt of an Issue Notification starting from the time Byte9 receives the Issue Notification from the Customer.

“Interim Report Period”

the period during the hours of 9.30 to 18.00 on a Working Day within which Byte9 will assign the Issue Notification a support issue reference and inform the Customer of the Corrective Maintenance to be undertaken. The Interim Report Period is measured from the time Byte9 receives the Issue Notification from the Customer.

“Low Priority Minor Error”

issues which cause an inability to perform a function properly but which have only a minor impact on the Customer’s ability to perform core business processes.

“Medium Priority Serious Error”

an issue which means that a business function cannot be used until the error is corrected but for which there are workarounds in place to avoid direct loss of revenue to the Customer.

2 Customer Contact

2.1 The Customer will notify Byte9 of any Errors with the Software (each such notification, a “Issue Notification”) using the reporting platform Gemini (available at http://support.thebyte9.com). Requests for Application Support Services made by any means other than Gemini will not be valid.

3 Corrective Maintenance

3.1 Byte9 will respond to an Issue Notification in accordance with the response times set out in clause 3.2 and perform Corrective Maintenance as required to resolve the Error.

3.2 Response times to an Issue Notification will be as follows:

Fatal Error

Initial Response Time: 4 hours

Interim Report Period: 8 hours

Serious Error

Initial Response Time: 4 hours

Interim Report Period: 28 hours

Minor Error

Initial Response Time: 4 hours

Interim Report Period: 52 hours

3.3 Byte9 will provide reasonable email and phone consultation to the Customer if the Errors fall within the scope of Corrective Maintenance.

4 Software Service Levels

4.1 Byte9 will use all reasonable endeavours to enable 99.9% availability of the Software. Performance is measured as a monthly average in arrears from the Effective Date and each month thereafter.

4.2 Calculation of availability will not extend to:

4.2.1 any scheduled outage of which the Byte9 has informed the Customer of in advance in writing;

4.2.2 any failure of any third-party products or services including Hosting Services;

4.2.3 equipment defects or repairs to or the supply of consumable items such as discs or tapes other than those supplied by Byte9;

4.2.4 modifications or additions to the servers, system set-up or network other than agreed in writing by between the parties; or

4.2.5 breaches of security or system integrity due to modification by a 3rd party unless agreed in writing by the parties.

5 Updates

5.1.1 Byte9 will without additional charge to the Customer:

5.1.2 supply and install Critical Updates issued generally by Byte9 to users of the Software after the Effective Date;

5.1.3 supply and install or Critical Updates as may be necessary to ensure that the Software operates to reflect any change in any applicable regulation, statute, law, code of conduct or necessary market practice which relates to the business of the Customer and which may be relevant from time to time;

5.1.4 supply physical documentation to the Customer detailing all changes that are contained within the Critical Updates

5.1.5 supply and install, in consultation with the Customer, Critical Update or patch issued by a third party software provider (such as an anti-virus software provider), or as otherwise necessary for the proper operation of the Software and website in accordance with the Documentation and/or the Story.; and

5.1.6 provide unlimited phone consultation to the Customer in respect of Critical Updates.

5.1.7 The Customer will test and use any Critical Updates within a timely period.

6 Excluded Application Support Services

6.1 Byte9 will be under no obligation to provide Application Support Services in respect of:

6.1.1 problems resulting from any modifications or customisation of the Software not approved in writing by Byte9;

6.1.2 any software other than the Software provided by Byte9 to the Customer under this Agreement;

6.1.3 breaches of security or system integrity due to modification of the Software by a third party unless approved in writing by Byte9;

6.1.4 any incorrect or unauthorised use of the Software, being a use not in accordance with the Documentation and/or the Story;

6.1.5 any fault in the Equipment;

6.1.6 any failure of any third party products or services or integrations with any such products or services unless this is due to a change implemented by Byte9; or

6.1.7 any programs used in conjunction with the Software.

Hosting Schedule

Byte9 will, in its own name, procure hosting services from Amazon Web Services, Inc. ("Amazon") for the hosting of the Software. Such services will be procured on the basis of Amazon’s standard terms of business from time to time. Amazon’s current standard terms of business can be found here:

· https://aws.amazon.com/agreement/

· https://aws.amazon.com/ec2/sla/

· https://aws.amazon.com/s3/sla/

· https://aws.amazon.com/rds/sla/

· https://aws.amazon.com/terms/

(the “Amazon Agreement”)

Byte9 will only be liable for the provision of Hosting Services to the Customer under this Agreement to the extent it itself receives such services from Amazon under the Amazon Agreement and to the extent Amazon accepts liability for the provision of such services under the Amazon Agreement.

The Customer agrees to comply with any terms or obligations applicable to end users of the Hosting Services as may be set out in the Amazon Agreement.

Hosting and Operating Environment Schedule

Browser Operating Environment:

· OS / Browser combinations tested (latest browser versions):

· Mac: Chrome; Firefox; Safari; Opera

· Windows: Chrome; Edge; Firefox; Opera

Hosting environment:

· The hosting services environment provided by a cloud services provider (which might include Amazon Web Services), in accordance with the Hosting Schedule.

Blaze Features Schedule

The Blaze Features made available to the Customer and other Blaze users as the Blaze Features Overview.

Blaze Trade Mark Schedule

The Blaze Trademark  entered into the UK Intellectual Property Office Register on the 13th August 2021 trademark UK00003419952