Updated: 26.09.2026

Partner Agreement: a testing office in the beta program

The Hebrew version prevails in case of discrepancy.

This agreement is made between the business trading as VITRUVIUS ECOSYSTEM (“the Business”) and an architecture office joining the partner program (“the Office”). The name “partner program” is only the name of a program. The agreement does not create a partnership, agency or joint venture between the parties, and neither party is liable for the other’s debts. The Office receives early access to versions of the plugin and to materials not yet published, and gives back feedback, examples and testing. No law dictates the wording of this agreement, so next to each clause we name the law it relies on.

The parties: The Business: ____________ (the full name of the business owner), business no. ____________, trading as VITRUVIUS ECOSYSTEM, contact@vitruviusecosystem.com · The Office: ____________ (office name), company/business no. ____________, contact person ____________.

Good faith

Both parties will act in an accepted manner and in good faith, both in negotiating the agreement and in performing it, as sections 12(a) and 39 of the Contracts Law (General Part), 5733-1973 require. The Office will report fairly on what works and what does not. The Business will tell the Office in advance about any change in a version that may affect active projects in the Office, and will give it time to prepare.

Confidentiality

Everything the Office receives under the program is confidential information of the Business: unpublished versions, documentation, future prices, product plans and working methods. The Office will protect it, will not disclose it to others, and will use it only to test the plugin and give feedback. This agreement is one of the reasonable measures the Business takes to keep that information confidential, and that is a condition for protecting it as a “trade secret” under section 5 of the Commercial Torts Law, 5759-1999. Using a trade secret in breach of a contractual obligation is misappropriation of a trade secret under section 6(b)(2) of that law. The duty of confidentiality lasts three years after the agreement ends. It does not apply to information the Office knew before, or that became public without a breach on its part.

No reverse engineering

The Office will not disassemble, decompile or analyse the plugin’s code, the licensing mechanism or the communication with the server, and will not ask anyone else to do so. This clause is needed because the law alone does not forbid it: section 6(c) of the Commercial Torts Law provides that discovering a trade secret by reverse engineering is not, in itself, an improper means. So the prohibition is set here in the contract, and whoever breaches it breaches the agreement.

No AI training

The Office may not feed the plugin’s code, the unpublished documentation or the outputs of beta versions into artificial intelligence tools, neither to train a model nor to produce a competing tool from it. This includes tools that use the information fed into them for training. The Business, too, undertakes that it will not train models on the Office’s files, drawings or data. The plugin is a literary work under section 1 of the Copyright Law, 5768-2007, and feeding it in this way is use of a trade secret in breach of a contractual obligation (section 6(b)(2) of the Commercial Torts Law).

The rights stay with the Business

All rights in the plugin, its versions and its documentation are owned by the Business, including improvements built following the Office’s feedback. Under section 33(1) of the Copyright Law, whoever wrote the feedback is its first owner. So the Office hereby assigns to the Business, without consideration and irrevocably, the rights in the feedback, suggestions and reports it gives about the plugin. Such an assignment requires a written document (section 37(c) of that law), and this agreement is that document. The Office’s files, templates, families and drawings remain its own (section 33(1)), and the Business will not use them beyond the testing the Office asked for.

Personal information and deletion

The Office will try not to send files containing identifying personal information, and will remove it from the files before sending where possible. If files containing personal information are nevertheless sent to the Business, for example client names or project addresses, the Business will use them only for the testing requested. It will keep them confidential (section 16 of the Privacy Protection Law, 5741-1981) and secure them (section 17(a)). The Business will delete them within 30 days of the end of the testing, or at once when the Office asks, and will confirm the deletion by e-mail if the Office asks. The 30 days are an undertaking of the Business, not a requirement of the law.

Liability

Beta versions are provided as they are, for testing purposes only, and not for work on real submissions without a backup. The Business is not liable for indirect or consequential damage. Its total liability under this agreement is limited to the amount the Office paid the Business in the year before the event, if it paid. The limit does not apply to damage caused wilfully or by gross negligence.

Term and termination

The agreement is in force for one year from signing and renews by itself for a further year, and either party may end it with 30 days’ notice. When the agreement ends, the Office will delete the unpublished versions, and the Business will delete the Office’s files as set out in the section “Personal information and deletion”. Israeli law applies to this agreement.

Signatures: The Business ____________ · The Office ____________ · Date ____________