Document:

EXHIBIT
10.5

 

Software
Development Agreement

 

This
Software Development Agreement is made on May 4 2017 between aiDataSoft Inc, an Ontario corporation with its principal place of
business located at 180 Northfield Dr W #4 Waterloo, ON N2L0C7 (the “Developer”), and EvaMedia Corp a Delaware
corporation with its principal place of business located at 75 Broadway Suite 202 San Francisco.

 

The
parties agree as follows:

 

1.
Definitions. In addition to the terms defined above, the following definitions apply:

 

1.1.
“Confidential Information” means all material information, written or oral, that the Customer discloses or
makes available to the Developer directly through any means of communication.

 

1.2.
“Software” means websites, apps, and demand side platform, and all associated documentation and other instructions.

 

1.3.
“Specifications” has the meaning given to it in section 3.1.

 

2.
Software Development Services. The Customer engages the Developer, and the Developer agrees, to perform services for the
Customer to develop, deliver, install, and support and maintain the Software in accordance with the terms of this agreement.

 

3.
Developer’s Duties and Responsibilities

 

3.1.
Specifications. The Customer shall define the specifications, requirements, and deliverables (the “Specifications).

 

3.2.
Development. The Developer shall design, develop, and implement the Software in accordance with the Specifications.

 

3.3.
Delivery. The Developer shall use reasonable efforts to deliver the Software to the Customer in accordance with the Specifications.

 

3.4.
Installation. The Developer will be responsible for conducting all activities required to install the Software at the Customer’s
premises.

 

4.
Acceptance

 

4.1.
Acceptance Period. The Customer will have 7 days following the date of delivery OR installation to assess and test the
Software.

 

4.2.
Completion. If the Developer, in the Customer’s opinion, delivers the Software in accordance with the Specifications,
then the Developer will be deemed to have completed its delivery obligations.

 

4.3.
Rejection. If the Developer, in the Customer’s opinion, fails to deliver the Software in accordance with the Specifications,
the Customer shall detail in writing its grounds for rejection. In that case, the Developer shall promptly OR use reasonable efforts
to correct the Software, in which case upon delivery of the corrected Software, the process of acceptance testing will restart.

 

4.4.
Continued Failure. If the Developer’s corrections, in the Customer’s opinion, fail to deliver the Software
in accordance with the Specifications, then the Customer may elect to either terminate this agreement or adjust the Specifications
accordingly.

 

5.
Change Orders

 

5.1.
Changes. The Customer may at any time request changes to the Specifications.

 

    	 	 	 

     

    

 

5.2.
Additional Time or Expense. If the proposed change will, in the Developer’s reasonable opinion, require a delay in
the delivery OR installation of the Software or result in additional expense, then the Customer and the Developer shall confer.
The Customer may in that case elect to either

 

(a)
withdraw its proposed change, or

 

(b)
require the Developer to deliver the Software with the proposed change, subject to the delay or additional expense or both.

 

5.3.
Termination. If the Developer is unable to accept, or chooses not to accept, the change order, the Customer may terminate
the agreement upon notice to the Developer.

 

6.
Training

 

6.1.
Scope. The Developer shall provide the Customer with x number of hours of training OR such training as the Customer may
reasonably request on the use of the Software.

 

6.2.
Dates and Locations. The Developer shall conduct the training on the dates and at the locations that the parties agree
upon.

 

6.3.
Costs. The training Developer shall provide the training no additional cost.

 

7.
Support and Maintenance

 

7.1.
Initial Period. The Developer shall provide the Customer with support and maintenance services for one year following delivery
and acceptance.

 

7.2.
Renewal Periods. The Customer may renew its support and maintenance subscription after the initial subscription period
at the Developer’s then-current rates.

 

8.
Fees and Expenses

 

8.1.
Fees. The Customer shall pay the Developer as quoted for each project.

 

8.2.
Expenses. The Customer shall reimburse the Developer for all reasonable expenses that the Developer incurs in developing
the Software, but only if the Customer has given its prior approval to the expenses.

 

8.3.
Payment Due Date. A retainer of $20,000 will be paid before work begins. This retainer will be replenished once the billed
costs bring the retainer held to a level under $1000.

 

8.4.
Late Payments. Any amount not paid when due will bear interest from the due date until paid at a rate equal to 1% per month
12.68% annually or the maximum allowed by law, whichever is less.

 

9.
Term. This agreement will begin on May 5 2017 and will continue indefinitely, unless terminated earlier.

 

10.
Representations. The Developer represents and warrants to the Customer as follows, acknowledging that the Customer is relying
on these representations and warranties:

 

10.1.
Right to Assign. The Developer is the sole author of the Software and has, and will have, the authority to assign rights
to the Software to the Customer under this agreement.

 

10.2.
No Infringement. The Developer’s use of the Software will not infringe upon the intellectual property, contractual,
or other proprietary or personal rights of any person.

 

    	 	 	 

     

    

 

11.
Warranties

 

11.1.
Limited Media Warranty. The Developer warrants that, for a period of MEDIA WARRANTY PERIOD following delivery of the Software,
the media upon which the Software is delivered will be free from defects in materials and workmanship under normal use.[ The Developer’s
sole obligation in this regard will be to provide the Customer with a performing copy of the Software within a reasonable time
following the Customer’s written notice to the Developer of the defect.]

 

11.2.
Limited Support Warranty. For a period of SUPPORT WARRANTY PERIOD following the delivery OR installation of the Software,
the Developer shall perform its maintenance and support services consistent with generally accepted industry standards, but only
if the Software is installed and operated in accordance with the Developer’s documentation and other instructions.

 

11.3.
Limited Performance Warranty. The Developer warrants that, for a period of PERFORMANCE WARRANTY PERIOD starting on the
date of delivery OR installation of the Software, the Software will perform substantially in accordance with the functional specifications
set forth in the documentation, but only if the Software is installed and operated in accordance with the Developer’s documentation
and other instructions.

 

12.
Acknowledgments

 

12.1.
Independent Contractor. The Developer is an independent contractor. Nothing contained in this agreement creates a partnership,
joint venture, employer/employee, principal-and-agent, or any similar relationship between the parties.

 

12.2.
Proprietary Rights. The parties acknowledge that the development of the Software is “work for hire” within
the meaning of the Copyright Act of 1976, as amended on one or more occasions, and that the Software will be the Customer’s
sole property.

 

12.3.
Consent to Use of Data. The Developer may collect and use technical information gathered as part of its support services,
but may only use this information to improve its products and services. The Developer shall not disclose this any of this information
in a form that personally identifies the Customer or it clients.

 

12.4.
Government End Users. If the Software and related documentation are supplied to or purchased by or on behalf of the United
States Government, then the Software is deemed to be “commercial software” as that term is used in the Federal Acquisition
Regulation system. The rights of the United States will not exceed the minimum rights set forth in FAR 52.227-19 for “restricted
computer software”. All other terms and conditions of this agreement otherwise apply.

 

13.
Confidentiality

 

13.1.
Confidentiality Obligations. During the term of this agreement and for 2 years afterward, the Developer shall hold all
Confidential Information in confidence in accordance with the terms of this agreement.

 

13.2.
Use Solely for Purpose. The Developer shall use the Confidential Information in accordance with, and solely for the purpose
of providing its services under, the terms of this agreement.

 

14.
Source Code Escrow

 

14.1.
Delivery of Object Code. The Developer shall deliver the Software to the Customer in object code form only.

 

14.2.
Escrow of Source Code. The Developer shall deposit one copy of the source code version of the Software with an escrow agent
specializing in software escrows, to be mutually agreed upon in writing by the parties after good faith negotiation.

 

14.3.
Delivery and Update of Source Code. The Developer shall deliver the source code to the escrow agent within SOURCE CODE
DELIVERY DAYS days after its delivery of the object code to the Customer.

 

    	 	 	 

     

    

 

Thereafter,
the Developer shall deposit with the escrow agent the source code version of all updates to, enhancements of, and modifications
to the Software created by the Developer on the Customer’s behalf.

 

14.4.
Payment of Escrow Fees. The Customer shall pay all fees necessary to establish and maintain the escrow.

 

14.5.
Contingent License. The Developer hereby grants to the Customer a contingent license to receive the source code from the
escrow agent and to use the source code to support its use of the Software in machine- readable form if one or more of the following
events occurs:

 

(a)
the Developer fails to fulfill its obligations to maintain the Software as provided in this agreement,

 

(b)
the Developer, whether directly or through a successor or affiliate, ceases to be in the software business,

 

(c)
the Developer becomes insolvent or admits insolvency or a general inability to pay its debts as they become due,

 

(d)
the Developer files a petition for protection under the U.S. Bankruptcy Code, or an involuntary petition is filed against it and
is not dismissed within [60] days, or

 

(e)
the Developer comes under the control of a competitor of the Customer.

 

15.
Assignment of Rights. Upon acceptance of the Software and payment of all compensation due to the Developer, the Developer
agrees to grant and assign, and hereby grants and assigns, to the Customer its entire interest in the Software (including all
intellectual and other property rights).

 

16.
Indemnification

 

16.1.
Developer’s Indemnity. The Developer shall indemnify the Customer and its officers, directors, employees, agents,
and affiliates, against all claims, liability, costs, and expenses (including attorneys’ fees) arising from any third party
claim or proceeding against the Customer

 

(a)
based on any claim that the Software [or any services performed under this agreement] infringes or violates any intellectual or
other property right, or

 

(b)
that alleges any negligent act or omission or willful conduct of the Developer or its directors, officers, employees, agents,
or affiliates.

 

16.2.
Notice of Claim. The Customer shall give prompt written notice to the Developer of any claim or potential claim for indemnification
under this agreement.

 

16.3.
Exclusive Remedies. The rights granted under this section 16 (Indemnification) are the exclusive remedies available under
this agreement in connection with the claims and losses that this section addresses.

 

17.
Limitation of Liability. Neither party will be liable for breach-of-contract damages that the breaching party could not
reasonably have foreseen on entering into this agreement.

 

18.
Termination

 

18.1.
Termination upon Notice. Either party may terminate this agreement for any reason upon TERMINATION FOR CONVENIENCE NOTICE
days’ Notice to the other party.

 

18.2.
Termination for Cause. If either party

 

(a)
commits a material breach or material default in the performance or observance of any of its obligations under this agreement,
and

 

    	 	 	 

     

    

 

(b)
the breach or default continues for a period of [CURE PERIOD] after delivery by the other party of written notice reasonably detailing
such breach or default, then

 

the
non-breaching or non-defaulting party may terminate this agreement, with immediate effect, upon written notice to the breaching
or defaulting party.

 

18.3.
Termination upon Insolvency. This agreement will terminate immediately upon the Developer’s insolvency, bankruptcy,
receivership, dissolution, or liquidation.

 

18.4.
Effect of Termination

 

(a)
Termination for Customer’s Breach. In the event of termination of this agreement due to a material breach or default
committed by the Customer,

 

(i)
the assignment of rights to the Customer in this agreement will terminate, and

 

(ii)
the Customer shall immediately stop using the Software and destroy or erase all copies in its possession or control.

 

(b)
Termination for any other Reason. In the event of termination of this agreement for any other reason,

 

(i)
the Customer will not be required to make payment for any Deliverables that the Customer had not accepted,

 

(ii)
the Customer will continue to exercise all rights to the Software that it has acquired under this agreement,

 

(iii)
the Developer shall immediately deliver to the Customer all Software, documentation, source code, and other Customer property
in its possession relating to the Software and then destroy all copies in its possession or control, and

 

(iv)
the Customer shall pay the Developer for all services rendered and work performed up to the effective date of termination, unless
the Customer has terminated for cause, in which case it will only be required to pay fair value. The Developer shall provide the
Customer with an invoice for its fees within [30] days of the effective date of the termination, and the Client shall pay the
invoice within [14] days of receipt.

 

19.
General

 

19.1.
Entire Agreement. This agreement contains all the terms agreed to by the parties relating to its subject matter. It replaces
all previous discussions, understandings, and agreements.

 

19.2.
Amendment. This agreement may only be amended by a written document signed by both parties.

 

19.3.
Assignment. The Developer may not assign this agreement or any of its rights under it. The Customer may assign this agreement
or any of its rights without notice or the need for the Developer’s consent.

 

19.4.
Remedies Cumulative. Except as provided in section 16.3 (Exclusive Remedies), the rights and remedies available to a party
under this agreement are cumulative and in addition to, not exclusive of or in substitution for, any rights or remedies otherwise
available to that party.

 

    	 	 	 

     

    

 

19.5.
Survival. Sections 13 (Confidentiality), 14 (Source Code Escrow), 15 (Assignment of Rights), 16 (Indemnification), 17 (Limitation
of Liability), and 18.4 (Effect of Termination) survive the termination or expiration of this agreement.

 

19.6.
Severability. If any part of this agreement is declared unenforceable or invalid, the remainder will continue to be valid
and enforceable.

 

19.7.
Waiver. A party’s failure or neglect to enforce any of rights under this agreement will not be deemed to be a waiver
of that party’s rights.

 

19.8.
Governing Law. This agreement will be governed by and construed in accordance with the laws of the State of California,
without regard to its conflict of laws rules.

 

19.9.
Dispute Resolution

 

(a)
Arbitration. Any dispute or controversy arising under or in connection with this agreement will be settled exclusively
by arbitration in California, in accordance with the rules of the American Arbitration Association then in effect by 2 arbitrators.

 

(b)
No Punitive Damages. The arbitrators will not have the power to award punitive damages.

 

(c)
Judgment. The successful party may enter the arbitral judgment in any court having jurisdiction.

 

19.10.
Waiver of Jury Trial. The parties waive their respective rights to trial by jury in any action or proceeding involving
this agreement or the transactions relating to its subject matter.

 

19.11.
Headings. The headings used in this agreement and its division into sections and other subdivisions do not affect its interpretation.

 

19.12.
Counterparts. This agreement may be signed in any number of counterparts, each of which is an original and all of which
taken together form one single document.

 

19.13.
Effectiveness of Agreement. This agreement is effective as of the date shown at the top of the first page, even if any
signatures are made after that date.

 

This
agreement has been

 

signed
by the parties. ai DataSoft Inc

 

By:

Name:
Daryl Walser Title: CTO

Date
May 4 2017

 

EvaMedia
Corp

 

By:

Name:
David Boulette CEO

Date
May 4 2017

 

Schedule
A: Software Specifications,

Requirements, and Deliverables N/AMaximum Anniversary Value Death Benefit Rider

This rider forms a part of the Base Contract to which it is attached and is effective on the Issue Date shown on the Maximum Anniversary Value Death Benefit Contract Schedule.  In the case of a conflict with any provision in the Base Contract, the provisions of this rider control.  Defined terms and contractual provisions are set forth in the Base Contract or are added in this rider.  This is a first-to-die rider that terminates as indicated under the Termination of this Rider section.

	
Definitions

Base Contract

The contract to which this rider is attached.

Charge Base

We base the Rider Fee on the Charge Base.  On the Issue Date, the Charge Base is equal to the Initial Purchase Payment.  On each Quarterly Contract Anniversary, or the next Business Day if the Quarterly Contract Anniversary is not on a Business Day, the Charge Base is equal to the Contract Value.

At the end of each Business Day, we:

	
·

	
Increase the Charge Base by the amount of any Additional Purchase Payments received that day; and

	
·

	
Reduce the Charge Base proportionately by the percentage of any Contract Value withdrawn that day, including any Withdrawal Charge, and Transfer Fee, if any, and Contract Charges.

Daily Transactions

On each Business Day, any Additional Purchase Payments received, Withdrawals taken, including any Withdrawal Charge, credits applied, and Contract Charges and Transfer Fees, if any, deducted.

End Date

The End Date occurs on the earlier of:

	
·

	
the Business Day we receive the first Valid Claim from any one Beneficiary; or

	
·

	
the older Determining Life's Maximum Anniversary Value Death Benefit Maximum Birthday shown on the Maximum Anniversary Value Death Benefit Contract Schedule.

Determining Life (Lives)

The person(s) on whose life (lives) we base the Maximum Anniversary Value Death Benefit.  We determine the Determining Life (Lives) on the Issue Date.

After we issue this contract, you cannot add, remove or replace a Determining Life.

	
·

	
If the Base Contract is solely owned, the Determining Life is the Owner.

	
·

	
If the Base Contract is owned by a non-individual, the Determining Life is the Annuitant.

	
·

	
If the Base Contract is jointly owned, the Determining Lives are the joint Owners.

If we remove a person as a Joint Owner due to divorce, that person no longer qualifies as a Determining Life and we remove him or her as such from this rider.

For jointly owned non-qualified contracts, if you establish a trust and change ownership to the trust, the prior Owner who is not the Annuitant no longer qualifies as a Determining Life and we remove him or her as such from this rider.

Maximum Anniversary Value

A calculation we use in determining the Maximum Anniversary Value Death Benefit.

Quarterly Contract Anniversary

A three-month anniversary of the Issue Date or any subsequent three-month Quarterly Contract Anniversary.

S40897-NF                                                     [Admin Tracking Identifier]

	
Death Benefit

The following is replacing the "Death Benefit" provision under the "Death Benefit" section of the Base Contract. If this rider terminates, we revert back to the "Death Benefit" provision in the Base Contract.

Maximum Anniversary Value Death Benefit

The Maximum Anniversary Value on the Issue Date is equal to the Purchase Payment received on the Issue Date.

At the end of each Business Day we:

	
·

	
increase the Maximum Anniversary Value by the amount of any Additional Purchase Payments received that day, and

	
·

	
reduce the Maximum Anniversary Value proportionately by the percentage of Contract Value withdrawn that day, including any Withdrawal Charge.

Before the End Date, on the Index Effective Date and each Index Anniversary thereafter, or on the next Business Day if the Index Anniversary is not on a Business Day, the Maximum Anniversary Value is equal to the greater of:

	
(a)

	
 its current value after processing any Additional Purchase Payments or Withdrawals; or

	
(b)

	
 the Contract Value after processing any Daily Transactions.

If your Index Effective Date is the same day as your Issue Date, the Maximum Anniversary Value on the Index Effective Date is equal to the Purchase Payment received on the Issue Date.

We no longer make this comparison on or after the End Date.

During the Accumulation Phase, if you (the Owner, or Annuitant if the Owner is a non-individual) are a Determining Life  and you die, or if you die simultaneously with a Determining Life (Lives), the Maximum Anniversary Value Death Benefit is equal to the greater of (a) or (b).

	
(a)

	
The Contract Value.

	
(b)

	
The Maximum Anniversary Value.

	
·

	
For a sole Beneficiary, we determine the Maximum Anniversary Value at the end of the Business Day we receive a Valid Claim from the Beneficiary.

	
·

	
For multiple Beneficiaries, we determine the Maximum Anniversary Value for each surviving Beneficiary's portion of the Maximum  Anniversary Value Death Benefit at the end of the Business Day we receive the first Valid Claim from any one Beneficiary.  We determine the Contract Value for each surviving Beneficiary's portion of the Maximum Anniversary Value Death Benefit as of the end of the Business Day we receive his or her Valid Claim.

However, if you (the Owner, or Annuitant if the Owner is a non-individual) and the Determining Life (Lives) are different individuals:

	
·

	
If the Determining Life dies before you, we compare the Contract Value and Maximum Anniversary Value determined at the end of Business Day we receive due proof of a Determining Life's death. If your Contract Value is less than the Maximum Anniversary Value, we increase your Contract Value to equal the Maximum Anniversary Value.

	
·

	
If you die before a Determining Life, the Maximum Anniversary Value Death Benefit is unavailable and instead your Beneficiary(s) will receive the Death Benefit described in the Base Contract.

Any part of the Death Benefit that is in the subaccounts, if any, remains there until distributed.

	
Ownership

The following is added to the "Assignment of this Contract" and "Change of Ownership" provisions under the "Ownership" section of the Base Contract.

Assignment of this Contract

An assignment does not change any Determining Life, except as described under the definition of "Determining Life (Lives)".

Change of Ownership

A change of ownership does not change any Determining Life, except as described under the definition of "Determining Life (Lives)".

S40897-NF 2                                                    [Admin Tracking Identifier]

	
Contract Charges

The following is added to the "Contract Charges" section of the Base Contract.

Rider Fee

The Rider Fee for this rider is shown on the Maximum Anniversary Value Death Benefit Contract Schedule.

The Rider Fee is assessed as a percentage of the Charge Base as an annualized rate that we accrue each day during the Accumulation Phase and when paying the Death Benefit as noted under Death Benefit provision of this rider.  If any day that we are to accrue this charge is not a Business Day, we use the Charge Base at the end of the previous Business Day. We deduct the Rider Fee for each quarter on the earlier of the following: (a) the next Quarterly Contract Anniversary, or the next Business Day if the next Quarterly Contract Anniversary is not a Business Day; or (b) when we deduct the final Rider Fee.  We deduct the Rider Fee from the Contract Value on each Quarterly Contract Anniversary (or the next Business Day if the Quarterly Contract Anniversary is not on a Business Day) before we use that Contract Value to compute any guaranteed value(s) under this contract.

When we deduct the Rider Fee, we deduct it proportionately from each Allocation Option.  The deduction of the Rider Fee reduces the Contract Value.  The deduction of the Rider Fee does not reduce the amount we use to determine the Free Withdrawal Privilege or the Withdrawal Charge Basis, and is not treated as a Withdrawal when calculating the guaranteed value(s) provided by the Death Benefit.

We deduct the final Rider Fee on the earlier of the Business Day this rider terminates or we receive the first Valid Claim from any one Beneficiary.  However, if on a Quarterly Contract Anniversary the Contract Value is less than the Rider Fee, we deduct any remaining Contract Value to cover the final Rider Fee and reduce the Contract Value to zero.

We will no longer charge the Rider Fee for this rider on the earlier of the Business Day:

	
·

	
this rider terminates; or

	
·

	
we receive the first Valid Claim from any one Beneficiary.

	
Termination of this Rider

This rider terminates on the earliest of the following.

	
·

	
The Business Day that the Maximum Anniversary Value and the Contract Value are both zero.

	
·

	
The Business Day before the Annuity Date.

	
·

	
Upon the death of a Determining Life, the end of the Business Day we receive a Valid Claim from all Beneficiaries, if the Determining Life is the Owner (or Annuitant if the Owner is a non-individual) or if the Determining Life dies simultaneously with the Owner.

	
·

	
Upon the death of a Determining Life, the end of the Business Day we receive due proof of a Determining Life's death, if the Determining Life is no longer an Owner (or Annuitant if the Owner is a non-individual).

	
·

	
Upon the death of an Owner (or Annuitant if the Owner is a non-individual), the end of the Business Day we receive the first Valid Claim from any one Beneficiary, if the Owner is no longer a Determining Life.

	
·

	
The Business Day that the Base Contract terminates.

In all other respects the provisions, conditions, exceptions and limitations contained in the Entire Contract remain unchanged.

Signed for the Company at its home office.

Allianz Life Insurance Company

of North America

[ ]

[Gretchen Cepek] [Walter R. White]

Secretary  President

S40897-NF 3                                                   [Admin Tracking Identifier]

 

	
Maximum Anniversary  Value Death Benefit Contract Schedule

Owner:                [John Doe] Contract Number:               [??687456]

[Joint Owner:   [Jane Doe]] Issue Date:                             [04/15/10]

Annuitant:         [John Doe]

End Date

Maximum Anniversary Value Death Benefit Maximum Birthday:                      [91st] birthday

Contract Charges

Rider Fee: [0.15]%

S40898-NF                                                      [Admin Tracking Identifier]

Source: [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00277-of-00352.parquet"}, [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00277-of-00352.parquet"}]]