[{"data":1,"prerenderedAt":522},["ShallowReactive",2],{"document-source-code-trust-agreement-development-D812":3},{"document":4,"label":21,"preview":11,"thumb":22,"thumb600":23,"description":5,"descriptionCustom":6,"apiDescription":5,"pages":8,"extension":10,"parents":24,"breadcrumb":28,"related":36,"customDescModule":174,"customdescription":6,"mdFm":175,"mdProseHtml":521},{"description":5,"descriptionCustom":6,"label":7,"pages":8,"size":9,"extension":10,"preview":11,"thumb":12,"svgFrame":13,"seoMetadata":14,"parents":15,"keywords":20},"SOURCE CODE TRUST AGREEMENT This Source Code Trust Agreement (the \"Agreement\") is effective [DATE], BETWEEN: [YOUR COMPANY NAME] (the \"Company\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [COMPANY NAME] (the \"Trustee\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [COMPANY NAME] (the \"Licensee\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] WHEREAS Company, in partial consideration of Licensee agreeing to enter into a license agreement (the \"License Agreement\") for the use of a computer software program [developed and] owned by Company known as (the \"Software\"), has agreed to enter into this agreement which will make available to Licensee the source code of the Software [and certain related materials required for the maintenance and support of the Software] (the \"Trust Materials\", as more particularly described in Section 1) in certain circumstances as more particularly described herein; WHEREAS Licensee acknowledges and agrees that, as an integral part of maintaining the value of the trade secrets and other proprietary interests associated with the Software, the Licensee's access to, and use of, the Trust Materials shall be expressly limited as more particularly described herein; WHEREAS as between them, Company and the Licensee acknowledge that this agreement reflects a reasonable balance of their respective needs and concerns respecting access to, and the use of, the Trust Materials; WHEREAS the foregoing representations and statements of fact are made by Company and Licensee and not by the Trustee; WHEREAS Company and the Licensee have requested that the Trustee and the Trustee has agreed to, assist in the arrangements as set forth in this agreement; IN CONSIDERATION of the foregoing Background, the mutual covenants in this agreement, and other good and valuable consideration (the receipt and sufficiency of which are acknowledged), the parties agree as follows: DEFINITIONS In this Agreement, except where the context or subject matter is inconsistent therewith, the following terms shall have the following meanings: \"Agreement\" means this Source Code Trust Agreement and all schedules annexed to this agreement as the same may be amended from time to time in accordance with the provisions hereof; \"hereof\", \"hereto\" and \"hereunder\" and similar expressions refer to this Agreement and not to any particular article or section; and \"Section\" or \"paragraph\" refers to the specified article or section of this Agreement; \"Business Day\" means any day, other than a Saturday, Sunday, statutory or civic holiday in [STATE/PROVINCE]; \"Court\" means the [STATE/PROVINCE] Courts; \"Deposit\" means either an Initial Deposit or Subsequent Deposit; \"Event of Default\" means any one or more of the events set out in paragraph 6.1; \"Initial Deposit\" has the meaning attributed to it in paragraph 4.1; \"License Agreement\" means the license agreement dated, [YEAR] in which Company licensed the use of the Software to the Licensee, as amended from time to time in accordance with its terms; \"Licensee's Certificate\" means a certificate in the form attached as Schedule A hereto executed by any [NUMBER] senior officers of the Licensee; \"Notice Period\" means the [NUMBER] Business Day period of time commencing on the date the Trustee notifies Company that an Event of Default has occurred; \"Parties\" means Company, the Trustee and the Licensee collectively and \"Party\" means any one of them; \"Person\" includes an individual, body corporate, partnership, joint venture, trust, unincorporated organization, the Crown or any agency or instrumentality thereof or any other entity recognized by [YOUR COUNTRY LAW]; \"Software\" means, at any time, that version of the computer software then licensed to the Licensee under the License Agreement [including that version of any associated compiler programs, utility programs and library functions, including all corrections, changes, improvements and enhancements thereto] as more particularly described in Schedule B hereto; \"Company's Certificate\" means a certificate in the form attached as Schedule C hereto executed by any [NUMBER] senior officers of Company; \"Source Code\" means a complete copy of the source code version of the Software, appropriately labeled to denote the version or release thereof, and the currency date thereof, in each of: machine-readable form on machine-readable storage medium suitable for long term storage and compatible with the computer system then being used by the Licensee and which, when compiled, will produce the object code version of the Software; and human-readable form with annotations in the [English] language on bond paper suitable for long term archival storage; \"Subsequent Deposit\" has the meaning attributed to it in paragraph 4.2; \"Software Documentation\" means a complete copy, in [LANGUAGE], printed on bond paper, suitable for long term archival storage, and appropriately labeled to describe the contents thereof, of all applicable documentation and other explanatory materials including programmer's notes, technical or otherwise, for the Software as may be required by the Licensee, using a competent computer programmer possessing ordinary skills and experience, to further develop, maintain and operate the Software without further recourse to Company including, but not necessarily limited to, general flow-charts, input and output layouts, field descriptions, volumes and sort sequence, data dictionary, file layouts, processing requirements and calculation formula and the details of all algorithms and which shall be deemed to include those materials, as revised from time to time, set out in Schedule D; and \"Trust Materials\" means, at any particular time, those copies of the Source Code and Software Documentation which are deposited in trust with the Trustee hereunder. SETTLEMENT OF TRUST Company transfers to the Trustee, in trust, all legal title in and to the physical copies of the Trust Materials provided to Trustee from time to time in accordance with the terms of this Agreement. It is acknowledged by the Parties that such transfer by Company to Trustee under this paragraph is not intended to, nor does it, transfer any copyright or other intangible or intellectual property rights in the Trust Materials. The Trustee agrees to hold the Trust Materials in trust for the Licensee and Company as provided in this Agreement. Except as otherwise provided herein, the Trustee shall hold and preserve the Trust Materials in a safe and secure manner appropriate for valuable assets similar in nature to the Trust Materials in a separate container, appropriately segregated from materials which do not form part of the subject matter of this Agreement at a location within the boundaries of [COUNTRY/STATE/PROVINCE]. [The Trustee agrees that both the temperature and the humidity of the environment of the storage area are controlled within the parameters set out in Schedule E, and agrees to bear all risks of damage to the Trust Materials arising from any lack of such control.] The Trustee recognizes and agrees that the Trust Materials are the valuable assets and proprietary and confidential information of Company and agrees to hold them in strict confidence and to take all appropriate and reasonable actions to preserve their confidentiality. Except as expressly provided for in this Agreement, the Trustee agrees that it will not use, copy or disclose the Trust Materials to any Person, in any manner, without the prior written consent of Company. GRANT OF LICENSE",null,"Source Code Trust Agreement Development","18",117,"doc","https://templates.business-in-a-box.com/imgs/1000px/source-code-trust-agreement_development-D812.png","https://templates.business-in-a-box.com/imgs/250px/812.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#812.xml",{"title":6,"description":6},[16,19],{"label":17,"url":18},"Software & Technology","/templates/software-technology-business/",{"label":17,"url":18},"source code trust agreement development","Source Code Trust Agreement Development Template","https://templates.business-in-a-box.com/imgs/400px/812.png","https://templates.business-in-a-box.com/imgs/600px/812.png",[25,16,19],{"label":26,"url":27},"Templates","/templates/",[29,30,33],{"label":26,"url":27},{"label":31,"url":32},"Legal Agreements","/templates/business-legal-agreements/",{"label":34,"url":35},"Intellectual Property & Licensing","/templates/intellectual-property-and-licensing/",[37,41,45,49,53,57,61,65,69,73,77,81,85,100,117,132,148,162],{"label":38,"url":39,"thumb":40,"extension":10},"Source Code Trust Agreement 2","/template/source-code-trust-agreement-2-D810","https://templates.business-in-a-box.com/imgs/250px/810.png",{"label":42,"url":43,"thumb":44,"extension":10},"Source Code Trust Agreement Licensed Program","/template/source-code-trust-agreement-licensed-program-D813","https://templates.business-in-a-box.com/imgs/250px/813.png",{"label":46,"url":47,"thumb":48,"extension":10},"Source Code License Agreement","/template/source-code-license-agreement-D807","https://templates.business-in-a-box.com/imgs/250px/807.png",{"label":50,"url":51,"thumb":52,"extension":10},"Source Code Escrow Agreement","/template/source-code-escrow-agreement-D806","https://templates.business-in-a-box.com/imgs/250px/806.png",{"label":54,"url":55,"thumb":56,"extension":10},"Source Code License Agreement Short Form","/template/source-code-license-agreement-short-form-D809","https://templates.business-in-a-box.com/imgs/250px/809.png",{"label":58,"url":59,"thumb":60,"extension":10},"Voting Trust Agreement","/template/voting-trust-agreement-D926","https://templates.business-in-a-box.com/imgs/250px/926.png",{"label":62,"url":63,"thumb":64,"extension":10},"Source Code License Agreement Fully Paid-Up, Royalty Free","/template/source-code-license-agreement-fully-paid-up-royalty-free-D808","https://templates.business-in-a-box.com/imgs/250px/808.png",{"label":66,"url":67,"thumb":68,"extension":10},"Development and Publishing Agreement","/template/development-and-publishing-agreement-D5190","https://templates.business-in-a-box.com/imgs/250px/5190.png",{"label":70,"url":71,"thumb":72,"extension":10},"Economic Development Agreement","/template/economic-development-agreement-D13006","https://templates.business-in-a-box.com/imgs/250px/13006.png",{"label":74,"url":75,"thumb":76,"extension":10},"Web Site Development and Service Agreement","/template/web-site-development-and-service-agreement-D5181","https://templates.business-in-a-box.com/imgs/250px/5181.png",{"label":78,"url":79,"thumb":80,"extension":10},"Joint Development Agreement Standard","/template/joint-development-agreement-standard-D887","https://templates.business-in-a-box.com/imgs/250px/887.png",{"label":82,"url":83,"thumb":84,"extension":10},"Development Agreement General","/template/development-agreement-general-D789","https://templates.business-in-a-box.com/imgs/250px/789.png",{"description":86,"descriptionCustom":6,"label":87,"pages":88,"size":89,"extension":10,"preview":90,"thumb":91,"svgFrame":92,"seoMetadata":93,"parents":94,"keywords":98,"url":99},"CUSTOM SOFTWARE DEVELOPMENT AGREEMENT This Custom Software Development Agreement (the \"Agreement\") is made and effective [DATE], BETWEEN: [CUSTOMER NAME] (the \"Customer\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [YOUR COMPANY NAME] (the \"Developer\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] RECITALS WHEREAS Customer wishes to [DESCRIBE NEEDS TO BE ADDRESSED], and wants to hire Developer to develop these custom software packages, and; WHEREAS Developer desires to develop these custom software packages for Customer: NOW, THEREFORE, in consideration of the mutual covenants and agreements herein contained, the parties hereto, intending, to be legally bound, agree as follows: Purpose of Agreement Customer desires to retain Developer as an independent contractor to develop the computer software (the \"Software\") described in the Functional Specifications contained in Exhibit A attached to and made part of this Agreement. Developer is ready, willing and able to undertake the development of the Software and agrees to do so under the terms and conditions set forth in this Agreement. Preparation of Development Plan Developer shall prepare a development plan (\"Development Plan\") for the Software, satisfying the requirements set forth in the Functional Specifications. The Development Plan shall include: Detailed Specifications for the Software; A listing of all items to be delivered to Customer under this Agreement (\"Deliverables\"); A delivery schedule containing a delivery date for each Deliverable; and A payment schedule setting forth the amount and time of Developer's compensation. ACCEPTANCE OF DEVELOPMENT PLAN Developer shall deliver the Development Plan to Customer by [DEVELOPMENT PLAN DEADLINE]. Customer shall have [NUMBER] days to review the Development Plan. Upon approval of the Development Plan by Customer, it will be marked as Exhibit B and will be deemed by both parties to have become a part of this Agreement and will be incorporated by reference. Developer shall then commence development of Software that will substantially conform to the requirements set forth in the Development Plan. If the Development Plan is in Customer's reasonable judgment unsatisfactory in any material respect, Customer shall prepare a detailed written description of the objections. Customer shall deliver such objections to Developer within [NUMBER] days of receipt of the Development Plan. Developer shall then have [NUMBER] days to modify the Development Plan to respond to Customer's objections. Customer shall have [NUMBER] days to review the modified Development Plan. If Customer deems the modified Development Plan to be unacceptable, Customer has the option of terminating this Agreement upon written notice to Developer or permitting Developer to modify the Development Plan again under the procedure outlined in this paragraph. If this Agreement is terminated, the obligations of both parties under it shall end except for Customer's obligation to pay Developer all sums due for preparing the Development Plan and the ongoing obligations of confidentiality set forth in the provision of this Agreement entitled \"Confidentiality.\" Payment for Development Plan If the Development Plan is not accepted by Customer and Customer terminates this Agreement, Developer shall be entitled to compensation on a time and materials basis at an hourly rate of [HOURLY RATE] plus expenses to the date of termination. Developer shall submit an invoice detailing its time and expenses preparing the Development Plan. If the invoice amount is less than the amounts paid to Developer prior to termination, Developer shall promptly return the excess to Customer. If the invoice amount exceeds the amounts paid to Developer prior to termination, Customer shall promptly pay Developer the difference. However, Developer's total compensation for preparing the Development Plan shall not exceed [AMOUNT]. Payment [TIME AND MATERIALS AGREEMENT] Developer shall be compensated at the rate of [RATE] per hour [OR \"day,\" \"week,\" \"month\"]. Payment will be made within [NUMBER OF DAYS] days of Developer's submission of an invoice for work completed. [OPTIONAL: \"Unless otherwise agreed upon in writing by Customer, Customer's maximum liability for all services performed during the term of this Agreement shall not exceed [MAXIMUM AMOUNT].\"] OR [FIXED PRICE AGREEMENT] The total contract price shall be set forth in the Development Plan. Customer shall pay the Developer the sum of [INITIAL AMOUNT] upon execution of this Agreement and the sum of [AMOUNT IF PLAN APPROVED] upon Customer's approval of the Development Plan. The remainder of the contract price shall be payable in installments according to the payment schedule to be included in the Development Plan. Each installment shall be payable upon completion of each project phase by Developer and acceptance by Customer in accordance with the provision of this Agreement entitled \"Acceptance Testing of Software.\" Payment of Developer's Costs Customer shall reimburse Developer for all out-of-pocket expenses incurred by Developer in performing services under this Agreement. Such expenses include, but are not limited, to: All communications charges Costs for providing conversion services for converting Customer's database Media costs Travel expenses other than normal commuting, including airfares, rental vehicles, and highway mileage in company or personal vehicles at [cents per mile] Other expenses resulting from the work performed under this Agreement. Developer shall submit an itemized statement of Developer's expenses. Customer shall pay Developer within [NUMBER] days from the date of each statement. Late Fees Late payments by Customer shall be subject to late penalty fees of [%] per month from the due date until the amount is paid. Materials Customer shall make available to Developer, at Customer's expense, the following materials, facilities and equipment: [LIST] These items will be provided to Customer by [DATE]. Changes in Project Scope If at any time following acceptance of the Development Plan by Customer, Customer should desire a change in Developer's performance under this Agreement that will alter or amend the Specifications or other elements of the Development Plan, Customer shall submit to Developer a written proposal specifying the desired changes. Developer will evaluate each such proposal at its standard rates and charges. Developer shall submit to Customer a written response to each such proposal within [NUMBER] working days following receipt thereof. Developer's written response shall include a statement of the availability of Developer's personnel and resources, as well as any impact the proposed changes will have on the contract price, delivery dates or warranty provisions of this Agreement. Changes to the Development Plan shall be evidenced by a \"Development Plan Modification Agreement.\" The Development Plan Modification Agreement shall amend the Development Plan appropriately to incorporate the desired changes and acknowledge any effect of such changes on the provisions of this Agreement. The Development Plan Modification Agreement shall be signed by authorized representatives of Customer and Developer, whereupon Developer shall commence performance in accordance with it. Should Developer not approve the Development Plan Modification Agreement as written, Developer will so notify Customer within [NUMBER] working days of Developer's receipt of the Development Plan Modification Agreement. Developer shall not be obligated to perform any services beyond those called for in the Development Plan prior to its approval of the Development Plan Modification Agreement.","Custom Software Development Agreement","16",116,"https://templates.business-in-a-box.com/imgs/1000px/custom-software-development-agreement-D787.png","https://templates.business-in-a-box.com/imgs/250px/787.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#787.xml",{"title":6,"description":6},[95,97],{"label":17,"url":96},"software-technology-business",{"label":17,"url":96},"custom software development agreement","/template/custom-software-development-agreement-D787",{"description":101,"descriptionCustom":6,"label":102,"pages":103,"size":104,"extension":10,"preview":105,"thumb":106,"svgFrame":107,"seoMetadata":108,"parents":110,"keywords":109,"url":116},"NON-DISCLOSURE AGREEMENT (NDA) This Non-Disclosure Agreement (the \"Agreement\") is made and effective [DATE], BETWEEN: [YOUR COMPANY NAME] (the \"Disclosing Party\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [RECEIVING PARTY NAME] (the \"Receiving Party\"), an individual with his main address located at OR a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] WHEREAS, Receiving Party has been or will be engaged in the performance of work on [DESCRIBE]; and in connection therewith will be given access to certain confidential and proprietary information; and WHEREAS, Receiving Party and Disclosing Party wish to evidence by this Agreement the manner in which said confidential and proprietary material will be treated. NOW, THEREFORE, it is agreed as follows: NON-DISCLOSURE OF CONFIDENTIAL INFORMATION Both Parties understand and agree that each Party may have access to the confidential information of the other party. For the purposes of this Agreement, \"Confidential Information\" means proprietary and confidential information about the Disclosing Party's (or it's suppliers') business or activities. Such information includes all business, financial, technical, and other information marked or designated by such Party as \"confidential\" or \"proprietary.\" Confidential Information also includes information which, by the nature of the circumstances surrounding the disclosure, ought in good faith to be treated as confidential. For the purposes of this Agreement, Confidential Information does not include: Information that is currently in the public domain or that enters the public domain after the signing of this Agreement. Information a Party lawfully receives from a third Party without restriction on disclosure and without breach of a non-disclosure obligation. Information that the Receiving Party knew prior to receiving any Confidential Information from the Disclosing Party. Information that the Receiving Party independently develops without reliance on any Confidential Information from the Disclosing Party. Each Party agrees that it will not disclose to any third Party or use any Confidential Information disclosed to it by the other Party except when expressly permitted in writing by the other Party. Each Party also agrees that it will take all reasonable measures to maintain the confidentiality of all Confidential Information of the other Party in its possession or control. TERM The term of this Agreement is [number] of [years/months] from the date of execution by both Parties. TITLE The Receiving Party agrees that all Confidential Information furnished by the Disclosing Party shall remain the sole property of the Disclosing Party. DISCLAIMER","Non Disclosure Agreement Nda","3",513,"https://templates.business-in-a-box.com/imgs/1000px/non-disclosure-agreement-nda-D12692.png","https://templates.business-in-a-box.com/imgs/250px/12692.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12692.xml",{"title":109,"description":6},"non disclosure agreement nda",[111,113],{"label":31,"url":112},"business-legal-agreements",{"label":114,"url":115},"Confidentiality Agreements","confidentiality-agreement","/template/non-disclosure-agreement-nda-D12692",{"description":118,"descriptionCustom":6,"label":119,"pages":120,"size":121,"extension":10,"preview":122,"thumb":123,"svgFrame":124,"seoMetadata":125,"parents":126,"keywords":130,"url":131},"INDEPENDENT CONTRACTOR AGREEMENT This Independent Contractor Agreement (\"Agreement\") is made and effective [Date], BETWEEN: [INDEPENDENT CONTRACTOR NAME] (the \"Independent Contractor\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [YOUR COMPANY NAME] (the \"Company\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] RECITALS Independent Contractor is engaged in providing [Describe] business services, its Employer Tax I.D. Number is [Insert], and its Business License Number is [insert]. Independent Contractor has complied with all Federal, State, and local laws regarding business permits, sales permits, licenses, reporting requirements, tax withholding requirements, and other legal requirements of any kind that may be required to carry out said business and the Scope of Work which is to be performed as an Independent Contractor pursuant to this Agreement. Independent Contractor is or remains open to conducting similar tasks or activities for clients other than the Company and holds themselves out to the public to be a separate business entity. Company desires to engage and contract for the services of the Independent Contractor to perform certain tasks as set forth below. Independent Contractor desires to enter into this Agreement and perform as an independent contractor for the company and is willing to do so on the terms and conditions set forth below. NOW, THEREFORE, in consideration of the above recitals and the mutual promises and conditions contained in this Agreement, the Parties agree as follows: TERMS This Agreement shall be effective commencing [Date], and shall continue until terminated at the completion of the Scope of Work which shall occur no later than [Date] or by either party as otherwise provided herein. STATUS OF INDEPENDENT CONTRACTOR This Agreement does not constitute a hiring by either party. It is the parties intentions that Independent Contractor shall have an independent contractor status and not be an employee for any purposes, including, but not limited to, [laws]. Independent Contractor shall retain sole and absolute discretion in the manner and means of carrying out their activities and responsibilities under this Agreement. This Agreement shall not be considered or construed to be a partnership or joint venture, and the Company shall not be liable for any obligations incurred by Independent Contractor unless specifically authorized in writing. Independent Contractor shall not act as an agent of the Company, ostensibly or otherwise, nor bind the Company in any manner, unless specifically authorized to do so in writing. TASKS, DUTIES, AND SCOPE OF WORK Independent Contractor agrees to devote as much time, attention, and energy as necessary to complete or achieve the following: [Describe]. The above to be referred to in this Agreement as the \"Scope of Work\". It is expected that the Scope of Work will completed by [Date]. Independent Contractor shall additionally perform any and all tasks and duties associated with the Scope of Work set forth above, including but not limited to, work being performed already or related change orders. Independent Contractor shall not be entitled to engage in any activities which are not expressly set forth by this Agreement. The books and records related to the Scope of Work set forth in this Agreement shall be maintained by the Independent Contractor at the Independent Contractor's principal place of business and open to inspection by Company during regular working hours. Documents to which Company will be entitled to inspect include, but are not limited to, any and all contract documents, change orders/purchase orders and work authorized by Independent Contractor or Company on existing or potential projects related to this Agreement. Independent Contractor shall be responsible to the management and directors of Company, but Independent Contractor will not be required to follow or establish a regular or daily work schedule. Supply all necessary equipment, materials and supplies. Independent Contractor will not rely on the equipment or offices of Company for completion of tasks and duties set forth pursuant to this Agreement. Any advice given Independent Contractors regarding the scope of work shall be considered a suggestion only, not an instruction. Company retains the right to inspect, stop, or alter the work of Independent Contractor to assure its conformity with this Agreement. ASSURANCE OF SERVICES Independent Contractor will assure that the following individuals (the \"Key Employees\") will be available to perform, and will perform, the Services hereunder until they are completed (identify by title and name as applicable): [Name of Key Employee, Title] [Name of Key Employee, Title] The Key Employees may be changed only with the prior written approval of the Company, which approval shall not be unreasonably withheld. COMPENSATION Independent Contractor shall be entitled to compensation for performing those tasks and duties related to the Scope of Work as follows: [Describe] Such compensation shall become due and payable to Independent Contractor in the following time, place, and manner: [Describe] NOTICE CONCERNING WITHHOLDING OF TAXES Independent Contractor recognizes and understands that it will receive a [specify tax] statement and related tax statements, and will be required to file corporate and/or individual tax returns and to pay taxes in accordance with all provisions of applicable Federal and State law. Independent Contractor hereby promises and agrees to indemnify the Company for any damages or expenses, including attorney's fees, and legal expenses, incurred by the Company as a result of independent contractor's failure to make such required payments. AGREEMENT TO WAIVE RIGHTS TO BENEFITS Independent Contractor hereby waives and foregoes the right to receive any benefits given by Company to its regular employees, including, but not limited to, health benefits, vacation and sick leave benefits, profit sharing plans, etc. This waiver is applicable to all non-salary benefits which might otherwise be found to accrue to the Independent Contractor by virtue of their services to Company, and is effective for the entire duration of Independent Contractor's agreement with Company. This waiver is effective independently of Independent Contractor's employment status as adjudged for taxation purposes or for any other purpose. Neither this Agreement, nor any duties or obligations under this Agreement may be assigned by either party without the consent of the other. TERMINATION This Agreement may be terminated prior to the completion or achievement of the Scope of Work by either party giving [number] days written notice. Such termination shall not prejudice any other remedy to which the terminating party may be entitled, either by law, in equity, or under this Agreement. NON-DISCLOSURE OF TRADE SECRETS, CUSTOMER LISTS AND OTHER PROPRIETARY INFORMATION Independent Contractor agrees not to disclose or communicate, in any manner, either during or after Independent Contractor's agreement with Company, information about Company, its operations, clientele, or any other information, that relate to the business of Company including, but not limited to, the names of its customers, its marketing strategies, operations, or any other information of any kind which would be deemed confidential, a trade secret, a customer list, or other form of proprietary information of Company. Independent Contractor acknowledges that the above information is material and confidential and that it affects the profitability of Company. ","Independent Contractor Agreement","6",62,"https://templates.business-in-a-box.com/imgs/1000px/independent-contractor-agreement-D160.png","https://templates.business-in-a-box.com/imgs/250px/160.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#160.xml",{"title":6,"description":6},[127],{"label":128,"url":129},"Consultant & Contractors","consulting-contractor-business","independent contractor agreement","/template/independent-contractor-agreement-D160",{"description":133,"descriptionCustom":6,"label":134,"pages":135,"size":136,"extension":10,"preview":137,"thumb":138,"svgFrame":139,"seoMetadata":140,"parents":141,"keywords":146,"url":147},"INTELLECTUAL PROPERTY ASSIGNMENT AGREEMENT This Intellectual Property Assignment Agreement (the \"Agreement\") is effective [DATE], BETWEEN: [YOUR COMPANY NAME] (the \"Assignor\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [COMPANY NAME] (the \"Assignee\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [COMPANY NAME] (the \"Shareholder\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] PREAMBLE WHEREAS [YOUR COMPANY NAME] owns all rights in a patent registered with the [COUNTRY] Patent Office under file number [NUMBER], serial number [NUMBER], entitled [SPECIFY] (the \"Patent\"); WHEREAS [YOUR COMPANY NAME] wishes to assign all rights and title in and to the Patent [COMPANY NAME]; WHEREAS the parties wish to enter into this Agreement on the terms and conditions more particularly provided herein. NOW, THEREFORE, in consideration of the above premises and agreements herein contained, the preamble forming an integral part hereof, the parties agree as follows: DEFINITIONS In this Agreement, except where the context or subject matter is inconsistent therewith, the following terms shall have the following meanings: \"Affiliates\" means, with respect to a Party to this Agreement, any person which, directly or indirectly, through one or more intermediaries, controls, is controlled by, or is under common control with such Party. The term \"control\" means possession, direct or indirect, of the powers to direct or cause the direction of the management or policies of a person, whether through ownership of equity participation, voting securities, or beneficial interests, by contract, by agreement or otherwise. \"Agreement\" shall mean this document, the annexed schedules, which are incorporated herein, together with any future written and executed amendments agreed to by the parties. \"Assigned Rights\" shall mean all rights and title in the Patent and all Intellectual Property Rights in the technology described in the Patent, in all countries. \"Improvements\" means innovations, inventions, ideas, designs, concepts, discoveries, techniques, works, processes, formulas, new derived material and modifications related to the Patent, whether or not patentable, copyrightable, or otherwise protectable as trade secrets or under any other intellectual property, conceived, brought to practice or developed by either Party after the date of this Agreement. \"Intellectual Property Rights\" includes all patents, trade marks, service marks, registered designs, integrated circuits topographies, including applications for any of the foregoing, and includes all copyrights, design rights, know-how, confidential information, trade secrets and any other similar rights in [COUNTRY] and in any other countries. \"Patent\" shall mean the patent described in recitals hereof and its counterpart applications in any country, now or thereafter owned by [YOUR COMPANY NAME] or to which [YOUR COMPANY NAME] otherwise acquires rights, including any patent application, divisional, continuation, provisional, reissue, re-examination, extension certificate, registration, renewal, confirmation and national phase entry application related to such Patent. ASSIGNMENT OF PATENT Subject to the terms and conditions contained in this Agreement, [YOUR COMPANY NAME] hereby irrevocably assigns to [COMPANY NAME] all rights and title and any other rights to the Patent as well as all Intellectual Property Rights in the technology described in the Patent, in all countries. The parties hereby recognize that any and all Intellectual Property Rights in any Improvements shall be held by [COMPANY NAME]. The parties hereby recognize that no Intellectual Property Rights are assigned, licensed or otherwise granted under this Agreement, save and except as explicitly stated in this Section 2. COMPENSATION In consideration of the Assigned Rights, [COMPANY NAME] agrees to pay [YOUR COMPANY NAME] the sum of [AMOUNT] (the \"Purchase Price\") payable upon the execution of this Agreement by all of the parties hereto. REPRESENTATIONS AND WARRANTIES The Guarantors represent and warrant on a joint and several basis to [COMPANY NAME] that: the Patent and [COMPANY NAME]'s use of the Patent does not, to the best knowledge of the Guarantors, infringe upon any patent, or any trademark, copyright, trade secret or other Intellectual Property Rights or proprietary right of any third party, and that there is currently no actual or threatened suit against [YOUR COMPANY NAME] by any third party based on an alleged violation of such right, and the Guarantors do not know of any basis for any such action; there are no outstanding assignments, grants, licenses, liens, encumbrances, obligations or agreements (whether written, oral or implied) regarding the Patent; [YOUR COMPANY NAME] has all rights, power and authority required in order to grant the Assigned Rights free and clear of all encumbrances or legal restrictions, in accordance with this Agreement; [YOUR COMPANY NAME] has good and marketable title to the Patent; there is no requirement for [YOUR COMPANY NAME] to obtain any other authorization, consent or approval from any third party as a condition to the enforceability of any provision of this Agreement or the lawful conclusion of the transactions contemplated by this Agreement; Notwithstanding any investigation conducted prior to the execution of this Agreement, and notwithstanding implied knowledge or notice of any fact or circumstance which [COMPANY NAME] may have as a result of such investigation or otherwise, [COMPANY NAME] shall be entitled to rely upon the representations and warranties set forth herein and the obligations of [YOUR COMPANY NAME] hereto with respect to such representations and warranties shall survive the termination of this Agreement for any reason. The Guarantors, on a joint and several basis, shall indemnify and hold [COMPANY NAME] harmless from all losses, liabilities, damages and expenses, including reasonable attorneys' fees and costs (collectively, \"Liabilities\"), that [COMPANY NAME] may suffer to the extent resulting from any claims, demands, actions or other proceedings made or instituted by any third party against [COMPANY NAME] and arising out of the use of the Patent, or related to the breach of any obligation or any representation and warranty under this Agreement, except for Liabilities arising out of the gross negligence or willful misconduct of [COMPANY NAME]. TERM AND TERMINATION This Agreement shall take effect upon the execution hereof by both parties hereto, and, unless sooner terminated as per paragraph 5.2 below, shall remain in effect until the expiration of the Patent. Upon any material breach or default under this Agreement by either Party, the other Party may give notice of such breach or default and, unless the same shall be cured within [NUMBER] days after delivery of such notice, then, without limitation of any other remedy available hereunder, such Party may terminate this Agreement immediately upon delivery of a notice of termination to the other Party at any time thereafter. The termination of this Agreement by either of the Parties shall be subject to all other rights and remedies available to the Parties hereunder or otherwise. NOTICE","Intellectual Property Assignment","7",80,"https://templates.business-in-a-box.com/imgs/1000px/intellectual-property-assignment-D5229.png","https://templates.business-in-a-box.com/imgs/250px/5229.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#5229.xml",{"title":6,"description":6},[142,143],{"label":31,"url":112},{"label":144,"url":145},"Transfer & Assignment Agreements","transfer-assignment-agreement","intellectual property assignment","/template/intellectual-property-assignment-D5229",{"description":149,"descriptionCustom":6,"label":150,"pages":151,"size":152,"extension":10,"preview":153,"thumb":154,"svgFrame":155,"seoMetadata":156,"parents":157,"keywords":160,"url":161},"SERVICE LEVEL AGREEMENT This Service Level Agreement (the Agreement\") is effective as of [DATE] (the \"Effective Date\"). BETWEEN: [YOUR COMPANY NAME] (the \"Service Provider\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [CLIENT NAME] (the \"Client\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] RECITALS This Agreement sets forth the terms and conditions under which Client will provide Service Provider with certain Equipment under bailment and Service Provider will provide certain support services to Client on specified Service Provider premises (hereinafter referred to as the \"Service Provider Network Location(s)\"). WHEREAS, Service Provider is desirous and capable of providing support services for certain Client-Provided Equipment which interconnects to Service Provider transmission services; and WHEREAS, Client desires to have the Equipment supported by Service Provider in a designated portion of certain Service Provider Network Location(s), as set forth in Exhibit A of this agreement (hereinafter referred to as the \"Location and Equipment Summary\"), which is attached hereto and made a part hereof; and WHEREAS, Client and Service Provider (hereinafter referred to cumulatively as the \"Parties\" and singularly as the \"Party\") have agreed on the terms which shall govern the bailment and support of the Equipment as set forth in Exhibit B of this agreement (hereinafter referred to as the \"Statement of Work\"), which is attached hereto and made a part hereof, and as set forth in Exhibit C of this agreement (hereinafter referred to as the \"Non-Recurring and Monthly Recurring Pricing Summary\"), which is attached hereto and made a part hereof; NOW, THEREFORE, in consideration of the mutual agreements and promises contained herein and for other good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, the Parties agree as follows: UNDERTAKINGS Client will provide for the inside delivery of the Equipment at the Service Provider Network Location(s) as specified in the Location and Equipment Summary with proper and timely notification as specified in the Statement of Work. Client will install the Equipment at the Service Provider Network Location(s) as specified in the Location and Equipment Summary in accordance with Service Provider and Industry standards and practices as specified in the Statement of Work. Service Provider will connect the Equipment to Service Provider services at the Service Provider Network Location(s) as specified in the Location and Equipment Summary in accordance with Service Provider standards and practices as specified in the Statement of Work. Service Provider will hold the Equipment in bailment for use only at the Service Provider Network Location(s) as specified in the Location and Equipment Summary and only for the purposes contemplated herein. During the term of the bailment, Service Provider shall provide space, power, testing, environment and other support services for the Equipment as set forth in the Statement of Work and Service Provider shall have no other responsibility for the Equipment. Client shall cooperate fully with Service Provider in the provision of these support services and agrees to perform those activities identified as Client Responsibilities in the Statement of Work. TERM AND TERMINATION The initial term of this Agreement shall commence on the [DATE], shall continue for a period of [NUMBER] years, and then shall terminate on [DATE]. This Agreement is binding when executed by Client and subsequently accepted by Service Provider and once accepted by Service Provider, the rates and charges provided in this Agreement will be effective from the first day of the next billing cycle following Client's signature date (the \"Effective Date\"). Either Party may terminate this Agreement following the giving of [NUMBER] calendar days prior written notice of termination to the other Party. If Client terminates this Agreement prior to the expiration of the initial [NUMBER] year term, Client will pay Service Provider, in addition to all other charges due, per Service Provider Network Location, which amount shall represent liquidated damages that Client agrees are reasonable. Client shall remove its Equipment from the Service Provider Network Location(s) within [NUMBER] calendar days of the termination of this Agreement and, if Client fails to do so, Service Provider may itself remove the Equipment and store the same at Client's expense and at Client's sole risk. Any expenditure by Service Provider for the removal and storage of the Equipment shall bear interest at the lesser of [%] per annum or the maximum rate permitted by law. The rights and duties in Article D, \"Warranty and Liability\" shall survive the termination of this Agreement. FINANCIAL PROVISIONS Client shall pay Service Provider a non-recurring fee for Site Preparation, Additional AC or DC Power Circuits and Circuit Interconnection at each of the Service Provider Network Location(s) as set forth in the Non-Recurring and Monthly Recurring Pricing Summary. Client shall pay Service Provider on a monthly recurring basis for Location Management Fee(s), an Uninterruptable Power Supply (UPS) for [115V OR OTHER] AC Power Circuits and for Service Provider First-Level Maintenance Support at each of the Service Provider Network Location(s) as set forth in the Non-Recurring and Monthly Recurring Pricing Summary. Client shall pay Service Provider a one time charge of [AMOUNT per circuit when, at the Client's request, Service Provider provided cabling is added, moved or changed after the initial Site Preparation work listed in the Equipment and Location Summary is completed by Service Provider. This charge is in addition to any other charges specified in the applicable tariff or contract from the entity from which the facility or service is obtained. For equipment moves made pursuant to Client's request, Client shall pay for each unit of Equipment this is moved to a different location within the same Service Provider Network Location after the initial Site Preparation work listed in the Equipment and Location Summary is completed by Service Provider. Client shall pay directly or reimburse Service Provider, as applicable, for all taxes, duties, and similar liabilities which may result from this Agreement, or any support services specified hereunder, exclusive of taxes based on Service Provider's net income. All invoices shall be due and payable in [CURRENCY] within [NUMBER] calendar days upon receipt as set forth in the Non-Recurring and Monthly Recurring Pricing Summary. WARRANTY AND LIABILITY Service Provider warrants that its undertakings hereunder shall be performed in a professional and workmanlike manner and that it will provide Support Services in accordance with this Agreement. NO OTHER WARRANTIES ARE EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, ANYWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Client warrants that it has the unrestricted right to place the Equipment at Service Provider's Location(s) listed in the Location and Equipment Summary for the term of this Agreement. Except as otherwise set forth herein, neither Party shall be deemed negligent, at fault or liable in any respect to the other for any delay, interruption or failure in performance hereunder resulting from fire, flood, water, the elements, explosions, acts of God, war, accidents, labor disputes, strikes, shortages of equipment or suppliers, unavailability of transportation or other cause beyond the reasonable control of the Party delayed or prevented from performing.","Service Level Agreement","12",89,"https://templates.business-in-a-box.com/imgs/1000px/service-level-agreement-D778.png","https://templates.business-in-a-box.com/imgs/250px/778.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#778.xml",{"title":6,"description":6},[158,159],{"label":17,"url":96},{"label":17,"url":96},"service level agreement","/template/service-level-agreement-D778",{"description":163,"descriptionCustom":6,"label":164,"pages":135,"size":104,"extension":10,"preview":165,"thumb":166,"svgFrame":167,"seoMetadata":168,"parents":170,"keywords":169,"url":173},"MASTER SERVICE AGREEMENT This Master Service Agreement (\"Agreement\") is made and effective this [Date], BETWEEN: [YOUR COMPANY NAME],\" PARTY A\", a corporation organized and existing under the laws of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [COMPANY NAME],\" PARTY B\", a corporation organized and existing under the laws of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] SCOPE OF SERVICES [PARTY A] shall provide [PARTY B] with the services and products described in the Statements of Work. The SOW must describe the respective contribution and services of each party. Any services provided by either party under this Agreement are referred to as the \"Services\". For the purposes of this Agreement, the party engaged to perform the Services, [PARTY A], is the \"Performing Party\" and the party for whom the Services are to be performed, [PARTY B], is the \" Engaging Party\". All SOWs that are negotiated between the parties shall be in writing and executed by both parties and shall be attached hereto as supplemental Exhibits, and shall be incorporated into, and governed by, this Agreement. STATEMENT OF WORK (SOW) Contents of Statements of Work The parties shall describe each individual deliverable to be provided under this agreement in its own statement of work (each, a \"Statement of Work\"), each one including a complete description of the deliverable provided under the Statement of Work, the number of [PARTY A] personnel who will be assigned to provide the deliverable in question, key [PARTY A] personnel the parties agree are essential to the provision of the particular deliverable (shall not exceed [SPECIFY] percent of the total personnel assigned to this Statement of Work) (each one a \"Key Personnel\"), the applicable fees and fee schedule, including any milestones and milestone payments if applicable, for the particular deliverable, the service levels and acceptance criteria for the particular deliverable, any materials the parties will provide for the particular deliverable, a timeline for providing the particular deliverable, and a unique identification number for the Statement of Work and explicit reference to this agreement. Integration. A Statement of Work signed by both parties, bearing a unique identification number and making explicit reference to this Agreement, shall be deemed to form an integral part of this Agreement. Severable. The parties may terminate any individual Statement of Work without affecting the rest of the agreement or any other Statement of Work. Conflict of Terms. If there is a conflict between the terms of this agreement and any Statement of Work, the Statement of Work shall apply. Changes to Statements of Work Proposing Changes. Either party may propose amendments to the Statement of Work deliverable, fees or schedule by giving written notice to the other party. Finalizing Changes. If the parties agree to change the deliverable, fees, or schedule of a Statement of Work they parties shall cooperate to execute a written amendment to the relevant Statement of Work detailing the changes. Additional Statements of Work Request Additional Services. [PARTY B] may request additional services by sending a written notice to [PARTY A] reasonably detailing the services requested. Assess the Request. Immediately after receiving a request for additional services from [PARTY B], [PARTY A] shall evaluate the request to determine whether there are circumstances preventing it from providing the requested services and, if there are no circumstances preventing it from providing the requested services, shall provide [PARTY A] with the estimated fees and timelines for such requested services. Execute New Statement of Work. If after receiving [PARTY A] 's estimates [PARTY B] still wants the requested services, the parties shall execute a new Statement of Work according to the requirements of paragraph CONTENT OF STATEMENTS OF WORK. Acceptance and Rejection Inspection Period. [PARTY B] shall have an \"Inspection period\" of [NUMBER] working days after [PARTY A] has provided the deliverable to review and verify that the deliverable meets the acceptance criteria as set out in the applicable Statement of Work (the \"Inspection Period\"). Acceptance. If in [PARTY B] 's opinion the deliverable meets the acceptance criteria, [PARTY B] must accept the deliverable and notify [PARTY A] that it is accepting the deliverable. Deemed Acceptance.[PARTY B] shall be deemed to have accepted the deliverable if [PARTY B] fails to notify [PARTY A] by the end of the inspection period, or if, during the inspection period, [PARTY B] uses or attempts to use the deliverable beyond what is necessary for the inspection and testing, in a manner that a reasonable person would consider compatible with [PARTY B] having accepted deliverable from [PARTY A]. Rejection. If in [PARTY B]'s opinion, the deliverable does not materially meet the acceptance criteria, [PARTY B] may reject the deliverable by delivering to [PARTY B] a written list detailing each failure to satisfy the acceptance criteria. TERM The term of this Agreement begins on [INSERT START DATE] and continues until such time as the Deliverables have been provided to the Purchaser in accordance with this Agreement or until such time as this Agreement is terminated by either party in accordance with its terms. BUDGET AND PAYMENT DEADLINE The budget and payment deadline will be defined in each SOW. Unless otherwise provided in this SOW, uncontested invoices are payable within 30 calendar days of receipt of the invoice. Payment is made as follows: [SPECIFY]. INDEPENDENT CONTRACTOR The relationship between [PARTY A] and [PARTY B] shall, within the context of the SOW, be that of an independent contractor, and nothing in this Agreement should be construed to create a partnership, joint venture, or employer-employee relationship. Each Party shall, at all times during the term of this Agreement, perform the duties and responsibilities herein without any control by the other Party. Either Party may realize a profit or loss in connection with performing the services. Either Party may render similar services for the benefit of others. Neither Party is an agent of the other Party and is not authorized to make any representation, contract, or contract commitment on behalf of the other Party. DELIVERABLES The Supplier shall provide the goods and/or services described in the Statement of Work (attached) of this Master Service Agreement. CONFIDENTIALITY Information shall be treated as confidential during the term of this Agreement and for a period of seven (7) years thereafter. During such period, the parties will not: (a) disclose the Confidential Information of the Disclosing Party to any third party, using at least the same degree of care as it uses to protect its own confidential information, but not less than reasonable care or (b) use such information for any purpose other than to perform its obligations under this Agreement. Confidential Information does not include information which has previously been made generally available to the public, becomes publicly known, without fault on the part of the Receiving Party, subsequent to disclosure by the Disclosing Party of such information to the Receiving Party, is received by the Receiving Party at any time from a source, other than the Disclosing Party, lawfully having possession of and the right to disclose such information, otherwise becomes known by the Receiving Party prior to disclosure by the Disclosing Party to the receiving party of such information, or is independently developed by the Receiving Party without use of such information","Master Service Agreement","https://templates.business-in-a-box.com/imgs/1000px/master-service-agreement-D12657.png","https://templates.business-in-a-box.com/imgs/250px/12657.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12657.xml",{"title":169,"description":6},"master service agreement",[171,172],{"label":31,"url":112},{"label":31,"url":112},"/template/master-service-agreement-D12657",false,{"seo":176,"reviewer":189,"quick_facts":193,"at_a_glance":195,"personas":199,"variants":224,"glossary":252,"clauses":286,"how_to_fill":337,"common_mistakes":378,"faqs":403,"industries":431,"comparisons":448,"diy_vs_lawyer":463,"jurisdictions":476,"related_template_ids_curated":497,"schema":508,"classification":509},{"meta_title":177,"meta_description":178,"primary_keyword":179,"secondary_keywords":180,"family":179,"is_canonical":188},"Source Code Trust Agreement Template (Free Word)","Free source code trust agreement template for software development deals. Covers escrow conditions, release triggers, IP ownership, and trustee duties. Free Word and PDF download.","source code trust agreement",[181,182,20,183,184,185,186,187],"source code escrow agreement template","software escrow agreement template","source code escrow contract","software source code escrow template word","source code release agreement","technology escrow agreement template","software development escrow contract",true,{"name":190,"credential":191,"reviewed_date":192},"Bruno Goulet","CEO, Business in a Box","2026-05-02",{"difficulty":194,"legal_review_recommended":188,"signature_required":188},"advanced",{"what_it_is":196,"when_you_need_it":197,"whats_inside":198},"A Source Code Trust Agreement (Development) is a legally binding tripartite contract among a software developer, a licensee (end-user or customer), and a neutral trustee under which the developer deposits the application's source code — and related build documentation — with the trustee for safekeeping. This free Word download gives you a structured, attorney-ready starting point you can edit online and export as PDF to protect both sides of a software development or licensing relationship.\n","Use it whenever a licensee relies on proprietary software critical to its operations and needs assurance that source code will remain accessible if the developer becomes insolvent, ceases support, or materially breaches the development agreement. It is also used during active development when milestone deposits are required as a condition of staged payments.\n","Trustee appointment and duties, deposit obligations and acceptance procedures, release conditions and verification rights, IP ownership and license-back provisions, confidentiality obligations, trustee fees and liability limits, and termination mechanics covering all three parties.\n",[200,204,208,212,216,220],{"title":201,"use_case":202,"icon_asset_id":203},"Software licensees and enterprise buyers","Protecting access to mission-critical application source code if the vendor fails","persona-enterprise-buyer",{"title":205,"use_case":206,"icon_asset_id":207},"Independent software vendors (ISVs)","Satisfying a customer's contractual escrow requirement to close a licensing deal","persona-isv",{"title":209,"use_case":210,"icon_asset_id":211},"SaaS founders and CTO teams","Structuring milestone-based code deposits tied to development sprint completions","persona-startup-founder",{"title":213,"use_case":214,"icon_asset_id":215},"Private equity and M&A teams","Requiring escrow as a condition of a software acquisition or technology transfer","persona-private-equity",{"title":217,"use_case":218,"icon_asset_id":219},"Legal and compliance officers","Documenting third-party software dependency risk management for auditors or regulators","persona-legal-counsel",{"title":221,"use_case":222,"icon_asset_id":223},"Government and public-sector IT procurement","Meeting statutory requirements for source code continuity in regulated technology contracts","persona-government-procurement",[225,229,233,237,240,244,248],{"situation":226,"recommended_template":227,"slug":228},"Protecting a completed, deployed software product under a perpetual license","Software Escrow Agreement","software-escrow-agreement-D14061",{"situation":230,"recommended_template":231,"slug":232},"Active software development with staged milestone deposits","Source Code Trust Agreement (Development)","source-code-trust-agreement-development-D812",{"situation":234,"recommended_template":235,"slug":236},"Transferring full IP ownership of source code to a buyer","Software IP Assignment Agreement","ip-sale-agreement-D964",{"situation":238,"recommended_template":46,"slug":239},"Licensing source code for modification without an escrow requirement","source-code-license-agreement-D807",{"situation":241,"recommended_template":242,"slug":243},"Outsourcing development to a third-party contractor with IP assignment","Software Development Agreement","custom-software-development-agreement-D787",{"situation":245,"recommended_template":246,"slug":247},"Protecting SaaS platform source code for a cloud-hosted product","SaaS Escrow Agreement","escrow-agreement-D1173",{"situation":249,"recommended_template":250,"slug":251},"Depositing firmware or embedded software with a hardware product","Technology Escrow Agreement","technology-assignment-agreement-D765",[253,256,259,262,265,268,271,274,277,280,283],{"term":254,"definition":255},"Trustee (Escrow Agent)","A neutral third party that holds the deposited source code and release materials and releases them only upon a defined triggering event.",{"term":257,"definition":258},"Deposit Materials","Everything placed in trust: source code, build scripts, technical documentation, third-party library licenses, and any other materials needed to compile and run the software.",{"term":260,"definition":261},"Release Condition","A contractually defined event — such as developer insolvency, material breach, or cessation of support — that entitles the licensee to receive the deposited materials.",{"term":263,"definition":264},"Verification","A technical audit performed by the trustee or an appointed specialist to confirm that the deposit materials are complete, compilable, and match the production version.",{"term":266,"definition":267},"License-Back","A conditional, limited license the developer grants the licensee to use, modify, and maintain the released source code solely for the licensee's internal purposes following a release event.",{"term":269,"definition":270},"Milestone Deposit","A scheduled deposit of updated source code tied to the completion of a defined development sprint, phase, or deliverable under the underlying development agreement.",{"term":272,"definition":273},"Insolvency Event","A release trigger encompassing bankruptcy filing, receivership appointment, voluntary liquidation, or assignment for the benefit of creditors by the developer.",{"term":275,"definition":276},"Continuity of Support Obligation","The developer's contractual commitment to maintain, update, and support the software for a defined period — breach of which may itself constitute a release condition.",{"term":278,"definition":279},"Tripartite Agreement","A contract binding three parties simultaneously — here, the developer, the licensee, and the trustee — each with distinct rights and obligations.",{"term":281,"definition":282},"Proprietary Information","Source code, algorithms, trade secrets, and technical know-how embedded in the deposit materials that the developer has not made publicly available.",{"term":284,"definition":285},"Build Documentation","Written instructions, configuration files, and environment specifications sufficient for a competent developer to compile the source code into a working, deployable application.",[287,292,297,302,307,312,317,322,327,332],{"name":288,"plain_english":289,"sample_language":290,"common_mistake":291},"Recitals and definitions","Identifies all three parties by legal name, establishes the underlying development or license agreement this escrow supports, and defines key terms used throughout the contract.","This Source Code Trust Agreement ('Agreement') is entered into as of [DATE] among [DEVELOPER LEGAL NAME] ('Developer'), [LICENSEE LEGAL NAME] ('Licensee'), and [TRUSTEE LEGAL NAME] ('Trustee'). Capitalized terms not defined herein have the meanings given in the Software Development Agreement dated [DATE] ('Underlying Agreement').","Failing to cross-reference the underlying development or license agreement by full title and date, making it impossible to determine which software version the escrow covers.",{"name":293,"plain_english":294,"sample_language":295,"common_mistake":296},"Deposit obligations and schedule","Specifies what the developer must deposit, when initial and subsequent deposits are due, and the format and media requirements for delivery to the trustee.","Developer shall deliver to Trustee the Deposit Materials described in Exhibit A within [30] days of the Effective Date and within [5] business days of completing each Milestone identified in Exhibit B. All deposits shall be delivered on [MEDIA TYPE / secure upload portal] with a signed Deposit Certificate.","Defining deposit materials too narrowly — omitting build scripts, environment configuration files, or third-party component licenses — so the released code cannot be compiled by the licensee.",{"name":298,"plain_english":299,"sample_language":300,"common_mistake":301},"Trustee acceptance and verification","Sets out the trustee's duty to acknowledge receipt, conduct or commission a technical verification of deposit completeness, and notify both parties of any deficiency.","Upon receipt of Deposit Materials, Trustee shall issue a written Deposit Receipt within [3] business days. Within [30] days of each deposit, Trustee shall perform a Level [1 / 2 / 3] Verification and notify both Developer and Licensee of any identified deficiency. Developer shall cure deficiencies within [15] business days.","Skipping verification entirely or scheduling it only at initial deposit, leaving later milestone deposits unverified and potentially incomplete at the time they are most needed.",{"name":303,"plain_english":304,"sample_language":305,"common_mistake":306},"Release conditions","Lists the specific events that entitle the licensee to request release of the deposit materials, and sets out the notice and response procedure before the trustee releases.","Licensee may request release of the Deposit Materials upon the occurrence of any of the following: (a) Developer files for bankruptcy or is subject to an involuntary insolvency proceeding not dismissed within [60] days; (b) Developer commits a Material Breach of the Underlying Agreement and fails to cure within [30] days of written notice; (c) Developer permanently ceases to offer support for the Software.","Drafting release conditions so broadly that any minor breach triggers release, creating litigation risk, or so narrowly that legitimate business disruption events are excluded.",{"name":308,"plain_english":309,"sample_language":310,"common_mistake":311},"Release procedure and dispute resolution","Defines how the licensee submits a release request, the notice period given to the developer to object, and how a disputed release is resolved before the trustee acts.","To request release, Licensee shall deliver written notice to Trustee and Developer specifying the release condition. Developer may object within [10] business days. If no objection is timely received, Trustee shall release the Deposit Materials. If Developer objects, release shall be withheld pending resolution by [arbitration / court order] under Clause [X].","Omitting a developer objection window entirely, exposing the trustee to liability for premature release, or setting the window so long (30+ days) that the licensee cannot respond to an urgent operational failure.",{"name":313,"plain_english":314,"sample_language":315,"common_mistake":316},"License-back and permitted use after release","Grants the licensee a limited, non-exclusive license to use, modify, and maintain the released source code solely for internal business continuity purposes — not for redistribution or competitive use.","Upon release, Developer grants Licensee a non-exclusive, non-transferable, royalty-free license to use, reproduce, and modify the Deposit Materials solely to continue operating the Software for Licensee's internal business purposes. This license does not include the right to distribute, sublicense, or commercialize the Software or Deposit Materials.","Granting an unrestricted license on release, effectively giving the licensee commercial distribution rights the developer never intended to convey.",{"name":318,"plain_english":319,"sample_language":320,"common_mistake":321},"IP ownership and confidentiality","Confirms that the developer retains all IP rights in the deposit materials at all times, and obligates the trustee and licensee to treat the materials as confidential proprietary information.","All right, title, and interest in the Deposit Materials remains exclusively with Developer. Trustee and Licensee shall treat the Deposit Materials as Developer's Confidential Information, apply no less than reasonable security measures, and disclose them only as expressly permitted by this Agreement.","No explicit IP retention clause, leaving the legal status of ownership ambiguous after a release — which courts in some jurisdictions have construed against the developer.",{"name":323,"plain_english":324,"sample_language":325,"common_mistake":326},"Trustee fees, liability, and indemnification","Allocates trustee fees between the parties, caps the trustee's liability for storage and release, and requires the developer and licensee to indemnify the trustee against third-party claims arising from a disputed release.","Annual escrow fees of $[AMOUNT] shall be paid by [Licensee / Developer / equally]. Trustee's total liability under this Agreement shall not exceed the fees paid to Trustee in the preceding [12] months. Developer and Licensee shall jointly and severally indemnify Trustee against any third-party claims arising from a release made in good-faith compliance with this Agreement.","Omitting a trustee liability cap, making qualified trustees unwilling to accept the appointment and leaving the escrow unenforceable for lack of a willing agent.",{"name":328,"plain_english":329,"sample_language":330,"common_mistake":331},"Term and termination","Sets the initial term, auto-renewal provisions, and the conditions under which any party may terminate — and what happens to the deposit materials on termination.","This Agreement commences on the Effective Date and continues for [1 year], renewing automatically for successive [1-year] terms unless terminated by any party on [60] days' written notice. On termination without a pending release request, Trustee shall return the Deposit Materials to Developer or destroy them per Developer's written instruction within [30] days.","No provision for what happens to deposit materials on termination — leaving the trustee holding materials indefinitely with no authority to act and creating storage liability.",{"name":333,"plain_english":334,"sample_language":335,"common_mistake":336},"Governing law and dispute resolution","Specifies the jurisdiction whose law governs the agreement and how disputes among any of the three parties are resolved — typically arbitration for speed and confidentiality in technology disputes.","This Agreement is governed by the laws of [STATE / PROVINCE / COUNTRY]. Any dispute arising hereunder shall be resolved by binding arbitration under the [AAA / JAMS / ICC] rules in [CITY], conducted in [LANGUAGE], except that either party may seek injunctive relief in any court of competent jurisdiction.","Choosing a governing law that differs from the underlying software development agreement, creating conflicting legal standards for what constitutes a material breach triggering release.",[338,343,348,353,358,363,368,373],{"step":339,"title":340,"description":341,"tip":342},1,"Identify all three parties by their legal entity names","Enter the developer's and licensee's full registered legal names, jurisdiction of incorporation, and principal addresses. Identify the trustee — a professional escrow company, law firm, or neutral third party — by its registered name and contact details.","Use a professionally accredited escrow agent such as an IP escrow service or technology escrow company rather than an individual, so the appointment survives personnel changes.",{"step":344,"title":345,"description":346,"tip":347},2,"Define the deposit materials in Exhibit A","List every component required to compile and run the software: source code files with directory structure, build scripts, configuration files, database schemas, API keys management documentation, and third-party library license details.","Have your lead developer review Exhibit A before signing — a legal team alone will miss technical components that make the difference between compilable and useless code.",{"step":349,"title":350,"description":351,"tip":352},3,"Set the deposit schedule in Exhibit B","For development escrows, tie each deposit date to a specific milestone in the underlying development agreement. For completed-software escrows, specify the initial deposit deadline and an annual or quarterly update schedule.","Align milestone deposit deadlines to payment milestones in the development agreement — if payment is withheld for a late deposit, both parties have a strong incentive to comply.",{"step":354,"title":355,"description":356,"tip":357},4,"Negotiate and draft the release conditions","List each release trigger with precision: insolvency events by specific type, material breach with cure periods, and cessation of support with a defined notice threshold. Avoid vague triggers like 'failure to perform' without a specific cure mechanism.","Include a business-sale or change-of-control trigger if the licensee's concern is that the developer will be acquired and the new owner will discontinue the product.",{"step":359,"title":360,"description":361,"tip":362},5,"Specify the verification level required","Level 1 verification confirms deposit existence; Level 2 confirms completeness against a specification; Level 3 is a full build and functional test. Higher levels cost more but provide meaningful assurance.","For mission-critical software, require at least Level 2 verification at initial deposit and after each major version update — Level 1 only confirms a file exists, not that it compiles.",{"step":364,"title":365,"description":366,"tip":367},6,"Draft the license-back scope carefully","Define the permitted use after release: internal business continuity only, or including the right to engage a third-party maintenance contractor. Explicitly exclude commercial redistribution and sublicensing.","If the licensee needs to hire an outside developer to maintain the code after a release, the license-back clause must explicitly permit disclosure to and use by such a contractor.",{"step":369,"title":370,"description":371,"tip":372},7,"Confirm trustee fees and payment responsibility","Enter the trustee's annual fee, who pays it, and what happens if payment lapses. Many escrow agents will suspend access or return materials if fees are not paid on time.","Structure the agreement so the licensee pays the trustee fee directly — placing it on the developer creates a scenario where a financially distressed developer may let the escrow lapse precisely when it is most needed.",{"step":374,"title":375,"description":376,"tip":377},8,"Execute all three counterparts before the first deposit","All three parties — developer, licensee, and trustee — must sign before any deposit is made. Post-deposit signature creates an ambiguity about what materials are covered and whether the trustee's obligations have commenced.","Use timestamped electronic signatures so the execution date is indisputable if a release is ever disputed in arbitration or court.",[379,383,387,391,395,399],{"mistake":380,"why_it_matters":381,"fix":382},"Defining deposit materials without build documentation","Raw source code files are worthless without the build scripts, environment specifications, and dependency lists needed to compile them. A licensee who receives incomplete materials cannot restore the application and the escrow fails its entire purpose.","Require Exhibit A to include a build manifest signed off by the developer's technical lead, specifying every file, library, and configuration needed to produce a deployable binary from scratch.",{"mistake":384,"why_it_matters":385,"fix":386},"Setting release conditions that require a court judgment before release","Requiring a final court judgment as the sole release trigger means the licensee cannot access the code for 12–36 months while litigation proceeds — by which time the business disruption is irreparable.","Include self-executing triggers for objectively verifiable events (bankruptcy filing, public cessation of operations) and reserve court-order requirements only for contested factual disputes.",{"mistake":388,"why_it_matters":389,"fix":390},"Omitting the change-of-control as a release trigger","The most common scenario where licensees need escrow protection is a developer acquisition by a competitor, not insolvency. Without a change-of-control trigger, the acquirer can discontinue the product with no release obligation.","Add a release condition covering any acquisition, merger, or change of control of the developer where the acquirer is a direct competitor of the licensee or announces discontinuation of the software.",{"mistake":392,"why_it_matters":393,"fix":394},"No verification obligation on the trustee","A trustee that merely stores whatever the developer uploads provides no assurance that the deposit is complete or compilable. The licensee discovers the deficiency only after a release event, when it is too late.","Mandate at least Level 2 verification within 30 days of each deposit and require the developer to cure any identified deficiency within 15 business days under penalty of material breach.",{"mistake":396,"why_it_matters":397,"fix":398},"Using a different governing law from the underlying development agreement","Conflicting governing laws create disputes about what standard applies to a 'material breach' release trigger — the trustee cannot safely release without a court order, negating the agreement's value.","Always match the governing law clause in the trust agreement to the governing law of the underlying software development or license agreement.",{"mistake":400,"why_it_matters":401,"fix":402},"Allowing developer-only termination rights during active development","If the developer can unilaterally terminate the escrow and retrieve the deposit materials at any time, the licensee has no protection during exactly the period — active development — when insolvency risk is highest.","During the active development term, restrict unilateral developer termination and require mutual consent or a defined notice period of no less than 90 days, with the licensee retaining the right to object and seek injunctive relief.",[404,407,410,413,416,419,422,425,428],{"question":405,"answer":406},"What is a source code trust agreement?","A source code trust agreement is a legally binding contract among a software developer, a licensee, and a neutral trustee under which the developer deposits the application's source code with the trustee for safekeeping. The trustee holds the materials and releases them to the licensee only if a defined triggering event occurs — such as developer insolvency, material breach, or cessation of support. It is the standard mechanism for protecting enterprise and government buyers against loss of access to mission-critical software.\n",{"question":408,"answer":409},"What is the difference between a source code trust agreement and a software escrow agreement?","The terms are often used interchangeably, but a source code trust agreement in the development context specifically contemplates ongoing milestone deposits during active software development, whereas a standard software escrow agreement typically covers a completed, deployed product. The development variant includes deposit schedules tied to sprint or milestone completion, more detailed verification obligations, and release conditions calibrated to development-phase risks rather than post-deployment maintenance failures.\n",{"question":411,"answer":412},"Who are the three parties to a source code trust agreement?","The three parties are the developer (who deposits the code), the licensee or end-user (who benefits from the escrow protection), and the trustee or escrow agent (a neutral third party who holds the materials and manages the release procedure). All three must sign the agreement for it to be binding and for the trustee's obligations to commence.\n",{"question":414,"answer":415},"What events typically trigger the release of escrowed source code?","Common release triggers include: the developer filing for bankruptcy or entering insolvency proceedings, the developer committing a material breach of the underlying development or license agreement and failing to cure within a defined period, the developer permanently ceasing maintenance and support of the software, and — in well-drafted agreements — a change of control of the developer where the acquirer discontinues the product or is a direct competitor of the licensee.\n",{"question":417,"answer":418},"Does a source code trust agreement transfer ownership of the source code to the licensee?","No. The developer retains full IP ownership of the source code at all times, including after a release. What the licensee receives on release is a limited, conditional license — typically for internal business continuity use only — not an assignment of IP rights. Any commercial redistribution or sublicensing of released code without a separate IP assignment agreement would typically constitute IP infringement.\n",{"question":420,"answer":421},"What is source code verification and why does it matter?","Verification is a technical audit of the deposited materials to confirm they are complete, compilable, and match the production version of the software. Level 1 confirms a deposit was received; Level 2 checks completeness against a specification; Level 3 involves a full build and functional test. Without at least Level 2 verification, the licensee has no assurance the deposit would actually work in a release scenario, making the entire escrow arrangement commercially meaningless.\n",{"question":423,"answer":424},"Is a source code trust agreement enforceable in bankruptcy?","In most jurisdictions, a properly structured source code trust agreement provides meaningful protection in a developer's bankruptcy, but the details matter. In the US, software licenses are treated as executory contracts under the Bankruptcy Code (11 U.S.C. § 365(n)), allowing licensees to retain their rights. A well-drafted escrow reinforces those rights by creating a separate legal obligation on the trustee that survives the developer's insolvency. Consider engaging a lawyer to confirm the agreement's structure is bankruptcy-remote under the applicable jurisdiction's law.\n",{"question":426,"answer":427},"Who pays the trustee's fees?","Fee responsibility is negotiable but typically falls on the licensee, since the escrow primarily benefits them. Placing fee obligations on the developer creates a risk that a financially distressed developer — exactly the scenario the escrow is meant to address — allows fees to lapse and the escrow to terminate. Having the licensee pay directly ensures the arrangement remains in force regardless of the developer's financial condition.\n",{"question":429,"answer":430},"Do I need a lawyer to prepare a source code trust agreement?","For straightforward domestic software licensing arrangements with a standard commercial trustee, a high-quality template reviewed by a technology lawyer is typically sufficient. Engage a lawyer independently when the software is highly valuable or mission-critical, when the developer or licensee operates across multiple jurisdictions, when the agreement needs to be bankruptcy-remote under specific insolvency laws, or when the release conditions involve complex technical or contractual definitions. A 2–4 hour review typically costs $600–$1,200 and is worthwhile for any enterprise deal.\n",[432,436,440,444],{"industry":433,"icon_asset_id":434,"specifics":435},"Financial services and fintech","industry-fintech","Regulatory continuity requirements mean financial institutions routinely require source code escrow for core banking, trading, and compliance software — often as a condition of vendor onboarding under DORA, OCC, and FCA operational resilience frameworks.",{"industry":437,"icon_asset_id":438,"specifics":439},"Healthcare and MedTech","industry-healthtech","FDA-regulated software and hospital EHR systems require source code continuity provisions to satisfy 21 CFR Part 11 and HIPAA audit obligations, and to ensure patient-care systems remain operable if a software vendor fails.",{"industry":441,"icon_asset_id":442,"specifics":443},"Government and public sector","industry-government","Many government procurement frameworks in the US (FAR), UK (Crown Commercial Service), and EU mandate software escrow for mission-critical public-sector systems, with specific verification and release-condition standards written into contract requirements.",{"industry":445,"icon_asset_id":446,"specifics":447},"SaaS and enterprise software","industry-saas","Enterprise SaaS customers with data sovereignty or operational continuity requirements increasingly require source code trust agreements as a condition of multi-year licensing deals, particularly for on-premise or private-cloud deployments.",[449,452,455,459],{"vs":242,"vs_template_id":450,"summary":451},"software-development-agreement-D13237","A software development agreement governs the entire development relationship — scope, deliverables, timelines, payment, and IP ownership. A source code trust agreement is a companion document that provides continuity protection by placing the code with a neutral trustee. The development agreement creates the obligation to build; the trust agreement protects the output. Both are typically executed simultaneously.",{"vs":46,"vs_template_id":453,"summary":454},"D{SOURCE_CODE_LICENSE_ID}","A source code license agreement grants the licensee direct access to and specified usage rights over the source code from day one. A trust agreement keeps the code held by a neutral trustee and releases it only on a triggering event. Use a license agreement when the licensee needs to modify or maintain the code actively; use a trust agreement when the goal is continuity protection without immediate code access.",{"vs":456,"vs_template_id":457,"summary":458},"IP Assignment Agreement","D{IP_ASSIGNMENT_ID}","An IP assignment agreement permanently transfers full ownership of the source code and associated intellectual property to the buyer. A source code trust agreement leaves ownership with the developer and grants only a conditional, limited license on release. Use an assignment when the developer is selling the software outright; use a trust agreement when the developer retains the product and the licensee needs risk protection only.",{"vs":460,"vs_template_id":461,"summary":462},"Non-Disclosure Agreement","non-disclosure-agreement-nda-D12692","An NDA protects the confidentiality of source code shared directly between parties during negotiations, due diligence, or evaluation. A source code trust agreement is an operational continuity mechanism — it governs who holds the code, when it is released, and on what terms, not merely who may view it. A well-structured software deal typically requires both: an NDA for pre-contract disclosure and a trust agreement for post-execution protection.",{"use_template":464,"template_plus_review":468,"custom_drafted":472},{"best_for":465,"cost":466,"time":467},"Standard domestic software licensing deals with a professional escrow agent and straightforward release conditions","Free","1–3 hours to complete, plus trustee onboarding time",{"best_for":469,"cost":470,"time":471},"Enterprise deals above $100K ACV, regulated industries, or cross-border arrangements with one jurisdiction","$600–$1,200 for a 2–4 hour technology lawyer review","3–7 business days",{"best_for":473,"cost":474,"time":475},"Mission-critical financial, healthcare, or government software with complex release conditions, multi-jurisdiction enforcement, or bankruptcy-remote structuring requirements","$2,000–$8,000+","2–5 weeks",[477,482,487,492],{"code":478,"name":479,"flag_asset_id":480,"note":481},"us","United States","flag-us","US software licensees benefit from 11 U.S.C. § 365(n) of the Bankruptcy Code, which allows licensees to retain their rights under a software license even if the developer's trustee in bankruptcy rejects the contract. A source code escrow reinforces this protection by creating a separate obligation on the trustee. State UCC Article 9 may affect the trustee's security interest in deposit materials; choose a governing state carefully — Delaware and New York are common for technology contracts.",{"code":483,"name":484,"flag_asset_id":485,"note":486},"ca","Canada","flag-ca","Canadian insolvency law under the Companies' Creditors Arrangement Act (CCAA) and the Bankruptcy and Insolvency Act (BIA) does not contain an equivalent to § 365(n), making a well-structured source code trust agreement more — not less — important for Canadian licensees. Quebec civil law may treat trust arrangements differently from common-law provinces; Quebec-based deals should be reviewed by a Quebec-licensed lawyer to confirm the trust structure is valid under the Civil Code.",{"code":488,"name":489,"flag_asset_id":490,"note":491},"uk","United Kingdom","flag-uk","UK law treats software escrow as a standard commercial arrangement with no specific statutory framework — enforceability depends on the trust being properly constituted under the Trustee Act 2000 and the escrow not constituting a registrable charge under the Companies Act 2006. Post-Brexit, UK and EU arrangements require separate governing law clauses; UK contracts should specify English and Welsh law or Scots law explicitly. The UK Financial Conduct Authority and Prudential Regulation Authority expect source code escrow for critical third-party software in regulated financial firms under their operational resilience rules.",{"code":493,"name":494,"flag_asset_id":495,"note":496},"eu","European Union","flag-eu","The EU Digital Operational Resilience Act (DORA), effective January 2025, requires financial entities to include source code access and continuity provisions in ICT contracts with third-party technology providers — making source code trust agreements a compliance obligation rather than a commercial option for many EU financial firms. GDPR may apply if source code includes or processes personal data; the trustee's data processing role should be addressed in a separate Data Processing Agreement. Member state insolvency laws vary significantly; cross-border EU deals should specify a single governing member state law to avoid conflicts.",[243,461,498,499,500,501,502,503,504,505,506,507],"independent-contractor-agreement-D160","intellectual-property-assignment-D5229","service-level-agreement-D778","master-service-agreement-D12657","website-development-agreement-D14084","it-service-agreement-D13422","software-license-agreement-D12928","consulting-agreement-D12711","confidentiality-agreement-D950","joint-venture-agreement-D889",{"emit_how_to":188,"emit_defined_term":188},{"primary_folder":112,"secondary_folder":510,"document_type":511,"industry":512,"business_stage":513,"tags":514,"confidence":520},"intellectual-property-and-licensing","agreement","software-and-technology","all-stages",[515,516,517,518,519],"intellectual-property","source-code-escrow","software-licensing","escrow-agreement","developer-protection",0.92,"\u003Ch2>What is a Source Code Trust Agreement (Development)?\u003C/h2>\n\u003Cp>A \u003Cstrong>Source Code Trust Agreement (Development)\u003C/strong> is a legally binding tripartite contract among a software developer, a licensee, and a neutral trustee that governs the deposit, safekeeping, and conditional release of a software application's source code during and after active development. Unlike a standard software escrow tied to a finished product, the development variant structures ongoing milestone deposits throughout the build process, giving the licensee staged assurance that compilable, complete source code exists at every phase of the project. The trustee — typically a professional escrow service or law firm — holds the materials in trust and releases them to the licensee only when a defined triggering event occurs, such as developer insolvency, material breach, or permanent cessation of support. The developer retains full IP ownership throughout; the licensee receives only a limited, conditional license-back on release.\u003C/p>\n\u003Ch2>Why You Need This Document\u003C/h2>\n\u003Cp>Without a source code trust agreement, a licensee whose developer becomes insolvent, is acquired by a competitor, or simply stops maintaining the software faces a stark choice: rebuild the application from scratch or halt operations. Either outcome can cost six figures in emergency development spend or operational downtime. A trust agreement eliminates that exposure at a fraction of the cost by ensuring the code is held securely by a neutral party who will release it the moment a defined threshold is crossed. For developers, the agreement answers the licensee's continuity objection and closes deals that would otherwise stall on due diligence. This template gives both sides a professionally structured starting point — covering deposit schedules, verification obligations, release conditions, and license-back scope — that can be adapted to any software development arrangement without starting from a blank page.\u003C/p>\n",1781186035130]