# Open Connector Contributor License Agreement **Version: 1.0 — 2026-10-01** This is the published agreement for the signing process described in [the contribution guide](CONTRIBUTING.md#cla-and-dco). Publication does not sign an agreement for anyone; each Contributor must explicitly accept it, and Lorevia LLC must confirm receipt and coverage as described below. ## 1. Parties and scope This Agreement is between **Lorevia LLC**, a limited liability company organized under the laws of **Wyoming, United States** ("Project Owner"), and the individual or company identified in the signing record ("Contributor"). The agreement contact is **legal@lorevia.io**, which is also the private email signing channel. The Contributor and Project Owner may instead agree on another recorded signing process meeting section 6. "Project" means Open Connector. "Contribution" means code, documentation or other material the Contributor deliberately provides for inclusion in the Project. A submission expressly identified as excluded from this Agreement is not a Contribution under it; maintainers must resolve its separate permissions before including it. The Contributor confirms that covered submissions are intentional and that it has the authority described in section 4. Coverage is limited to the submissions and future scope expressly identified in the signing record and confirmed by both parties. Future Contributions are covered only when that future scope is expressly selected. Work submitted before the effective date is covered only when its PRs or commits are expressly listed in the record. Company coverage is limited to its identified work and authorized contributors; affiliates are not automatically included. ## 2. Ownership and copyright permission The Contributor retains copyright and may use or license its Contributions elsewhere. This Agreement does not assign ownership to the Project Owner. For rights it owns or is authorized to license, the Contributor gives the Project Owner worldwide, perpetual, non-exclusive permission, without license fees or royalties, to use, copy, modify, create derivative works, display, perform, distribute and sublicense the Contributions. This grant is irrevocable except where mandatory applicable law provides otherwise. No non-waivable author termination right, including any applicable right under 17 U.S.C. section 203, is waived by this Agreement. The permission expressly covers AGPL-3.0-only, the Open Connector Commercial License, and other open-source or proprietary terms, including paid Cloud services and licensed self-host products. These uses require no further Contributor approval or royalties. Recipients receive permissions through the applicable distribution license. This Agreement gives them no independent, unrestricted copyright license to EE components and does not withdraw permissions for copies already licensed to them. ## 3. Patent permission For patent claims it can license that are necessarily practiced by a Contribution itself or its combination with the Project as submitted, the Contributor grants the Project Owner a non-exclusive patent license to make, have made, use, distribute, import, offer for sale and sell that work, with authority to sublicense these permissions to authorized recipients without patent license fees. Later combinations do not expand the covered claims. This worldwide grant lasts for the relevant patents' duration and is otherwise irrevocable, subject to mandatory law and this condition: if a beneficiary starts patent litigation, including a counterclaim seeking affirmative infringement relief, alleging that a covered Contribution or that combination infringes a patent, its patent permissions under this Agreement end when it files the claim. This condition does not terminate the copyright grant. ## 4. Authority and provenance The Contributor confirms it has authority to grant these permissions. It must identify third-party material, its source and applicable restrictions when submitting it. A PR does not convert someone else's work into the submitter's own Contribution or remove that work's existing license conditions. If an employer or client owns relevant rights, an individual must supply written permission for these grants, a relevant rights waiver, or coverage under a company signing record. Permission merely to submit code is insufficient if it does not also authorize these grants. A company must sign through a representative authorized to bind it and identify the covered contributors or submissions. Maintainers must verify that scope. Neither a company nor an individual signature grants rights the signing party does not control. The Contributor must notify the agreement contact of any material error in these statements or change affecting its authority for future Contributions. ## 5. Other rights and obligations No permission to use the Contributor's names, trademarks or logos is granted here. In exchange for the contribution permissions, the Project Owner undertakes to make covered submissions eligible for review under its ordinary contribution process, retain the accepted agreement and confirmation, and provide the Contributor a copy. It will use private signing information only to administer and enforce contribution permissions and meet legal obligations, and will not publish signed records or private supporting documents. Contributing GitHub handles, agreement version/digest and the permission-check result may appear publicly; legal names, contact emails, signatures and employer documents remain private. Necessary service providers may process them under appropriate confidentiality safeguards, subject to required legal disclosures. The Project Owner need not accept a Contribution, publish it, pay for it or provide credit beyond distribution-license requirements. The Contributor need not provide maintenance or support. Except for the authority and provenance statements and applicable legal requirements, Contributions are supplied without warranties, including merchantability, fitness for a purpose or non-infringement. Non-excludable legal rights and liabilities remain. ## 6. Signing and changes Acceptance requires an explicit signature or recorded electronic assent to the identified final text, followed by Project Owner confirmation of receipt and coverage. The effective date is the confirmation date. Both parties must be able to retain the accepted text and signing record. Before an electronic signing transaction, both parties must agree to that process. The Contributor must be able to review and save or print the complete final text, correct its signing details, and explicitly accept that text using a signature associated with its verified identity. The Project Owner's authorized representative or designated signing process must record confirmation. An account name or automated bot result alone does not establish a person's authority to bind an employer. Submitting a PR, contributing code or adding a Developer Certificate of Origin (DCO) sign-off does not by itself accept this Agreement. DCO certifies contribution provenance under the applicable license; CLA acceptance must be recorded separately. The signing record must bind Contributor identity and account to the agreement version and content digest, assent, timestamp and coverage. Company records also identify the representative's authority and covered contributors. Use the private signing channel for signed documents, private identity details and employer permissions; do not place these in public PRs or repository files. Changes to this Agreement require fresh acceptance of the changed text. Stopping future contributions does not revoke grants for work already covered. The Project Owner may transfer this Agreement and its rights only to a successor acquiring the relevant Project or business and assuming its obligations in writing. It must give the Contributor notice through the recorded contact. This does not expand Contribution coverage; sublicensing under sections 2 and 3 remains separately allowed. ## 7. Governing law and disputes Wyoming law governs this Agreement, without its conflict-of-laws rules, together with applicable United States federal law. This choice does not override non-waivable rights or mandatory applicable law. To the extent law permits, disputes must be brought before a court in Wyoming with lawful subject-matter jurisdiction: the United States District Court for the District of Wyoming where federal jurisdiction exists, or a competent Wyoming state court otherwise. The parties consent to personal jurisdiction and venue there, except where mandatory law requires another forum. This provision does not confer subject-matter jurisdiction on a court that lacks it. ## 8. Agreement scope and severability This Agreement governs the contribution permissions described here and does not replace separate employment, contractor, copyright-assignment or customer agreements. If a provision cannot lawfully be enforced, it applies only to the extent permitted; the remaining provisions continue where lawful. Failure to enforce a provision on one occasion is not a waiver of future enforcement. ## How to sign Follow the [private signing steps](CONTRIBUTING.md#cla-and-dco). Maintainers follow the Project Owner's private verification and record process.