[{"data":1,"prerenderedAt":522},["ShallowReactive",2],{"document-source-code-trust-agreement-2-D810":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":177,"customdescription":6,"mdFm":178,"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 \"Software Publisher\"), 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 \"Licensee\"), 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 \"Trustee\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] BACKGROUND 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 the Software Publisher known as [SPECIFY], the Software Publisher 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 Article One) in certain circumstances as more particularly described herein. 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. The Software Publisher acknowledges and agrees that the Software is necessary to the Licensee in its business and that the Licensee has a legitimate right to have access to, and the use of, the Trust Materials in the specific manner contemplated herein to maintain and support the Software. As between them, the Software Publisher 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. The Software Publisher and the Licensee candidly acknowledge their divergent interests regarding Licensee's access to, and use of, the Trust Materials and further acknowledge that they may disagree as to the disclosure and use of the Trust Materials. Accordingly, they have provided for an abbreviated arbitration process, which, while not unduly delaying Licensee's access and use thereof, will ensure that the disclosure and use of the Trust Materials is granted only in appropriate circumstances. The foregoing representations and statements of fact are made by Software Publisher and Licensee and not by the Trustee. The Software Publisher 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: INTERPRETATION 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 \"Article\" or \"Section\" 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], [COUNTRY]. \"Court\" means the [STATE/PROVINCE] Court (General Division) or any other judicial court of either [COUNTRY] or provincial jurisdiction within [COUNTRY]; \"Deposit\" means either an Initial Deposit or Subsequent Deposit; \"Event of Default\" means any one or more of the events set out in Section 6.1; \"Initial Deposit\" has the meaning attributed to it in Section 4.1; \"License Agreement\" means the license agreement dated, [YEAR] in which the Software Publisher licensed the use of the Software to the Licensee, as amended from time to time in accordance with its terms, a copy of which is attached as Schedule A hereto; \"Licensee's Certificate\" means a certificate in the form attached as Schedule B hereto executed by any two senior officers of the Licensee; \"No Change Certificate\" means a certificate in the form attached as Schedule C hereto executed by any two senior officers of the Software Publisher; \"Notice Period\" means the [NUMBER] Business Day period of time commencing on the date the Trustee notifies the Software Publisher that an Event of Default has occurred; \"Parties\" means the Software Publisher, 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 law; \"Software\" means, at any time, that version of the computer software then licensed to the Licensee by 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 D hereto; \"Software Publisher's Certificate\" means a certificate in the form attached as Schedule E hereto executed by any [NUMBER] senior officers of the Software Publisher; \"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 (SPECIFY) language on bond paper suitable for long term archival storage; \"Subsequent Deposit\" has the meaning attributed to it in Section 4.2; \"System Documentation\" means a complete copy, [SPECIFY 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 the Software Publisher 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 F; and \"Trust Materials\" means, at any particular time, those copies of the Source Code and System Documentation that are deposited in trust with the Trustee hereunder. Schedules The following are the schedules attached to and forming part of this Agreement: Schedule A - License Agreement Schedule B - Licensee's Certificate Schedule C - No Change Certificate Schedule D - Description of Software Schedule E - Software Publisher's Certificate Schedule F - Description of System Documentation Schedule G - Environmental Parameters Schedule H - Dispute Resolution Procedure Headings",null,"Source Code Trust Agreement 2","22",136,"doc","https://templates.business-in-a-box.com/imgs/1000px/source-code-trust-agreement-2-D810.png","https://templates.business-in-a-box.com/imgs/250px/810.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#810.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 2","Source Code Trust Agreement 2 Template","https://templates.business-in-a-box.com/imgs/400px/810.png","https://templates.business-in-a-box.com/imgs/600px/810.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,102,117,133,148,162],{"label":38,"url":39,"thumb":40,"extension":10},"Source Code Trust Agreement Development","/template/source-code-trust-agreement-development-D812","https://templates.business-in-a-box.com/imgs/250px/812.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},"Joint Venture Agreement 2","/template/joint-venture-agreement-2-D888","https://templates.business-in-a-box.com/imgs/250px/888.png",{"label":70,"url":71,"thumb":72,"extension":10},"Limited Partnership Agreement 2","/template/limited-partnership-agreement-2-D1009","https://templates.business-in-a-box.com/imgs/250px/1009.png",{"label":74,"url":75,"thumb":76,"extension":10},"Assignment of Deed of Trust","/template/assignment-of-deed-of-trust-D975","https://templates.business-in-a-box.com/imgs/250px/975.png",{"label":78,"url":79,"thumb":80,"extension":10},"Deed of Trust Donation","/template/deed-of-trust-donation-D986","https://templates.business-in-a-box.com/imgs/250px/986.png",{"label":82,"url":83,"thumb":84,"extension":10},"Code Of Conduct","/template/code-of-conduct-D13318","https://templates.business-in-a-box.com/imgs/250px/13318.png",{"description":86,"descriptionCustom":6,"label":87,"pages":88,"size":89,"extension":10,"preview":90,"thumb":91,"svgFrame":92,"seoMetadata":93,"parents":95,"keywords":94,"url":101},"SOFTWARE LICENSE AGREEMENT This Software License Agreement (the \"Agreement\") is effective [DATE], BETWEEN: [FIRST PARTY NAME] (the \"Licensor\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [LICENSEE NAME] (the \"Licensee\"), 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 the Licensor owns [SOFTWARE NAME] (the \"Software\") and wishes to grant a license to the Licensee, along with the right to use and operate the Software in [TERRITORY] (the \"Territory\") and the Licensee agrees to take the said license from the Licensor upon the terms and conditions as set forth in this Agreement. NOW THEREFORE, in consideration of the premises and of the mutual agreements contained in this Agreement, the Parties hereto agree as follows: DEFINITIONS AND INTERPRETATION The following definitions apply throughout this Agreement unless otherwise stated: \"Agreement\" means this Software Licensing Agreement and any amendment made thereto from time to time by the Parties hereto. \"Software\" refers to [SOFTWARE NAME]. \"Derivative Works\" mean works developed by the Licensee, its officers, agents, contractors or employees, which are based upon, in whole or in part, the Source Code and/or the Documentation and may also be based upon and/or incorporate one or more other pre-existing works. Derivative Works may be any Improvement, revision, modification, translation (including compilation or recapitulation by computer), abridgment, condensation, expansion, or any other form in which such a pre-existing work may be recast, transformed, or adapted. For purposes hereof, a Derivative Work shall also include any compilation that incorporates such a pre-existing work. \"Documentation\" means written, printed or otherwise recorded or stored (digital or paper) material relating to the Software and Source Code, including technical specifications and instructions for its use, including Source Code annotations and other descriptions of the principles of operation of the Source Code and tools and instructions for its use. \"Source Code\" means the computer programming Source Code form of the Software in the form provided by the Licensor to the Licensee, and includes all non-third-party executables, libraries, components, and Documentation created or used in the creation, development, maintenance, and support of the Software, as well as all updates, Error corrections and revisions thereto provided by the Licensor, all provided by the Licensor for use, in whole or in part, either by itself or in the development of Derivative Works. \"Improvements\" shall mean, with respect to the Source Code, all modifications and changes made, developed, acquired or conceived after the date hereof and during the entire term of this Agreement. TERM This Agreement shall come into effect on [SPECIFY DATE] and shall continue until termination of this Agreement. GRANT OF LICENSE The Licensor hereunder grants to the Licensee an exclusive, non-transferable, irrevocable, royalty-free license to use and operate the Software in the Territory, including but not limited to the right and license to use and incorporate the Source Code and/or the Documentation, in whole or in part, to develop Derivative Works (including the integration of all or part of the Source Code into the Licensee's own software), and to compile, use, copy, and distribute executable versions of such Derivative Works. The Licensor shall hereunder provide the Source Code and all other Software related information to the Licensee and also hereby allows the Licensee to modify the said Software, change its Source Code, and change its name and logo at any time and at its sole discretion without any notification to the Licensor. The Licensee shall also have the right and license to use and copy the Source Code, in whole or in part, in compiled, object-code form for the Licensee's internal testing and development use and also the right and license to make a reasonable number of backup and archival copies of Source Code and Documentation. The Licensee shall not, however, transfer or sublicense the Software to any third party, in whole or in part, in any form, whether modified or unmodified. DELIVERABLES The Licensor shall hand over the Software, including the Source Code, to the Licensee in order to be used and operated by the Licensee in the Territory within a period of [SPECIFY DAYS OR MONTHS] from the date of signing this Agreement. SUPPORT AND WARRANTY PERIOD For a period of [SPECIFY MONTHS OR YEARS] (the \"Warranty period\") from the date of the deliverables, as mentioned in clause 4 of this Agreement, the Licensor, at no additional charge, shall provide to the Licensee: the Source Code for all upgrades, updates, patches, fixes and other modifications to the Software (\"Software Modifications\"); Error correction services, more specifically, to the extent the Source Code (and/or the files resulting from compiling the Source Code), programming services, instructions and/or source code to correct such Errors to bring the Source Code (and/or the files resulting from compiling the Source Code) into compliance with the representations and warranties set forth in this Agreement. The Licensor shall use commercially reasonable measures to provide Error corrections, or a work-around for such Errors, within [NUMBER OF DAYS] days of notification by the Licensee. Where a work-around is initially provided, the Licensor shall continue to use commercially reasonable efforts to develop an Error correction until such Error correction is delivered. To the extent an Error is intermittent in nature and the Licensee is having problems recreating the Error for the purposes of reporting Errors to the Licensor, the Licensor shall provide assistance to the Licensee in recreating the Error; personnel with levels of expertise (both general technical as well as specifically with respect to the Software and the Source Code) to provide technical support, advice and consultation to the Licensee. Such technical support and assistance shall include, without limitation, support and assistance with respect to the Software, Source Code, and the Licensee's development efforts, and shall also include technical support consulting services for modifications to the Source Code made by the Licensee. LICENSE FEE The Licensee shall pay the Licensor for this license at the rate of [AMOUNT] per [month] payable in advance. The first payment shall be made on the date of the beginning of the period specified above. Subsequent payments shall be made in advance promptly on the [day of each month] thereafter during the continuation of this Agreement. All payments hereunder shall be made in [CURRENCY] currency and via [MODE OF PAYMENT] as the mode of payment. REPRESENTATIONS AND WARRANTIES OF LICENSOR The Licensor hereby represents and warrants that the license granted hereunder to the Licensee has been granted on [SPECIFY \"AN EXCLUSIVE\" OR \"A NON-EXCLUSIVE\"] basis. The Licensor represents and warrants that the Software and services shall be provided in a good and professional manner in accordance with industry practices. The Licensor represents and warrants that the Software shall be bug-free, error-free and compatible with third-party software, and, in case of any bugs etc. in the Software, this shall be rectified by the Licensor free of cost during the Warranty period.","Software License Agreement","8",513,"https://templates.business-in-a-box.com/imgs/1000px/software-license-agreement-D12928.png","https://templates.business-in-a-box.com/imgs/250px/12928.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12928.xml",{"title":94,"description":6},"software license agreement",[96,98],{"label":31,"url":97},"business-legal-agreements",{"label":99,"url":100},"License Agreements","license-agreement","/template/software-license-agreement-D12928",{"description":103,"descriptionCustom":6,"label":104,"pages":105,"size":106,"extension":10,"preview":107,"thumb":108,"svgFrame":109,"seoMetadata":110,"parents":111,"keywords":115,"url":116},"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},[112,114],{"label":17,"url":113},"software-technology-business",{"label":17,"url":113},"custom software development agreement","/template/custom-software-development-agreement-D787",{"description":118,"descriptionCustom":6,"label":119,"pages":120,"size":121,"extension":10,"preview":122,"thumb":123,"svgFrame":124,"seoMetadata":125,"parents":126,"keywords":131,"url":132},"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},[127,128],{"label":31,"url":97},{"label":129,"url":130},"Transfer & Assignment Agreements","transfer-assignment-agreement","intellectual property assignment","/template/intellectual-property-assignment-D5229",{"description":134,"descriptionCustom":6,"label":135,"pages":136,"size":89,"extension":10,"preview":137,"thumb":138,"svgFrame":139,"seoMetadata":140,"parents":142,"keywords":141,"url":147},"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","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":141,"description":6},"non disclosure agreement nda",[143,144],{"label":31,"url":97},{"label":145,"url":146},"Confidentiality Agreements","confidentiality-agreement","/template/non-disclosure-agreement-nda-D12692",{"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":113},{"label":17,"url":113},"service level agreement","/template/service-level-agreement-D778",{"description":163,"descriptionCustom":6,"label":164,"pages":165,"size":166,"extension":10,"preview":167,"thumb":168,"svgFrame":169,"seoMetadata":170,"parents":171,"keywords":175,"url":176},"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},[172],{"label":173,"url":174},"Consultant & Contractors","consulting-contractor-business","independent contractor agreement","/template/independent-contractor-agreement-D160",false,{"seo":179,"reviewer":191,"legal_disclaimer":195,"quick_facts":196,"at_a_glance":198,"personas":202,"variants":227,"glossary":254,"clauses":288,"how_to_fill":339,"common_mistakes":380,"faqs":405,"industries":433,"comparisons":450,"diy_vs_lawyer":465,"jurisdictions":478,"related_template_ids_curated":499,"schema":509,"classification":510},{"meta_title":180,"meta_description":181,"primary_keyword":182,"secondary_keywords":183,"robots":190,"family":182,"is_canonical":177},"Source Code Trust Agreement Template (Free Word)","Free source code trust agreement template for software escrow arrangements. Covers deposit conditions, release triggers, trustee duties, and IP rights. Free Word and PDF download.","source code trust agreement",[184,185,186,187,188,189],"source code escrow agreement template","source code deposit agreement","software source code trust template","source code release agreement","technology escrow agreement template","source code trust agreement word","noindex,follow",{"name":192,"credential":193,"reviewed_date":194},"Bruno Goulet","CEO, Business in a Box","2026-05-02",true,{"difficulty":197,"legal_review_recommended":195,"signature_required":195,"notarization_required":177},"advanced",{"what_it_is":199,"when_you_need_it":200,"whats_inside":201},"A Source Code Trust Agreement is a legally binding three-party contract between a software developer (depositor), an end-user or licensee (beneficiary), and a neutral third-party trustee, under which the developer deposits source code — and related build documentation — with the trustee to be held in escrow and released to the beneficiary only upon defined trigger events. This free Word download gives you a complete, attorney-drafted starting point you can edit online and export as PDF to protect both sides of a critical software licensing relationship.\n","Use it when a business relies on proprietary software it does not own — such as a licensed ERP, custom platform, or embedded firmware — and needs assurance that it can maintain or rebuild the application if the developer ceases operations, fails to maintain the software, or breaches the underlying license. It is also used by developers to formalize deposit obligations agreed to in a software license or development contract.\n","Trustee appointment and duties, deposit specifications and update schedule, release trigger conditions (insolvency, abandonment, material breach), beneficiary access rights upon release, IP ownership and license grants, confidentiality obligations, verification procedures, fees, indemnification, and termination provisions.\n",[203,207,211,215,219,223],{"title":204,"use_case":205,"icon_asset_id":206},"Enterprise software licensees","Securing continuity rights for a mission-critical licensed platform","persona-enterprise-it",{"title":208,"use_case":209,"icon_asset_id":210},"SaaS and software developers","Fulfilling escrow obligations required by an enterprise customer contract","persona-software-developer",{"title":212,"use_case":213,"icon_asset_id":214},"IT procurement managers","Protecting the organization if a key vendor becomes insolvent or exits the market","persona-it-manager",{"title":216,"use_case":217,"icon_asset_id":218},"Startup founders","Structuring escrow terms when licensing proprietary code to a large client","persona-startup-founder",{"title":220,"use_case":221,"icon_asset_id":222},"M&A and legal counsel","Ensuring source code access as a condition of a technology acquisition or joint venture","persona-legal-counsel",{"title":224,"use_case":225,"icon_asset_id":226},"Financial institutions and regulated entities","Meeting regulator requirements for operational continuity and third-party software risk","persona-fintech",[228,232,235,239,243,247,250],{"situation":229,"recommended_template":230,"slug":231},"Two-party arrangement where the developer acts as its own custodian","Software Escrow Agreement (Two-Party)","software-escrow-agreement-D14061",{"situation":233,"recommended_template":234,"slug":231},"Escrow combined with a full software development engagement","Software Development Agreement with Escrow Addendum",{"situation":236,"recommended_template":237,"slug":238},"SaaS product where source code access is tied to service continuity","SaaS Subscription Agreement with Continuity Clause","subscription-agreement-D12537",{"situation":240,"recommended_template":241,"slug":242},"Depositing IP assets beyond source code — designs, databases, and documentation","Technology Asset Escrow Agreement","technology-assignment-agreement-D765",{"situation":244,"recommended_template":245,"slug":246},"Short-term project delivery where code is transferred outright at completion","IP Assignment Agreement","ip-sale-agreement-D964",{"situation":248,"recommended_template":87,"slug":249},"Enterprise licensing deal that governs long-term software use rights","software-license-agreement-D12928",{"situation":251,"recommended_template":252,"slug":253},"Verifying deposit integrity through a formal technical audit","Source Code Verification Agreement","source-code-license-agreement-D807",[255,258,261,264,267,270,273,276,279,282,285],{"term":256,"definition":257},"Trustee","The neutral third party — typically a professional escrow agent or law firm — appointed to hold the deposited source code and administer the agreement.",{"term":259,"definition":260},"Depositor","The software developer or IP owner who delivers the source code and related materials to the trustee under the terms of the agreement.",{"term":262,"definition":263},"Beneficiary","The licensee or end-user who has the right to receive the source code from the trustee upon the occurrence of a defined release trigger.",{"term":265,"definition":266},"Deposit Materials","All items placed with the trustee — including source code files, build instructions, configuration scripts, third-party library lists, and technical documentation.",{"term":268,"definition":269},"Release Trigger","A specific event — such as the depositor's insolvency, material breach, or cessation of maintenance — that entitles the beneficiary to receive the deposit materials.",{"term":271,"definition":272},"Escrow","An arrangement in which assets are held by a neutral third party on behalf of two transacting parties and released only when predetermined conditions are met.",{"term":274,"definition":275},"Verification","A technical audit performed by a qualified examiner to confirm that the deposited source code is complete, current, and capable of producing the licensed software when built.",{"term":277,"definition":278},"Continuity License","A limited, conditional license granted to the beneficiary upon release of the deposit materials, allowing maintenance or operation of the software without the depositor's involvement.",{"term":280,"definition":281},"Material Breach","A failure to perform a fundamental obligation under the underlying software license — such as ceasing support, failing to deliver critical updates, or abandoning the product — that may trigger escrow release.",{"term":283,"definition":284},"Insolvency Event","A formal legal proceeding — voluntary or involuntary bankruptcy, receivership, or assignment for the benefit of creditors — that places the depositor's assets under court or administrator control.",{"term":286,"definition":287},"Update Obligation","The depositor's contractual duty to re-deposit revised source code whenever a new version, patch, or significant update of the licensed software is released.",[289,294,299,304,309,314,319,324,329,334],{"name":290,"plain_english":291,"sample_language":292,"common_mistake":293},"Appointment of trustee and acceptance","Formally names the trustee, confirms their acceptance of the role, and establishes the scope of their duties — limited to holding and releasing the deposit, not interpreting the code.","[DEPOSITOR NAME] and [BENEFICIARY NAME] hereby appoint [TRUSTEE NAME] ('Trustee') as escrow agent under this Agreement. Trustee accepts such appointment and agrees to hold the Deposit Materials in accordance with the terms herein. Trustee's duties are strictly ministerial and Trustee makes no representation regarding the adequacy or functionality of the Deposit Materials.","Failing to expressly limit the trustee's liability to gross negligence or willful misconduct. An unlimited liability clause will cause most professional escrow agents to refuse the appointment or charge significantly higher fees.",{"name":295,"plain_english":296,"sample_language":297,"common_mistake":298},"Deposit specifications and delivery","Defines exactly what must be deposited — file formats, directory structure, build environment, third-party dependencies, and any encryption keys — and the deadline for initial delivery.","Depositor shall deliver to Trustee, no later than [DATE], the Deposit Materials as specified in Schedule A, including: (a) all source code files in [LANGUAGE/FORMAT]; (b) build and compilation instructions sufficient to recreate the Licensed Software; (c) a list of all third-party libraries and licenses; and (d) any configuration or environment files required for deployment.","Describing deposit materials in vague terms such as 'all source code.' Without a specific Schedule A, the beneficiary may receive an incomplete deposit that cannot be built into a working application.",{"name":300,"plain_english":301,"sample_language":302,"common_mistake":303},"Update and refresh obligations","Requires the depositor to deliver updated deposit materials within a set number of days after each new software release, patch, or material change.","Depositor shall deposit updated Deposit Materials with Trustee within [30] days of each new release, update, patch, or material modification to the Licensed Software. Each updated deposit shall replace the prior deposit unless Trustee is instructed in writing to retain prior versions.","Setting no update timeline or making updates discretionary. A deposit that reflects a version from three years ago provides little continuity value to a beneficiary running a current production system.",{"name":305,"plain_english":306,"sample_language":307,"common_mistake":308},"Release trigger conditions","Lists the specific events that entitle the beneficiary to demand release of the deposit materials, along with the notice procedures and any cure period.","Beneficiary may issue a Release Notice to Trustee upon the occurrence of any of the following: (a) Depositor files for bankruptcy or is subject to involuntary insolvency proceedings not dismissed within [60] days; (b) Depositor ceases active maintenance of the Licensed Software for a period exceeding [90] days without written explanation; (c) Depositor commits a material breach of the Underlying License Agreement that remains uncured after [30] days' written notice.","Defining release triggers so broadly — for example, 'any breach of the license agreement' — that the depositor faces constant contested releases. Limit triggers to material, objective events with defined cure periods.",{"name":310,"plain_english":311,"sample_language":312,"common_mistake":313},"Release procedure and dispute resolution","Describes what the beneficiary must include in a release notice, how the trustee notifies the depositor, the depositor's right to object, and how disputes over contested releases are resolved.","Upon receiving a Release Notice, Trustee shall notify Depositor in writing within [5] business days. If Depositor does not object within [15] business days, Trustee shall release the Deposit Materials to Beneficiary. If Depositor objects, the dispute shall be submitted to [ARBITRATION BODY] for expedited resolution within [30] days, and Trustee shall withhold release pending the outcome.","Omitting an expedited dispute resolution mechanism. Without one, a contested release can take months in ordinary litigation, defeating the entire purpose of the escrow arrangement.",{"name":315,"plain_english":316,"sample_language":317,"common_mistake":318},"Continuity license grant","Grants the beneficiary a limited, non-transferable license to use the released source code solely to maintain, support, or operate the software for internal purposes — not to resell or redistribute it.","Upon release of the Deposit Materials, Depositor hereby grants Beneficiary a non-exclusive, non-transferable, royalty-free license to use, modify, and compile the Deposit Materials solely for the purpose of maintaining, supporting, and operating the Licensed Software for Beneficiary's internal business purposes.","Failing to restrict the continuity license to internal use. Without a restriction, the beneficiary could theoretically sublicense or redistribute the source code, far exceeding the intended scope of the escrow protection.",{"name":320,"plain_english":321,"sample_language":322,"common_mistake":323},"Verification procedure","Establishes the beneficiary's right to request a technical audit of the deposit to confirm it is complete, current, and buildable — and allocates the cost of verification between the parties.","Beneficiary may request verification of the Deposit Materials no more than [once per calendar year] at Beneficiary's expense. Trustee shall engage a mutually agreed qualified technical examiner to confirm that the Deposit Materials (a) are complete as specified in Schedule A, (b) correspond to the current production release of the Licensed Software, and (c) can be successfully compiled into a functioning build.","Including no verification right at all. A deposit that has never been tested may be missing build scripts, contain corrupted files, or reflect an outdated version — none of which becomes apparent until a crisis release is attempted.",{"name":325,"plain_english":326,"sample_language":327,"common_mistake":328},"Confidentiality obligations","Binds the trustee and beneficiary to strict confidentiality regarding the deposit materials and permits use only in accordance with the continuity license upon release.","Trustee and Beneficiary agree to hold the Deposit Materials in strict confidence using at least the same degree of care as they use to protect their own most sensitive proprietary information, but no less than reasonable care. Beneficiary shall not reverse-engineer, decompile, or disassemble the Deposit Materials except as expressly permitted by the Continuity License.","Using a standard NDA confidentiality standard for source code escrow. Source code warrants a higher standard — specifically prohibiting reverse engineering and restricting access to named individuals on a need-to-know basis.",{"name":330,"plain_english":331,"sample_language":332,"common_mistake":333},"Trustee fees and party obligations","Sets out the trustee's fee schedule, which party bears each fee (setup, annual custody, verification, and release), and the consequences of non-payment.","Beneficiary shall pay Trustee a one-time setup fee of $[AMOUNT] and an annual custody fee of $[AMOUNT] per year, payable in advance. Verification fees shall be borne by the requesting party. Failure to pay any fee within [30] days of the due date entitles Trustee to suspend its obligations upon [10] days' written notice to all parties.","Leaving fee allocation silent or stating 'as agreed separately.' Fee disputes between depositor and beneficiary about who pays the trustee can stall the entire arrangement before the first deposit is made.",{"name":335,"plain_english":336,"sample_language":337,"common_mistake":338},"Term and termination","States the duration of the agreement, how it can be terminated by any party, what happens to the deposit materials on termination, and survival of key obligations.","This Agreement shall commence on [DATE] and continue until (a) the Underlying License Agreement expires or terminates; (b) all parties agree in writing to terminate; or (c) either party provides [60] days' written notice of termination. Upon termination, Trustee shall return Deposit Materials to Depositor unless a Release Notice is pending. Confidentiality and IP ownership obligations survive termination.","Tying the trust agreement's term exclusively to the underlying license without a notice-based termination right. If the license is amended or replaced, the trust agreement may need to continue under revised terms — requiring flexibility beyond automatic co-termination.",[340,345,350,355,360,365,370,375],{"step":341,"title":342,"description":343,"tip":344},1,"Identify and confirm all three parties","Enter the full legal names and registered addresses of the depositor (software developer), beneficiary (licensee), and trustee (escrow agent or law firm). Confirm the trustee has agreed to act before executing.","Use the same entity name as appears on the underlying software license agreement — mismatched party names create enforceability questions if a release is ever contested.",{"step":346,"title":347,"description":348,"tip":349},2,"Draft Schedule A — the deposit specification","List every item that must be deposited: source code files and directory structure, programming language and version, build toolchain, third-party libraries and their licenses, configuration files, and deployment instructions. Be specific enough that a developer unfamiliar with the project could build the software from the deposit alone.","Have a senior engineer review Schedule A before signing — legal teams routinely under-specify technical requirements, resulting in incomplete deposits.",{"step":351,"title":352,"description":353,"tip":354},3,"Set the update obligation timeline","Choose a realistic update window — 30 days is standard — and define what triggers an update obligation: new major versions, minor releases, and security patches. Decide whether prior versions are retained or replaced.","For rapidly iterating software, require monthly deposits on a rolling schedule rather than event-triggered updates — it simplifies compliance.",{"step":356,"title":357,"description":358,"tip":359},4,"Define the release triggers precisely","List each trigger event with objective, measurable criteria. Include insolvency events, cessation of maintenance, and material breach with defined cure periods. Avoid vague language like 'failure to support.'","Cross-reference the release triggers against the maintenance and support obligations in the underlying license to ensure alignment — contradictions between the two documents create contested-release risk.",{"step":361,"title":362,"description":363,"tip":364},5,"Set the release and dispute procedure","Specify the form and contents of a release notice, the trustee's notification timeline, the depositor's objection window, and the forum for expedited dispute resolution. Most parties use AAA or JAMS expedited arbitration.","Agree on a specific arbitration provider and seat city in the agreement — having to negotiate those details during a contested release adds days of delay when time matters most.",{"step":366,"title":367,"description":368,"tip":369},6,"Draft the continuity license terms","Confirm the scope of the license granted upon release — internal use only, no redistribution, no sublicensing. State whether the beneficiary may engage a third-party contractor to perform maintenance under the continuity license.","Expressly permit the beneficiary to hire a maintenance contractor, with the contractor bound by the same confidentiality obligations as the beneficiary — otherwise a key practical use of the release is legally ambiguous.",{"step":371,"title":372,"description":373,"tip":374},7,"Agree on fees and allocate them in writing","Confirm setup, annual custody, verification, and release fees with the trustee. Allocate each fee to a party and include a payment timeline with consequences for late payment.","Obtain a fee schedule in writing from the trustee before executing the agreement — trustee fees vary widely ($500–$5,000+ annually) and material fee surprises post-signing create disputes.",{"step":376,"title":377,"description":378,"tip":379},8,"Execute before or simultaneously with the underlying license","Sign the trust agreement on or before the effective date of the software license it supports. All three parties must execute. The depositor should make the first deposit within the agreed window — do not allow the first deposit to slip past the signature date.","Schedule a calendar reminder for the first deposit deadline the moment the agreement is signed — depositors routinely miss the initial delivery deadline because no one tracked it.",[381,385,389,393,397,401],{"mistake":382,"why_it_matters":383,"fix":384},"Vague or incomplete deposit specification","A deposit described only as 'all source code' may arrive without build scripts, environment files, or dependency lists — rendering the deposit unbuildable in a crisis release scenario.","Require a detailed Schedule A signed by a technical lead, listing every component needed to compile and deploy the software from scratch in an isolated environment.",{"mistake":386,"why_it_matters":387,"fix":388},"No update obligation or discretionary update language","Software evolves continuously. An escrow holding a three-year-old codebase provides no protection to a beneficiary running the current production version.","Set a mandatory update window — 30 days after each release — and include a depositor certification that each new deposit reflects the current production version.",{"mistake":390,"why_it_matters":391,"fix":392},"Overbroad release triggers without cure periods","Triggers covering any breach of the license agreement expose the depositor to contested releases for minor or disputed infractions, creating operational and legal disruption disproportionate to the issue.","Limit triggers to material, objectively verifiable events — insolvency, cessation of maintenance for 90+ days, or uncured material breach after 30 days' written notice.",{"mistake":394,"why_it_matters":395,"fix":396},"No verification right included","Without a right to test the deposit, the beneficiary has no way to confirm the escrow contains a buildable, current copy of the software until a crisis event forces a release — often too late to be useful.","Include an annual verification right at the beneficiary's expense, performed by a mutually agreed technical examiner, confirming completeness and buildability.",{"mistake":398,"why_it_matters":399,"fix":400},"Continuity license silent on third-party maintenance","Upon release, the beneficiary will almost certainly need to hire an outside developer to maintain the software. A license that permits only the beneficiary's own employees to use the code makes this practically impossible.","Expressly permit the beneficiary to engage authorized contractors under a written confidentiality obligation, with the depositor's source code treated as third-party confidential information.",{"mistake":402,"why_it_matters":403,"fix":404},"Trust agreement terminates automatically with the license","Software licenses are amended, assigned, or replaced regularly. Auto-termination of the escrow leaves gaps in protection during transition periods when the risk of developer failure may actually be higher.","Include a notice-based termination right — minimum 60 days — that operates independently of the license, so the beneficiary can maintain escrow coverage through license transitions.",[406,409,412,415,418,421,424,427,430],{"question":407,"answer":408},"What is a source code trust agreement?","A source code trust agreement — also called a software escrow agreement — is a three-party contract in which a software developer deposits source code and build documentation with a neutral trustee, to be held in escrow and released to the licensee only when defined trigger events occur, such as the developer's insolvency or abandonment of the software. It gives enterprise users continuity protection without requiring them to own the source code outright. The trustee acts as a neutral custodian and has no obligation to evaluate the quality or adequacy of the deposited code.\n",{"question":410,"answer":411},"When should a business require a source code trust agreement?","Any business that depends on third-party proprietary software for critical operations should consider requiring escrow as a condition of the license. This includes ERP platforms, custom-built applications, embedded firmware, and SaaS products where loss of vendor support would halt operations. Financial regulators in the US, UK, and EU increasingly require escrow arrangements as part of third-party technology risk management programs, particularly for banks, insurers, and critical infrastructure operators.\n",{"question":413,"answer":414},"What is the difference between a source code trust agreement and a standard software license?","A software license grants the right to use the compiled, executable version of software without providing access to the underlying source code. A source code trust agreement is a separate contract that creates a conditional right to access the source code itself — allowing the licensee to maintain, modify, or rebuild the software independently if the developer is no longer able to support it. The two documents work together: the license governs day-to-day use; the trust agreement protects continuity in a failure scenario.\n",{"question":416,"answer":417},"Who typically acts as trustee in a source code trust agreement?","Professional escrow service providers (such as NCC Group, Iron Mountain, or specialized software escrow companies), law firms acting as neutral custodians, and in some cases financial institutions serve as trustees. The trustee's role is strictly ministerial — holding the deposit and following the release procedure — not evaluating the code. Annual fees for professional trustees typically range from $500 to $5,000 depending on the complexity of the deposit and the number of beneficiaries.\n",{"question":419,"answer":420},"What should be included in the deposit materials?","A complete deposit should include all source code files organized by directory structure, the programming language and version used, build and compilation instructions, a list of all third-party libraries and their licenses, configuration and environment files, database schemas, and any encryption keys required to run the software. The deposit should be specific enough that a developer who has never seen the codebase could build and deploy the application from the escrow contents alone. This specification is typically captured in a Schedule A attached to the agreement.\n",{"question":422,"answer":423},"How often does the source code deposit need to be updated?","The standard practice is to require the depositor to refresh the deposit within 30 days of each new software release, major update, or security patch. For rapidly iterating software, monthly rolling deposits are common. The agreement should specify that each update replaces or supplements the prior deposit and must be accompanied by a depositor certification that the new materials reflect the current production version.\n",{"question":425,"answer":426},"What happens when a release trigger occurs?","The beneficiary sends a formal release notice to the trustee describing the trigger event. The trustee notifies the depositor, who has a defined window — typically 15 business days — to object. If no objection is filed, the trustee releases the deposit materials to the beneficiary. If the depositor objects, the dispute goes to expedited arbitration and the trustee holds the materials pending resolution. The beneficiary then uses the released code under the continuity license to maintain or operate the software.\n",{"question":428,"answer":429},"Is a source code trust agreement legally enforceable?","A properly executed source code trust agreement is generally enforceable in most common-law and civil-law jurisdictions as a valid three-party contract. Enforceability depends on the trustee being a genuinely independent party, the release triggers being defined with sufficient specificity to be objectively verifiable, and the continuity license being clearly scoped. In insolvency scenarios, the deposit materials may be treated as assets of the estate — requiring the agreement to be structured carefully to survive an automatic stay or administration moratorium, particularly in the US and UK.\n",{"question":431,"answer":432},"Do I need a lawyer to set up a source code trust agreement?","For straightforward domestic arrangements with a professional escrow provider and a standard trigger structure, a high-quality template reviewed by counsel is often sufficient. Legal review is strongly recommended for cross-border arrangements, heavily regulated industries, agreements involving significant IP value, or situations where the trustee is not a professional escrow service. The agreement interacts with insolvency law in ways that require jurisdiction-specific expertise to get right.\n",[434,438,442,446],{"industry":435,"icon_asset_id":436,"specifics":437},"Financial Services and Banking","industry-fintech","Regulatory requirements from the FCA, OCC, and EBA mandate operational continuity plans that frequently include software escrow for third-party core banking and trading systems.",{"industry":439,"icon_asset_id":440,"specifics":441},"Healthcare and MedTech","industry-healthtech","FDA-regulated software and clinical systems require validated build environments — deposit specifications must include the exact compiler version, OS, and validation documentation to maintain regulatory compliance after a release.",{"industry":443,"icon_asset_id":444,"specifics":445},"SaaS and Technology","industry-saas","Enterprise SaaS customers increasingly require escrow as a procurement condition; developers use the trust agreement to formalize deposit obligations already referenced in their master subscription agreements.",{"industry":447,"icon_asset_id":448,"specifics":449},"Manufacturing and Industrial","industry-manufacturing","Embedded firmware and industrial control system software create single-vendor dependency risk; a trust agreement ensures production lines can continue operating if the firmware developer exits the market.",[451,454,458,461],{"vs":87,"vs_template_id":452,"summary":453},"software-license-agreement-D812","A software license agreement grants the right to use compiled, executable software and defines payment, support, and termination terms. It does not give the licensee access to source code. A source code trust agreement is a companion document that creates conditional access to the source code itself, providing continuity protection that the license alone cannot deliver. Both documents are typically executed simultaneously.",{"vs":455,"vs_template_id":456,"summary":457},"Software Development Agreement","software-development-agreement-D813","A software development agreement governs the creation of custom software — deliverables, milestones, payment, and IP ownership. When the developer retains IP ownership under the development agreement, a source code trust agreement is added to give the commissioning party continuity rights without requiring full IP transfer. If IP is fully assigned to the client, a separate trust agreement is unnecessary.",{"vs":245,"vs_template_id":459,"summary":460},"intellectual-property-assignment-agreement-D12708","An IP assignment transfers full ownership of the source code to the assignee — no trustee, no conditions, no escrow. A trust agreement is used when the developer retains ownership but the licensee needs continuity protection. If the developer is willing to transfer ownership outright, an assignment provides stronger protection than escrow, but most commercial developers will not agree to outright assignment of a product they continue to license broadly.",{"vs":462,"vs_template_id":463,"summary":464},"Non-Disclosure Agreement","non-disclosure-agreement-nda-D12692","An NDA protects confidential information shared between parties but creates no obligation to deposit, hold, or release materials. A source code trust agreement includes confidentiality provisions as one component but goes much further — establishing a three-party custodial structure, a release mechanism, and a continuity license. Executing only an NDA before sharing source code provides no structural protection against developer failure.",{"use_template":466,"template_plus_review":470,"custom_drafted":474},{"best_for":467,"cost":468,"time":469},"Straightforward domestic escrow arrangements with a professional trustee and a single beneficiary","Free","1–3 hours to customize and negotiate",{"best_for":471,"cost":472,"time":473},"Agreements involving significant IP value, regulated industries, or cross-border parties","$500–$1,500 for a technology lawyer review","3–7 days",{"best_for":475,"cost":476,"time":477},"Multi-beneficiary escrow, insolvency-resilient structures, enterprise transactions over $1M in software value, or heavily regulated environments","$2,500–$8,000+","2–4 weeks",[479,484,489,494],{"code":480,"name":481,"flag_asset_id":482,"note":483},"us","United States","flag-us","Under US bankruptcy law, an automatic stay may temporarily prevent release of escrowed materials when the depositor files for Chapter 11. Structuring the trust agreement to qualify as an executory contract with a clear IP license component — and including an explicit Section 365(n) election — helps preserve the beneficiary's rights during reorganization proceedings. State trade secret laws (Uniform Trade Secrets Act in most states, Defend Trade Secrets Act federally) apply to source code confidentiality obligations.",{"code":485,"name":486,"flag_asset_id":487,"note":488},"ca","Canada","flag-ca","Canadian insolvency proceedings under the Companies' Creditors Arrangement Act (CCAA) and the Bankruptcy and Insolvency Act (BIA) may affect release rights similarly to US Chapter 11. Quebec civil law governs contracts executed in the province; French-language requirements under the Charter of the French Language may apply to agreements with Quebec-based entities. IP ownership and license survival should be expressly addressed for cross-provincial arrangements.",{"code":490,"name":491,"flag_asset_id":492,"note":493},"uk","United Kingdom","flag-uk","UK administration proceedings can impose a moratorium that delays release of escrowed materials. The agreement should include an express statement that the deposit and the continuity license are intended to survive administration under the Insolvency Act 1986. The UK's Software Directive (derived from the EU Copyright Directive) governs lawful decompilation rights and should be considered when drafting the continuity license scope. FCA-regulated firms face specific third-party technology resilience requirements under PS21/3.",{"code":495,"name":496,"flag_asset_id":497,"note":498},"eu","European Union","flag-eu","GDPR applies if the deposit materials include personal data — which is uncommon but possible for analytics or user-data processing modules. The EU's DORA regulation (Digital Operational Resilience Act), effective January 2025, mandates that financial entities maintain contractual arrangements ensuring access to critical software, effectively requiring escrow for many licensed systems. Member state insolvency laws vary significantly; German and French proceedings have different moratorium rules affecting release timelines.",[249,500,501,463,502,503,504,505,506,507,238,508],"custom-software-development-agreement-D787","intellectual-property-assignment-D5229","service-level-agreement-D778","independent-contractor-agreement-D160","it-service-agreement-D13422","master-service-agreement-D12657","joint-venture-agreement-D889","confidentiality-agreement-D950","software-maintenance-agreement-D805",{"emit_how_to":195,"emit_defined_term":195},{"primary_folder":97,"secondary_folder":511,"document_type":512,"industry":513,"business_stage":514,"tags":515,"confidence":520},"intellectual-property-and-licensing","agreement","software-and-technology","all-stages",[516,517,518,519],"intellectual-property","source-code-escrow","software-licensing","escrow-agreement",0.92,"\u003Ch2>What is a Source Code Trust Agreement?\u003C/h2>\n\u003Cp>A \u003Cstrong>Source Code Trust Agreement\u003C/strong> is a legally binding three-party contract among a software developer (the depositor), a licensee or end-user (the beneficiary), and a neutral custodian (the trustee), under which the developer places source code — together with all build instructions, dependencies, and technical documentation — with the trustee to be held in escrow and released to the beneficiary only upon the occurrence of precisely defined trigger events. Unlike a standard software license, which grants rights to compiled executable software only, a source code trust agreement gives the beneficiary a conditional pathway to the underlying code itself: the raw materials needed to maintain, modify, or rebuild the application independently if the developer is no longer able to fulfil its obligations. The trustee's role is strictly administrative — holding and releasing the deposit according to the contract's terms — not evaluating the quality or completeness of what was deposited.\u003C/p>\n\u003Ch2>Why You Need This Document\u003C/h2>\n\u003Cp>Every business that runs critical operations on third-party proprietary software faces a single-vendor continuity risk: if the developer becomes insolvent, is acquired, abandons the product, or simply stops providing support, the licensee may find itself unable to maintain, repair, or operate software it depends on daily — with no legal right to look under the hood. Without a source code trust agreement in place before that failure occurs, obtaining access to the source code through litigation or insolvency proceedings can take months or years. Regulators in the financial services, healthcare, and critical infrastructure sectors increasingly treat software escrow not as a best practice but as a mandatory component of third-party risk management. For developers, a well-drafted trust agreement fulfills enterprise procurement requirements, signals operational maturity, and avoids ad-hoc source code disclosure demands. This template gives both sides a proven, balanced starting point — covering deposit specifications, update obligations, release triggers, continuity licensing, and verification rights — that can be customized and executed in hours rather than weeks of from-scratch drafting.\u003C/p>\n",1781186035127]