[{"data":1,"prerenderedAt":521},["ShallowReactive",2],{"document-source-code-trust-agreement-licensed-program-D813":3},{"document":4,"label":21,"preview":11,"thumb":22,"description":5,"descriptionCustom":6,"apiDescription":5,"pages":8,"extension":10,"parents":23,"breadcrumb":27,"related":35,"customDescModule":171,"customdescription":6,"mdFm":172,"mdProseHtml":520},{"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: [FIRST PARTY NAME] (the \"Depository\"), 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: [SECOND PARTY NAME] (the \"Trustee\"), a trust company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [THIRD PARTY NAME] (the \"Beneficiary\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] WHEREAS, in partial consideration of Beneficiary agreeing to enter into a \"License Agreement\" with Depository and Beneficiary as of (the \"License Agreement\") for the use of Licensed Programs more fully described in Schedule [SPECIFY] to the License Agreement (the \"Licensed Program\"), Depository has agreed to enter into this agreement which will make available to Beneficiary the source code of the Licensed Program and certain related materials required for the maintenance and support of the Licensed Program (the \"Source Materials\", as more particularly described in Section 4 hereof) in certain circumstances as more particularly described herein. WHEREAS Beneficiary acknowledges and agrees that, as an integral part of maintaining the value of the trade secrets and other proprietary interests associated with the Licensed Program, Beneficiary's access to, and use of, the Source Materials shall be expressly limited as more particularly described herein. WHEREAS Depository acknowledges and agrees that the Licensed Program is necessary to Beneficiary in its business and that Beneficiary has a legitimate right to have access to, and the use of, the Source Materials in the specific manner contemplated herein to maintain and support the Licensed Program. WHEREAS, as between them, Depository and Beneficiary acknowledge that this agreement reflects a reasonable balance of their respective needs and concerns respecting access to, and the use of, the Source Materials. WHEREAS the foregoing representations and statements of fact are made by Depository and Beneficiary and not by the Trustee. WHEREAS Depository and Beneficiary 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 [COMPANY NAME] 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: \"Affiliates and Subsidiaries\" have the meaning ascribed to them under the [COUNTRY] Business Corporations [ACT/LAW/RULE], [NUMBER], as amended. \"Agreement\" means this Source Code Source Agreement and all exhibits 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] and [STATE/PROVINCE]; \"Court\" means the [STATE/PROVINCE] Court (General Division) or any other judicial court of either [COUNTRY] or provincial jurisdiction within [COUNTRY]; \"Beneficiary\" means Beneficiary, or division designated herein or any successor (whether by change of name, dissolution, merger, consolidation, reorganization or otherwise) to such corporation or division or its business assets along with actual or future Affiliates and Subsidiaries of Beneficiary. \"Deposit\" means either an Initial Deposit or Subsequent Deposit; \"Depository's Certificate\" means a certificate in the form attached as Exhibit [SPECIFY] hereto executed by any two senior officers of Depository; \"Event of Default\" means any one or more of the events set out in Section 6.1 hereof; \"Initial Deposit\" has the meaning attributed to it in Section 4.1 hereof; \"Beneficiary's Certificate\" means a certificate in the form attached as Exhibit [SPECIFY] hereto executed by any two senior officers of Beneficiary; \"No Change Certificate\" means a certificate in the form attached as Exhibit [SPECIFY] hereto executed by any two senior officers of Depository; \"Notice Period\" means the [NUMBER] Business Day period of time commencing on the date the Trustee notifies Depository that an Event of Default has occurred; \"Parties\" means Depository, the Trustee and Beneficiary 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; \"Licensed Program\" means, at any time, that version of the Licensed Program then licensed to Beneficiary by Depository, 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 [SPECIFY] to the License Agreement hereto; \"Maintenance Agreement\" shall be deemed to include Depository's obligations with respect to the Licensed Program under and during the \"Warranty Period\" set forth in of the License Agreement as well as [any agreement between Depository and Beneficiary for the provision of maintenance and/or support services with respect to the Licensed Program] [a [\"Maintenance Agreement\"] entered into as of between Depository and Licensee, as the same may be amended, extended or replaced]. \"Source Code\" means a complete copy of the source code version of the Licensed Program, 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 Beneficiary and which, when compiled, will produce the object code version of the Licensed Program; and human-readable form with annotations in the (English) language on bond paper suitable for long term archival storage; \"Source Documentation\" means a complete copy, in English, 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 Licensed Program as may be required by Beneficiary, using a competent computer programmer possessing ordinary skills and experience, to further develop, maintain and operate the Licensed Program without further recourse to Depository 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 Exhibit [SPECIFY] hereto; and \"Source Materials\" means, at any particular time, those copies of the Source Code and Source Documentation which are deposited in trust with the Trustee hereunder. Exhibits The following are the exhibits attached to and forming part of this Agreement: Exhibit [SPECIFY] - Beneficiary's Certificate Exhibit [SPECIFY] - No Change Certificate Exhibit [SPECIFY] - Depository's Certificate Exhibit [SPECIFY] - Arbitration Exhibit [SPECIFY] - Trustee's Fees Headings",null,"Source Code Trust Agreement Licensed Program","20",124,"doc","https://templates.business-in-a-box.com/imgs/1000px/source-code-trust-agreement_licensed-program-D813.png","https://templates.business-in-a-box.com/imgs/250px/813.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#813.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 licensed program","Source Code Trust Agreement Licensed Program Template","https://templates.business-in-a-box.com/imgs/400px/813.png",[24,16,19],{"label":25,"url":26},"Templates","/templates/",[28,29,32],{"label":25,"url":26},{"label":30,"url":31},"Legal Agreements","/templates/business-legal-agreements/",{"label":33,"url":34},"Intellectual Property & Licensing","/templates/intellectual-property-and-licensing/",[36,40,44,48,52,56,60,64,68,72,76,80,84,101,116,132,147,159],{"label":37,"url":38,"thumb":39,"extension":10},"Source Code Trust Agreement 2","/template/source-code-trust-agreement-2-D810","https://templates.business-in-a-box.com/imgs/250px/810.png",{"label":41,"url":42,"thumb":43,"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":45,"url":46,"thumb":47,"extension":10},"Source Code License Agreement","/template/source-code-license-agreement-D807","https://templates.business-in-a-box.com/imgs/250px/807.png",{"label":49,"url":50,"thumb":51,"extension":10},"Source Code Escrow Agreement","/template/source-code-escrow-agreement-D806","https://templates.business-in-a-box.com/imgs/250px/806.png",{"label":53,"url":54,"thumb":55,"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":57,"url":58,"thumb":59,"extension":10},"Voting Trust Agreement","/template/voting-trust-agreement-D926","https://templates.business-in-a-box.com/imgs/250px/926.png",{"label":61,"url":62,"thumb":63,"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":65,"url":66,"thumb":67,"extension":10},"Affiliate Program Agreement","/template/affiliate-program-agreement-D743","https://templates.business-in-a-box.com/imgs/250px/743.png",{"label":69,"url":70,"thumb":71,"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":73,"url":74,"thumb":75,"extension":10},"Deed of Trust Donation","/template/deed-of-trust-donation-D986","https://templates.business-in-a-box.com/imgs/250px/986.png",{"label":77,"url":78,"thumb":79,"extension":10},"Code Of Conduct","/template/code-of-conduct-D13318","https://templates.business-in-a-box.com/imgs/250px/13318.png",{"label":81,"url":82,"thumb":83,"extension":10},"Code of Ethics","/template/code-of-ethics-D704","https://templates.business-in-a-box.com/imgs/250px/704.png",{"description":85,"descriptionCustom":6,"label":86,"pages":87,"size":88,"extension":10,"preview":89,"thumb":90,"svgFrame":91,"seoMetadata":92,"parents":94,"keywords":93,"url":100},"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":93,"description":6},"software license agreement",[95,97],{"label":30,"url":96},"business-legal-agreements",{"label":98,"url":99},"License Agreements","license-agreement","/template/software-license-agreement-D12928",{"description":102,"descriptionCustom":6,"label":103,"pages":104,"size":105,"extension":10,"preview":106,"thumb":107,"svgFrame":108,"seoMetadata":109,"parents":110,"keywords":114,"url":115},"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},[111,113],{"label":17,"url":112},"software-technology-business",{"label":17,"url":112},"custom software development agreement","/template/custom-software-development-agreement-D787",{"description":117,"descriptionCustom":6,"label":118,"pages":119,"size":120,"extension":10,"preview":121,"thumb":122,"svgFrame":123,"seoMetadata":124,"parents":125,"keywords":130,"url":131},"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},[126,127],{"label":30,"url":96},{"label":128,"url":129},"Transfer & Assignment Agreements","transfer-assignment-agreement","intellectual property assignment","/template/intellectual-property-assignment-D5229",{"description":133,"descriptionCustom":6,"label":134,"pages":135,"size":88,"extension":10,"preview":136,"thumb":137,"svgFrame":138,"seoMetadata":139,"parents":141,"keywords":140,"url":146},"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":140,"description":6},"non disclosure agreement nda",[142,143],{"label":30,"url":96},{"label":144,"url":145},"Confidentiality Agreements","confidentiality-agreement","/template/non-disclosure-agreement-nda-D12692",{"description":148,"descriptionCustom":6,"label":149,"pages":87,"size":88,"extension":10,"preview":150,"thumb":151,"svgFrame":152,"seoMetadata":153,"parents":155,"keywords":154,"url":158},"IT SERVICE AGREEMENT This IT Service Agreement (the \"Agreement\") is effective on [DATE], BETWEEN: [NAME OF THE SERVICE PROVIDER], (the \"Service Provider\"), an individual with their main address located at OR a Company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [NAME OF THE CLIENT], (the \"Client\"), an individual with their main address located at OR a Company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] Collectively, the Service Provider and Client shall be referred to as the \"Parties\" and individually as the \"Party.\" WHEREAS, the Service Provider is in the business of providing establishing, operating and managing Information Technology and suggesting solutions as the Client wishes, and the Client desires to hire the Service Provider for various IT services; and WHEREAS, the Client and Service Provider desire to enter into an Agreement, which will define respective rights and duties as to all services to be performed; WHEREAS, the Parties wish to evidence their contract in writing; WHEREAS, the Service Provider affirms to understand all of the provisions contained in this Agreement, and in case the Client requires clarification as to one or more of the provisions contained herein, it can request clarification or otherwise seek legal guidance; NOW, THEREFORE, in consideration and as a condition of the Parties entering into this Agreement and other valuable considerations, the receipt and sufficiency of which consideration is acknowledged, the Parties agree as follows: DEFINITIONS \"Intellectual Property\" shall mean any and all technology, technical information, technical data, inventions, invention disclosures, discoveries, processes, formulae, algorithms, know-how, software, designs, design elements, works of authorship, drawings, non-public materials and any other technical subject matter related thereto. Intellectual Property also includes all Intellectual Property rights or similar proprietary rights related to the foregoing, in any jurisdiction, whether owned or held for use under license, whether registered or unregistered, including (i) patent rights and utility models, (ii) copyrights and database rights, (iii) trademarks and trade dress and the goodwill associated therewith, (iv) trade secrets, (v) mask works, and (vi) industrial design rights; in each case, including any registrations of, applications to register, and renewals and extensions of, any of the foregoing with or by any governmental authority in any jurisdiction. \"Service(s)\" shall mean the IT services being provided by the Service Provider to the Client under this Agreement. \"Confidential Information\" will include all data and information relating to the business and management of the Company, including but not limited to, Client lists, business policies, business strategies, proprietary and trade secret technology to which access is obtained by the Service Provider, including accounting records, computer software, other proprietary data, business operations, marketing development operations and customer information. \"Disclosing Party\" shall mean the Party who shall be disseminating the Confidential Information to the Receiving Party. \"Receiving Party\" shall mean the Party to whom the Confidential Information is disclosed. TERM The Client and the Service Provider agree that the present Agreement shall be in force from the [DATE] unless terminated by either of the Parties in accordance with the present Agreement. SCOPE OF THE AGREEMENT The Service Provider shall provide the IT Services and satisfy the responsibilities described in this Agreement as it may be supplemented, enhanced or modified, upon mutual written agreement of the Parties, during the Term. SERVICES WORK ORDER: The Service Provider agrees to provide IT Services to the Client in accordance with the terms and conditions of this Agreement. A description of the Services to be provided shall be set forth in one or more mutually agreed upon documents (hereinafter referred as \"Work Order\" or \"WO\"), each of which, upon execution by the Service Provider and the Client, shall become binding between the Parties and made a part hereof. Each Work Order entered into by the Parties in connection herewith shall be subject to, and the obligations of the Parties hereunder shall be performed in accordance with, the terms and conditions of this Agreement. Each Work Order shall: supplement and form a part of this Agreement, be read and construed as one with this Agreement, be deemed incorporated by reference herein. In the event of any conflict between the terms of this Agreement and any Work Order, the terms of this Agreement shall govern and control unless such Work Order expressly indicates otherwise. PERFORMANCE OF THE SERVICES The Service Provider agrees to perform the Services specified by the Client in a professional manner and in accordance with this Agreement. Notwithstanding the foregoing, the Client acknowledges that the Service Provider's ability to perform the Services will require the Client to timely perform certain tasks and provide certain tangible and intangible items. The Client hereby agrees to perform its obligations hereunder, and the Parties acknowledge that the Client's failure to perform such obligations may adversely affect the Service Provider's ability to meet its performance obligations under the conditions specified by the Client. In addition, the Service Provider shall not be deemed to be in default under this Agreement for any delays or failure to meet its obligations if based on the Client's actions, omissions or failure to meet its performance requirements. If any services, functions or responsibilities not specifically described in this Agreement are inherent subtasks of the Services and are reasonably necessary for provision of the Services, they shall be deemed to be implied by and included within the scope of the Services to the same extent and in the same manner as if specifically described in this Agreement. RELATIONSHIP OF PARTIES Nothing contained in this Agreement shall create an employer and employee relationship, a master and servant relationship, or a principal and agent relationship between the Service Provider and the Client. ASSIGNMENT The Parties shall not assign any rights under the present Agreement to any other Party without the mutual written consent of the Parties. Subject to the foregoing, this Agreement will be binding upon the Parties' heirs, executors, successors and assigns. PAYMENT The Service Provider shall invoice the Client monthly for time and material-based fees, as per the rates specified in the WO, for the Services. The invoices should be accompanied with the time sheets supporting monthly billing information, as the case may be, signed off by the Client. The Client shall pay the Service Provider amounts under an undisputed invoice within [NUMBER OF DAYS] days from the receipt by the Client of payment of the Service Provider's invoice to the Client in respect of the Services provided by the relevant Assigned Employees. The Service Provider shall be solely responsible for paying all expenses incurred by the Service Provider before, during and after the Term of this Agreement that are related in any way and manner to the fulfillment of the Service Provider's obligations flowing from this Agreement. All payments to the Service Provider are to be made in the currency specified in the WO, subject to deduction of tax at source, if any, or withholding taxes. On receipt of the invoices, the Client shall cross check the invoices and if it has a dispute in regard to the raised invoices, then it shall notify the Service Provider about the dispute in writing mandatorily within seven (7) days of the receipt of the invoice","IT Service Agreement","https://templates.business-in-a-box.com/imgs/1000px/it-service-agreement-D13422.png","https://templates.business-in-a-box.com/imgs/250px/13422.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13422.xml",{"title":154,"description":6},"it service agreement",[156,157],{"label":30,"url":96},{"label":30,"url":96},"/template/it-service-agreement-D13422",{"description":160,"descriptionCustom":6,"label":161,"pages":119,"size":88,"extension":10,"preview":162,"thumb":163,"svgFrame":164,"seoMetadata":165,"parents":167,"keywords":166,"url":170},"SAAS AGREEMENT This Software-as-a-Service Agreement (SaaS) (\"Agreement\") is made and effective the [DATE], BETWEEN: [COMPANY NAME], (the \"Customer\"), a corporation organized and existing under the laws of [STATE], with its head office located at: [COMPLETE ADDRESS] AND: [COMPANY NAME], (the \"Provider\"), a corporation organized and existing under the laws of [STATE], with its head office located at: [COMPLETE ADDRESS] WHEREAS, The Customer is granted a license to use the Software, subject to a set of limitations and restrictions. WHEREAS, The Provider undertakes to provide high-performance Software while committing to comply with certain requirements relating to the maintenance of the Software. In consideration of the terms of this agreement, and other valuable consideration, the parties agree as follows: DEFINITION \"Administrator User\" means each Customer employee designated by Customer to serve as technical administrator of the SaaS Services on Customer's behalf. Each Administrator User must complete training and qualification requirements reasonably required by [PROVIDER NAME]. \"Confidential Information\" means any information disclosed by a party to the other party, directly or indirectly, which could be in orally or written (graphic, machine-readable or other tangible form], is marked as \"confidential\" or \"proprietary\". \"Host\" means the computer equipment on which the Software is installed, which is owned and operated by [PROVIDER NAME] or its subcontractors. \"Maintenance Services\" means the support and maintenance services provided by [PROVIDER NAME] to Customer pursuant to this SaaS Agreement. \"Software\" means the object code version of any Software to which Customer is provided access as part of the Service, including any updates or new versions. \"SaaS Services\" refer to the specific [PROVIDER NAME]'s internet-accessible service identified in a Schedule that provides use of [PROVIDER NAME]'s identity/access management Software that is hosted by [PROVIDER NAME] or its services provider and made available to Customer over a network on a term-use basis. SERVICE The Provider hereby grants the Customer, including all authorized users of the Customer, a non-exclusive, non-sublicensable, non-assignable, royalty-free, worldwide license to access and use the service (the \"Service\") solely for the internal business operations of the Customer in accordance with the terms of this Agreement and the Provider's online terms of use. TERM AND TERMINATION The term of this Agreement shall begin on the Effective Date and shall end [SPECIFY]. PAYMENT TERM [SPECIFY] is sold as a Software-as-a-Service (SaaS) and requires Clients to have a valid membership subscription. We accept payments with Credit Cards and Visa and Mastercard Debit Cards [OR SPECIFY]. Your subscription will renew automatically at the end of the subscription term unless you opt-out from automatic renewal or cancel your membership. You can update your payment method, manage your subscription, or cancel at any time by visiting the Billing page under your user account. By purchasing this software, you agreed to enroll in our automatic renewal service. This keeps your products up and running, automatically charging then-current renewal fees to your payment method on file, with no further action on your part. Account cancellation policy: Once a user submits a request for cancellation, no additional charges will be made. However, no refunds are provided upon cancellation. If you cancel before an upcoming renewal date, you will have access to your Account through the end of the then-current year. Cancellation of automatic renewal: Annual subscriptions purchased will renew automatically at the end of the term. Your credit card is charged at the end of each subscription period and a renewal confirmation notice is sent to the account administrator's email address. Notifications of upcoming renewal is sent to the account administrator's email address 30 days and 10 days before renewal. If the you wish to turn off the automated renewal, you can do so any time from your online account under My Account/Billing. Free trial: [COMPANY NAME] offers a free trial version for [SPECIFY]. We do not request credit card information when signing up to the free trial. The free trial allows anyone to view the whole content of the software. The free trial, however, does not allow you to Download, Export, Print or to Cut/Copy/Paste/Save. You need to purchase and activate the software in order to be able to fully download and use the product. Failed renewal & account suspension: If your credit card on file is closed or expired, or if for any reason, a charge is rejected, you will be requested to update your Billing Information and supply a new payment to keep your account active. If a charge is rejected, your access to the [COMPANY NAME] software will be suspended until you update your account information and the payment is successful. CUSTOMER'S RESPONSIBILITIES Customer shall provide commercially reasonable information and assistance to [PROVIDER NAME] to enable [PROVIDER NAME] to deliver the SaaS Services. Customer acknowledges that [PROVIDER NAME] 's ability to deliver the SaaS Services in the manner provided in this SaaS Agreement may depend upon the accuracy and timeliness of such information and assistance. Customer shall comply with all applicable local, state, national and foreign laws in connection with its use of the SaaS Services, including those laws related to data privacy, international communications, and the transmission of technical or personal data. Customer acknowledges that [PROVIDER NAME] exercises no control over the content of the information transmitted by Customer through the SaaS Services. Customer shall not upload, post, reproduce or distribute any information, Software or other material protected by copyright, privacy rights, or any other intellectual property right without first obtaining the permission of the owner of such rights. Customer shall be solely responsible for the acts and omissions of its Administrator Users. [PROVIDER NAME] shall not be liable for any loss of data or functionality caused directly or indirectly by the Administrator Users. Subject to the terms and conditions of this SaaS Agreement, Customer shall grant to [PROVIDER NAME] a limited, non-exclusive and non-transferable license, to copy, store, configure, perform, display and transmit Customer Content solely as necessary to provide the SaaS Services to Customer Customer shall: Notify [PROVIDER NAME] immediately of any unauthorized use of any password or user id or any other known or suspected breach of security, Report to [PROVIDER NAME] immediately and use reasonable efforts to stop any unauthorized use of the SaaS Services that is known or suspected by Customer, and Not provide false identity information to gain access to or use the SaaS Services. Customer is solely responsible for collecting, in putting and updating all Customer Content stored on the Host, and for ensuring that the Customer Content does not Include anything that actually or potentially infringes or misappropriates the copyright, trade secret, trademark or other intellectual property right of any third party, or Contain anything that is obscene, defamatory, harassing, offensive or malicious. limitationS of the license The Hosted Services may only be used by the officers, employees, agents and subcontractors of the Customer; The Hosted Services may only be used by the named users identified The Hosted Services must not be used at any point in time by more than the number of concurrent users specified in section.","SaaS Agreement","https://templates.business-in-a-box.com/imgs/1000px/saas-agreement-D12704.png","https://templates.business-in-a-box.com/imgs/250px/12704.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12704.xml",{"title":166,"description":6},"saas agreement",[168,169],{"label":30,"url":96},{"label":30,"url":96},"/template/saas-agreement-D12704",false,{"seo":173,"reviewer":185,"legal_disclaimer":189,"quick_facts":190,"at_a_glance":192,"personas":196,"variants":221,"glossary":249,"clauses":283,"how_to_fill":334,"common_mistakes":375,"faqs":400,"industries":428,"comparisons":445,"diy_vs_lawyer":461,"jurisdictions":474,"related_template_ids_curated":495,"schema":507,"classification":508},{"meta_title":174,"meta_description":175,"primary_keyword":176,"secondary_keywords":177,"family":176,"is_canonical":171},"Source Code Trust Agreement - Licensed Program | Free Word Download","Free source code trust agreement template for licensed software programs.","source code trust agreement",[178,179,180,181,182,183,184],"source code escrow agreement template","software source code trust agreement","licensed program source code agreement","source code escrow release conditions","software escrow agreement template word","source code trust agreement free download","technology escrow agreement template",{"name":186,"credential":187,"reviewed_date":188},"Bruno Goulet","CEO, Business in a Box","2026-05-02",true,{"difficulty":191,"legal_review_recommended":189,"signature_required":189,"notarization_required":171},"advanced",{"what_it_is":193,"when_you_need_it":194,"whats_inside":195},"A Source Code Trust Agreement for a Licensed Program is a three-party legal contract among a software licensor (the depositor), a licensee (the beneficiary), and a neutral trustee (typically an escrow agent) that governs the deposit, custody, and conditional release of proprietary source code. This free Word download gives you a structured, attorney-ready starting point covering deposit obligations, release triggers, trustee duties, verification rights, and IP protections — ready to edit online and export as PDF.\n","Use it whenever a software licensee requires assurance that mission-critical source code will be accessible if the licensor ceases operations, fails to maintain the software, or materially breaches the license agreement. It is also required by many enterprise procurement and government contracting policies as a condition of licensing business-critical applications.\n","Identification of all three parties and their roles, deposit and update obligations for the licensor, defined release conditions and trigger events, trustee verification and custody procedures, intellectual property ownership and use restrictions upon release, confidentiality obligations, fees and indemnification, and governing law with dispute resolution provisions.\n",[197,201,205,209,213,217],{"title":198,"use_case":199,"icon_asset_id":200},"Software vendors and ISVs","Satisfying enterprise or government customer escrow requirements to close a licensing deal","persona-software-vendor",{"title":202,"use_case":203,"icon_asset_id":204},"Enterprise technology buyers","Protecting access to business-critical licensed software if the vendor becomes insolvent or ceases support","persona-enterprise-buyer",{"title":206,"use_case":207,"icon_asset_id":208},"SaaS founders","Meeting investor or acquirer due-diligence requirements for source code continuity planning","persona-startup-founder",{"title":210,"use_case":211,"icon_asset_id":212},"Government and public-sector procurement officers","Complying with mandates requiring escrow for mission-critical licensed software systems","persona-operations-director",{"title":214,"use_case":215,"icon_asset_id":216},"M&A and transaction counsel","Establishing source code custody arrangements as part of an asset purchase or licensing transaction","persona-legal-counsel",{"title":218,"use_case":219,"icon_asset_id":220},"Financial institutions and regulated entities","Meeting regulatory requirements for operational resilience and third-party technology continuity","persona-fintech",[222,226,230,234,237,241,245],{"situation":223,"recommended_template":224,"slug":225},"Single licensor and single enterprise licensee with a direct escrow relationship","Source Code Trust Agreement Licensed Program (Two-Party Escrow)","source-code-trust-agreement-licensed-program-D813",{"situation":227,"recommended_template":228,"slug":229},"Multiple licensees sharing a single escrow deposit maintained by one licensor","Multi-Licensee Software Escrow Agreement","software-escrow-agreement-D14061",{"situation":231,"recommended_template":232,"slug":233},"SaaS product where source code and infrastructure configurations both require escrow","Technology Escrow Agreement (SaaS)","technology-assignment-agreement-D765",{"situation":235,"recommended_template":236,"slug":229},"Source code deposited as security for a software development contract obligation","Software Development Agreement with Escrow Rider",{"situation":238,"recommended_template":239,"slug":240},"Open-source component mixed with proprietary code requiring segregated deposit","Mixed-Source Software Escrow Agreement","source-code-escrow-agreement-D806",{"situation":242,"recommended_template":243,"slug":244},"IP assignment combined with source code custody on acquisition close","IP Assignment Agreement with Source Code Schedule","source-code-license-agreement-D807",{"situation":246,"recommended_template":247,"slug":248},"Source code deposit required as a condition of a government or public-sector contract","Government Software License Agreement with Escrow Provisions","checklist-software-license-agreement-provisions-D782",[250,253,256,259,262,265,268,271,274,277,280],{"term":251,"definition":252},"Depositor","The software licensor who places the source code and related materials into escrow with the trustee.",{"term":254,"definition":255},"Beneficiary","The licensee who has the right to receive the source code from the trustee if a defined release condition occurs.",{"term":257,"definition":258},"Trustee / Escrow Agent","The neutral third party that holds the deposited source code and releases it only when contractually specified conditions are met.",{"term":260,"definition":261},"Deposit Materials","The full set of assets placed in escrow — including source code, build scripts, technical documentation, encryption keys, and third-party library references needed to compile and operate the software.",{"term":263,"definition":264},"Release Condition","A specific, defined event — such as licensor insolvency, failure to maintain the software, or material license breach — that triggers the trustee to release the deposit materials to the beneficiary.",{"term":266,"definition":267},"Verification","A technical audit, conducted by the trustee or an appointed expert, confirming that the deposited materials are complete, current, and sufficient to build and operate the licensed program.",{"term":269,"definition":270},"Limited License","The restricted right granted to the beneficiary to use the released source code solely to maintain or operate the licensed program for their own internal purposes — not to distribute or sublicense.",{"term":272,"definition":273},"Update Obligation","The depositor's contractual duty to deposit a new version of the source code each time a material update, patch, or new release of the licensed program is issued.",{"term":275,"definition":276},"Escrow Fees","Charges payable to the trustee for initial setup, annual custody, verification services, and release administration — typically allocated between the parties in the agreement.",{"term":278,"definition":279},"Sole Remedy Clause","A provision stating that access to the escrowed source code is the beneficiary's exclusive remedy for the triggering failure — limiting the licensor's broader contractual liability.",{"term":281,"definition":282},"Interpleader","A legal procedure allowing the trustee to deposit the source code with a court when both parties make conflicting release demands, letting the court determine who is entitled to it.",[284,289,294,299,304,309,314,319,324,329],{"name":285,"plain_english":286,"sample_language":287,"common_mistake":288},"Parties and Recitals","Identifies the depositor (licensor), beneficiary (licensee), and trustee by their full legal names, and records the background context — the underlying license agreement, the business purpose of the escrow, and the parties' intent.","This Source Code Trust Agreement ('Agreement') is entered into as of [DATE] among [DEPOSITOR LEGAL NAME], a [STATE/PROVINCE] [ENTITY TYPE] ('Depositor'); [BENEFICIARY LEGAL NAME], a [STATE/PROVINCE] [ENTITY TYPE] ('Beneficiary'); and [TRUSTEE LEGAL NAME] ('Trustee'). This Agreement is entered into in connection with the Software License Agreement dated [DATE] between Depositor and Beneficiary (the 'License Agreement').","Failing to reference the underlying license agreement by date and title. If the escrow agreement exists independently of a named license, disputes about which software version is covered become nearly impossible to resolve.",{"name":290,"plain_english":291,"sample_language":292,"common_mistake":293},"Deposit Obligation and Deposit Materials","Requires the depositor to place a complete set of deposit materials — including source code, build instructions, dependencies, and technical documentation — with the trustee within a specified number of days of signing, and defines exactly what 'complete' means.","Within [30] days of the Effective Date, Depositor shall deliver to Trustee the Deposit Materials set out in Schedule A, including: (a) all source code files for [PROGRAM NAME] version [VERSION]; (b) build scripts and compilation instructions; (c) all third-party library references and license keys required to compile the software; and (d) technical documentation sufficient to allow a competent software engineer to build and operate the Program.","Defining deposit materials as 'source code' without specifying build scripts, dependency lists, encryption keys, and documentation. An incomplete deposit renders the escrow worthless — the beneficiary may receive files that cannot be compiled.",{"name":295,"plain_english":296,"sample_language":297,"common_mistake":298},"Update and Refresh Obligations","Requires the depositor to deposit updated materials each time a new version, major patch, or material update of the licensed program is released, within a defined timeframe after each release.","Depositor shall deposit updated Deposit Materials with Trustee within [30] days of each new Release of the Program. For purposes of this clause, 'Release' means any version increment, material patch, or update that modifies the functionality, security, or performance of the Program as distributed to Beneficiary.","Setting no update timeline or leaving it entirely to the depositor's discretion. Without a specific deadline, depositors routinely allow the escrowed version to fall 12–18 months behind the production version, making the escrow practically useless on a release event.",{"name":300,"plain_english":301,"sample_language":302,"common_mistake":303},"Verification Rights","Gives the beneficiary the right to request a technical verification — and allows the trustee or an appointed expert to confirm the deposit is complete and sufficient to build and operate the program — at defined intervals or on reasonable notice.","Beneficiary may request Verification of the Deposit Materials no more than [once per calendar year] upon [30] days' written notice to Trustee and Depositor. Verification shall be conducted by Trustee or a mutually agreed technical expert and shall confirm that the Deposit Materials (a) are complete as defined in Schedule A, (b) compile successfully, and (c) produce the current Release of the Program.","Omitting a verification right entirely. Without verification, neither party knows whether the deposit is complete or current until a release event occurs — at which point discovering the deposit is incomplete is too late.",{"name":305,"plain_english":306,"sample_language":307,"common_mistake":308},"Release Conditions","Defines the specific events that entitle the beneficiary to receive the deposit materials from the trustee — typically insolvency, cessation of business, material failure to maintain the software, or material breach of the license agreement.","Trustee shall release the Deposit Materials to Beneficiary upon written notice from Beneficiary, accompanied by evidence of any of the following Release Conditions: (a) Depositor files for bankruptcy, insolvency, or liquidation; (b) Depositor ceases business operations without a successor obligated to maintain the Program; (c) Depositor fails to provide maintenance or support required under the License Agreement and such failure continues for [60] days after written notice; or (d) Depositor materially breaches the License Agreement and such breach is not cured within [30] days.","Defining release conditions so broadly that the trustee cannot objectively verify them, or so narrowly that common failure scenarios are excluded. A condition like 'Depositor fails to perform its obligations' is too vague — the trustee has no way to assess a disputed breach without becoming a fact-finder.",{"name":310,"plain_english":311,"sample_language":312,"common_mistake":313},"Trustee Duties and Limitations","Defines what the trustee is and is not obligated to do — including custody, confidentiality, and release administration — while limiting the trustee's liability to intentional misconduct and capping the trustee's exposure to fees paid.","Trustee shall: (a) hold the Deposit Materials in secure storage; (b) release materials only upon receipt of a Release Notice conforming to Section [X] or a court order; and (c) maintain the confidentiality of the Deposit Materials. Trustee shall have no obligation to verify the completeness of Deposit Materials unless a Verification is requested under Section [X]. Trustee's liability shall be limited to its own gross negligence or willful misconduct, and shall in no event exceed the fees paid to Trustee in the [12] months preceding the claim.","Appointing the beneficiary's own legal counsel, or the licensor's affiliated entity, as trustee. The trustee must be genuinely neutral — a conflicted trustee can be challenged, delaying or preventing release.",{"name":315,"plain_english":316,"sample_language":317,"common_mistake":318},"Intellectual Property Ownership and Permitted Use on Release","Confirms that title to the source code remains with the depositor at all times, and that if released, the beneficiary receives only a limited, non-transferable license to use the code to maintain or operate the licensed program for their own internal purposes.","All right, title, and interest in the Deposit Materials, including all intellectual property rights, remain exclusively with Depositor at all times. Upon Release, Beneficiary is granted a limited, non-exclusive, non-transferable, non-sublicensable license to use the Deposit Materials solely to maintain and operate the Program for Beneficiary's own internal business purposes. Beneficiary shall not distribute, sublicense, reverse engineer beyond permitted use, or use the Deposit Materials to develop competing products.","Omitting a scope-of-use restriction on the released code. Without it, the beneficiary may argue that release grants them broader rights — including the right to modify and redistribute — which was never the depositor's intent.",{"name":320,"plain_english":321,"sample_language":322,"common_mistake":323},"Confidentiality","Requires both the trustee and the beneficiary to treat the deposited source code as strictly confidential, and limits use of any released code to the scope defined in the permitted-use clause.","Trustee and Beneficiary shall treat all Deposit Materials as the confidential and proprietary information of Depositor and shall not disclose, copy, or use the Deposit Materials except as expressly permitted by this Agreement. These obligations survive termination of this Agreement for a period of [5] years, or for so long as the Deposit Materials constitute trade secrets under applicable law, whichever is longer.","Using a time-limited confidentiality clause that expires before the software's commercial life. If confidentiality expires in 3 years and the program runs in production for 10, the depositor's core trade secrets are effectively unprotected after year three.",{"name":325,"plain_english":326,"sample_language":327,"common_mistake":328},"Fees, Costs, and Indemnification","Allocates the trustee's setup, annual custody, verification, and release fees between the parties, and establishes which party indemnifies the trustee against third-party claims arising from the escrow administration.","Beneficiary shall pay Trustee's annual custody fee of $[AMOUNT] and any Verification fees. Depositor shall pay the initial deposit setup fee of $[AMOUNT]. Release administration fees shall be paid by the party requesting release. Each party shall indemnify Trustee against claims, losses, and expenses arising from that party's breach of this Agreement or any disputed release instruction issued by that party.","Failing to address who bears the cost of a disputed release — including interpleader proceedings. When licensor and licensee each claim the other has triggered a release condition, trustee legal costs can exceed the annual escrow fee many times over.",{"name":330,"plain_english":331,"sample_language":332,"common_mistake":333},"Governing Law, Dispute Resolution, and Termination","Specifies the jurisdiction whose law governs the agreement, the mechanism for resolving disputes (arbitration or litigation), and the conditions under which the agreement terminates — including upon expiry of the underlying license.","This Agreement is governed by the laws of [STATE / PROVINCE / COUNTRY]. Disputes between Depositor and Beneficiary arising under this Agreement shall be resolved by binding arbitration administered by [AAA / JAMS / ICC] in [CITY], except claims for injunctive relief or interpleader, which may be brought in any court of competent jurisdiction. This Agreement terminates upon the expiration or termination of the License Agreement, provided Trustee returns or destroys the Deposit Materials within [30] days of termination.","Not specifying what happens to the deposit materials on termination. If the agreement is silent, the trustee holds materials indefinitely — accruing fees — and neither party has a clear right to direct their destruction or return.",[335,340,345,350,355,360,365,370],{"step":336,"title":337,"description":338,"tip":339},1,"Identify and name all three parties correctly","Enter the full registered legal name and jurisdiction of incorporation for the depositor, beneficiary, and trustee. Reference the underlying software license agreement by its full title and date.","Confirm the trustee's legal entity name against their corporate registration — trustee agreements are routinely signed with a trade name that differs from the contracting entity.",{"step":341,"title":342,"description":343,"tip":344},2,"Define the deposit materials in Schedule A","List every component the beneficiary would need to build and operate the licensed program independently: source code, build scripts, dependency manifests, API keys, encryption keys, third-party library licenses, and technical documentation. Be exhaustive.","Ask your lead developer to produce a fresh build from scratch using only the listed materials before signing — if they can't, the deposit list is incomplete.",{"step":346,"title":347,"description":348,"tip":349},3,"Set the initial deposit deadline and update frequency","Enter the number of days after signing by which the first deposit must be made (typically 30 days) and the number of days after each new release by which updated materials must be deposited (typically 30 days).","Tie the update trigger to your actual release cadence — if you ship monthly, a 30-day update window means the escrow is never more than one release behind.",{"step":351,"title":352,"description":353,"tip":354},4,"Define release conditions with objective, verifiable criteria","Draft each release condition so it can be confirmed by documentary evidence alone — a court filing for insolvency, a written notice of support failure with a cure period, or a termination notice under the license. Avoid subjective conditions the trustee cannot verify independently.","Include a minimum cure period of 30–60 days for non-insolvency conditions so that inadvertent maintenance lapses do not trigger an unintended release.",{"step":356,"title":357,"description":358,"tip":359},5,"Configure verification rights and schedule","Specify how often the beneficiary may request verification (typically once per year), who bears the cost, and the scope of the verification — compilation test, completeness check, or full functional test.","Budget verification costs at $1,500–$5,000 per event when using an independent technical expert; factor this into the annual escrow budget.",{"step":361,"title":362,"description":363,"tip":364},6,"Draft the IP ownership and permitted-use clause precisely","Confirm that all IP remains with the depositor and define the exact permitted use on release: internal use only, no distribution, no sublicensing, no competing product development. Reference the duration — typically coterminous with what would have been the remaining license term.","Add a provision requiring the beneficiary to destroy or return the released materials when the release condition is resolved or the license term expires.",{"step":366,"title":367,"description":368,"tip":369},7,"Allocate fees and set indemnification scope","Confirm which party pays setup fees, annual custody fees, verification costs, and release fees. Specify that each party indemnifies the trustee against claims arising from their own instructions and that disputed-release costs are borne by the losing party.","Negotiate with your escrow agent before signing — many agents offer flat-fee annual custody packages that are substantially cheaper than per-event billing once verification requests are included.",{"step":371,"title":372,"description":373,"tip":374},8,"Execute all three counterparts before the software goes live","All three parties — depositor, beneficiary, and trustee — must sign before the licensed program enters production use. Obtain countersignatures promptly; enterprise procurement teams sometimes allow the license to go live before the escrow is signed, eliminating the beneficiary's protection from day one.","Use a fully executed copy as a condition to the first license invoice payment — this creates a practical incentive for the depositor to sign and deposit promptly.",[376,380,384,388,392,396],{"mistake":377,"why_it_matters":378,"fix":379},"Incomplete deposit materials specification","If the deposit schedule omits build scripts, encryption keys, or third-party dependency licenses, the beneficiary may receive source code files that cannot be compiled into a working program — making the entire escrow worthless at the moment it is most needed.","Have a senior developer produce a complete cold-build checklist and attach it as Schedule A. Require the depositor to certify in writing that the deposit is sufficient for a competent engineer to build and operate the program from the listed materials alone.",{"mistake":381,"why_it_matters":382,"fix":383},"No enforceable update obligation","An escrow that holds a version from two years ago provides no real protection — the beneficiary cannot maintain or patch a production system using obsolete code, and may inherit security vulnerabilities the vendor has since fixed.","Include a specific update deadline (e.g., 30 days after each new release) with a written confirmation obligation to the trustee, and make failure to update a material breach of the escrow agreement itself.",{"mistake":385,"why_it_matters":386,"fix":387},"Overly broad or unverifiable release conditions","A condition the trustee cannot objectively verify — such as 'Depositor fails to meet quality standards' — forces the trustee to either refuse release or act as an arbitrator, typically resulting in interpleader proceedings that delay access for months.","Tie each release condition to a documentary trigger: a bankruptcy filing number, a written support-failure notice with a specified cure period, or a license-termination notice. The trustee should be able to release based on documents alone.",{"mistake":389,"why_it_matters":390,"fix":391},"Appointing a non-neutral trustee","A trustee affiliated with either party — even informally through a prior business relationship — creates a conflict of interest that can be challenged in court, potentially invalidating the release mechanism entirely when the beneficiary most needs it.","Select a professional escrow agent with no financial, ownership, or advisory relationship with either the depositor or beneficiary. Specialized technology escrow agents (e.g., NCC Group, Iron Mountain) are purpose-built for this role.",{"mistake":393,"why_it_matters":394,"fix":395},"Time-limited confidentiality that expires before the software's useful life","A three-year confidentiality clause on source code that will run in production for a decade leaves the depositor's core intellectual property exposed to disclosure after the term ends — including to competitors who could reverse-engineer the released materials.","Set confidentiality to survive for the longer of five years or the duration of trade-secret protection under applicable law. Include an explicit trade-secrets carve-out that survives agreement termination indefinitely.",{"mistake":397,"why_it_matters":398,"fix":399},"No provision for what happens to deposit materials on termination","If the agreement is silent on termination, the trustee holds the materials indefinitely while accruing annual custody fees. Neither party has a clear right to direct destruction or return, creating ongoing cost and IP exposure.","Add a clause requiring the trustee to return the deposit materials to the depositor or certify their destruction within 30 days of agreement termination, and specify which party is responsible for the final custody and administration fee.",[401,404,407,410,413,416,419,422,425],{"question":402,"answer":403},"What is a source code trust agreement?","A source code trust agreement is a three-party legal contract among a software licensor (depositor), a licensee (beneficiary), and a neutral trustee that governs the deposit, custody, and conditional release of proprietary source code. The depositor places the source code with the trustee, who holds it securely and releases it to the beneficiary only if a defined trigger event occurs — such as the licensor becoming insolvent, ceasing operations, or failing to maintain the software. It is also commonly called a software escrow agreement or source code escrow agreement.\n",{"question":405,"answer":406},"When is a source code trust agreement required?","It is typically required when a licensee relies on a third-party software program for critical business operations and cannot afford a service interruption if the vendor becomes unavailable. Enterprise procurement policies, government contracting regulations, and financial services regulators in many jurisdictions mandate source code escrow for mission-critical licensed applications. It may also be required as a condition of large-scale licensing deals or SaaS platform agreements where business continuity depends on continued access to the underlying code.\n",{"question":408,"answer":409},"Who are the three parties to a source code trust agreement?","The three parties are the depositor (the software licensor who owns and deposits the source code), the beneficiary (the licensee who has the right to receive the code if a release condition occurs), and the trustee (a neutral escrow agent who holds the deposit and administers the release process). The trustee's neutrality is essential — they act as a custodian only and do not adjudicate disputes between the other two parties.\n",{"question":411,"answer":412},"What should be included in the source code deposit?","At minimum: all source code files for the licensed program, build scripts and compilation instructions, third-party library references and license keys required to compile the software, API keys and encryption credentials needed for operation, and technical documentation sufficient for a competent software engineer to build and run the program independently. A deposit that omits build scripts, encryption keys, or dependency manifests is frequently uncompilable — and therefore worthless — when a release event occurs.\n",{"question":414,"answer":415},"What events trigger the release of source code from escrow?","Common release triggers include the licensor filing for bankruptcy or insolvency, ceasing business operations without a successor, materially breaching the license agreement without curing the breach within a defined period, or failing to provide contracted maintenance and support. Release conditions should be specific and objectively verifiable by the trustee using documentary evidence alone — vague or subjective conditions lead to disputed releases and delays.\n",{"question":417,"answer":418},"Does a source code trust agreement transfer ownership of the software?","No. A source code trust agreement does not transfer ownership or intellectual property rights in the source code. Title remains with the depositor at all times. If a release condition occurs, the beneficiary receives only a limited, non-transferable license to use the released code to maintain or operate the licensed program for their own internal purposes. The beneficiary may not distribute, sublicense, or use the released code to develop competing products.\n",{"question":420,"answer":421},"How often should the source code deposit be updated?","The deposit should be updated within 30 days of each new material release, version increment, or security patch issued to the beneficiary. An outdated deposit provides diminishing protection — a beneficiary trying to maintain a production system using source code that is several versions behind faces significant security and compatibility risks. The update obligation should be a defined contractual requirement with a specific deadline, not a best-efforts commitment.\n",{"question":423,"answer":424},"What is verification and why does it matter?","Verification is a technical audit confirming that the deposited materials are complete, current, and sufficient to compile and operate the licensed program. Without verification, neither party knows whether the deposit is actually usable until a release event occurs — which is exactly the wrong time to discover it is incomplete. Most agreements allow the beneficiary to request verification once per year, with costs typically ranging from $1,500 to $5,000 depending on the complexity of the software and the scope of the test.\n",{"question":426,"answer":427},"Do I need a lawyer to prepare a source code trust agreement?","For straightforward domestic software licensing relationships, a well-drafted template reviewed by counsel is typically sufficient. Legal review is strongly recommended when the underlying license involves significant value, when the licensee is a regulated financial institution or government entity with specific escrow requirements, when international parties are involved, or when the deposit materials include open-source components with conflicting license terms. Attorney review for this document type typically costs $800–$2,500 depending on complexity.\n",[429,433,437,441],{"industry":430,"icon_asset_id":431,"specifics":432},"Financial Services and Banking","industry-fintech","Regulators including the FCA, OCC, and OSFI expect documented continuity arrangements for third-party software that supports core banking, trading, or payment operations — source code escrow is a standard component of those arrangements.",{"industry":434,"icon_asset_id":435,"specifics":436},"Healthcare and Life Sciences","industry-healthtech","EHR systems, laboratory information management systems, and medical device software often require escrow provisions to satisfy FDA software continuity guidance and HIPAA business-continuity obligations.",{"industry":438,"icon_asset_id":439,"specifics":440},"Government and Public Sector","industry-government","Government contracting regulations in the US, UK, and EU frequently mandate source code escrow for mission-critical licensed software, and procurement officers routinely require a signed escrow agreement as a condition of contract award.",{"industry":442,"icon_asset_id":443,"specifics":444},"SaaS and Technology","industry-saas","Enterprise SaaS customers — particularly those in regulated industries — increasingly require source code and infrastructure-as-code escrow as a condition of multi-year platform agreements, covering not just source files but also deployment scripts and configuration data.",[446,449,453,457],{"vs":86,"vs_template_id":447,"summary":448},"software-license-agreement-D12692","A software license agreement governs the terms under which the licensee may use the software — defining permitted use, restrictions, fees, and support obligations. A source code trust agreement is a companion document that protects the licensee's ability to continue operating the software if the licensor becomes unable to fulfill the license. The two agreements work together: the license defines the right to use; the escrow secures continuity of that right.",{"vs":450,"vs_template_id":451,"summary":452},"IP Assignment Agreement","intellectual-property-assignment-agreement-D12700","An IP assignment agreement permanently transfers ownership of intellectual property from one party to another. A source code trust agreement does not transfer ownership — the depositor retains full title at all times. The beneficiary receives only a conditional, limited-use license triggered by a failure event. If permanent transfer is the goal, an IP assignment is the correct instrument; if continuity protection is the goal, a trust agreement is appropriate.",{"vs":454,"vs_template_id":455,"summary":456},"Non-Disclosure Agreement","non-disclosure-agreement-nda-D12692","An NDA protects confidential information shared between parties from unauthorized disclosure. A source code trust agreement includes confidentiality obligations but goes significantly further — it also governs custody, deposit mechanics, release triggers, trustee duties, and IP use rights. An NDA alone provides no mechanism for accessing source code if the licensor fails; a trust agreement addresses the full continuity problem.",{"vs":458,"vs_template_id":459,"summary":460},"Software Development Agreement","software-development-agreement-D820","A software development agreement governs the creation of custom software by a developer for a client, typically resulting in IP ownership by the client on delivery. A source code trust agreement is used for pre-existing licensed programs where the licensor retains IP ownership and the licensee needs continuity protection. If the client owns the code outright under a development agreement, no escrow is needed — the IP assignment clause in the development contract already covers them.",{"use_template":462,"template_plus_review":466,"custom_drafted":470},{"best_for":463,"cost":464,"time":465},"Standard two-party domestic software licensing relationships where the licensee needs basic continuity protection","Free","1–2 hours to complete",{"best_for":467,"cost":468,"time":469},"Enterprise licensing deals, regulated-industry licensees, or agreements involving international parties or open-source components","$800–$2,500","3–7 business days",{"best_for":471,"cost":472,"time":473},"High-value platform licensing, financial services regulatory compliance, government contracting requirements, or multi-licensee escrow structures","$3,000–$10,000+","2–4 weeks",[475,480,485,490],{"code":476,"name":477,"flag_asset_id":478,"note":479},"us","United States","flag-us","US source code escrow agreements are governed primarily by contract law under the applicable state's UCC Article 2 or common law, with Delaware and New York being the most common governing-law choices for technology contracts. Federal banking regulators (OCC, FDIC) and state financial regulators expect documented software continuity arrangements for licensed systems supporting critical operations. California's trade secrets law (CUTSA) provides strong baseline protection for deposited source code, and California courts have applied it to escrow disputes.",{"code":481,"name":482,"flag_asset_id":483,"note":484},"ca","Canada","flag-ca","Canadian software escrow arrangements are governed by provincial contract law, with Ontario and British Columbia being the most common governing-law choices. OSFI Guideline B-10 on outsourcing risk management effectively requires federally regulated financial institutions to have documented continuity arrangements — including source code escrow — for material third-party technology. Quebec's Civil Code may impose additional formality requirements for agreements involving Quebec-based parties, and French-language contract copies may be required for provincially regulated employers under the Charter of the French Language.",{"code":486,"name":487,"flag_asset_id":488,"note":489},"uk","United Kingdom","flag-uk","UK source code escrow agreements are well-established in technology contracting, with the British Standards Institution and the National Computing Centre having historically published guidance on escrow best practices. The FCA's Operational Resilience Policy Statement (PS21/3) and its outsourcing rules under SYSC effectively require documented continuity arrangements for material outsourced technology, including source code access provisions. NCC Group, one of the world's largest escrow agents, is UK-headquartered and widely used for UK and European escrow arrangements. Post-Brexit, UK and EU-based agreements may need separate governing-law provisions.",{"code":491,"name":492,"flag_asset_id":493,"note":494},"eu","European Union","flag-eu","EU-based source code escrow arrangements must be drafted with GDPR in mind if the deposit materials include personal data or data processing logic — a data processing addendum to the trust agreement may be required. The EU's Digital Operational Resilience Act (DORA), which applies to financial entities and their ICT providers from January 2025, effectively mandates exit plans and source code access arrangements for critical licensed software. Member-state variations in contract law — particularly between civil-law jurisdictions (France, Germany) and common-law-influenced systems — make choice-of-law and choice-of-court clauses especially important for pan-European escrow structures.",[496,497,498,455,499,500,501,502,503,504,505,506],"software-license-agreement-D12928","custom-software-development-agreement-D787","intellectual-property-assignment-D5229","it-service-agreement-D13422","saas-agreement-D12704","master-service-agreement-D12657","data-processing-agreement-D13954","independent-contractor-agreement-D160","joint-venture-agreement-D889","asset-purchase-agreement-D928","confidentiality-agreement-D950",{"emit_how_to":189,"emit_defined_term":189},{"primary_folder":96,"secondary_folder":509,"document_type":510,"industry":511,"business_stage":512,"tags":513,"confidence":519},"intellectual-property-and-licensing","agreement","software-and-technology","all-stages",[514,515,516,517,518],"intellectual-property","source-code-escrow","software-licensing","trustee-agreement","proprietary-code",0.95,"\u003Ch2>What is a Source Code Trust Agreement for a Licensed Program?\u003C/h2>\n\u003Cp>A \u003Cstrong>Source Code Trust Agreement\u003C/strong> is a three-party legal contract among a software licensor (the depositor), a software licensee (the beneficiary), and a neutral trustee — typically a professional escrow agent — that governs the deposit, secure custody, and conditional release of proprietary source code for a licensed software program. The depositor places a complete set of deposit materials, including source code, build scripts, and technical documentation, with the trustee. The trustee holds those materials under strict confidentiality and releases them to the beneficiary only if a defined trigger event occurs — most commonly the licensor's insolvency, cessation of operations, or material failure to maintain the software. At all other times, the depositor's intellectual property rights remain fully intact. The agreement provides the licensee with a structured continuity mechanism without requiring the licensor to surrender ownership or control of its software.\u003C/p>\n\u003Ch2>Why You Need This Document\u003C/h2>\n\u003Cp>Without a source code trust agreement, an enterprise or regulated-industry licensee that depends on a third-party software program for critical operations has no enforceable path to access the underlying code if the vendor goes dark. When a vendor becomes insolvent or simply stops maintaining a mission-critical system, a licensee without an escrow arrangement faces the choice of running unsupported software — accumulating security vulnerabilities and compliance risk — or undertaking an emergency migration with no technical baseline to work from. Financial services regulators in the US, UK, Canada, and EU increasingly treat documented source code continuity arrangements as a baseline operational resilience requirement, not an optional procurement term. For software vendors, a signed escrow agreement removes one of the most common deal blockers in enterprise and government licensing by demonstrating a credible commitment to continuity. This template gives both parties a professionally structured starting point — covering every material term from deposit obligations and verification rights to IP restrictions and trustee duties — reducing the legal drafting time and cost required to get a defensible agreement in place.\u003C/p>\n",1779480713074]