ErezAgent -- End User License Agreement (EULA) **Last updated: v4.94.5 -- 2026-10-18** --- ## 1. Agreement This End User License Agreement ("Agreement") is between you or the entity you represent ("Customer," "you") and Erez Rozenbaum, the developer and licensor of ErezAgent ("Licensor," "we," "us"). By downloading, installing, or using ErezAgent, you agree to this Agreement and to `COMMERCIAL_LICENSE.md` (which sets the license tier and usage scope you purchased). If you do not agree, do not install or use the software. ## 2. What ErezAgent Is ErezAgent is self-hosted software. You (or your infrastructure provider) install and run it entirely within your own environment -- your own server, VM, or cloud account, using your own Docker/Helm deployment. See Section 5 for what this means for your data. ## 3. License Grant Subject to this Agreement and `COMMERCIAL_LICENSE.md`, Licensor grants you a non-exclusive, non-transferable license to install and use ErezAgent for the number of users, projects, servers, or environments you purchased. You may not resell, redistribute, sublicense, or provide ErezAgent as a hosted service to third parties unless you hold a separate MSP or OEM agreement. ## 4. Ownership ErezAgent -- including its source code, architecture, prompts, agent definitions, and documentation -- is licensed, not sold. Licensor retains all right, title, and interest in the software. This Agreement grants you a license to use it; it does not transfer any ownership. ## 5. Your Data and Your Responsibility **You control your data because you control the deployment.** ErezAgent does not transmit your operational data (missions, agents, financial records, customer data, or anything else stored in your database) to Licensor, and there is no analytics collection built into the product. A deployment can optionally be connected to a provider you choose (described below). Concretely, as of this version: - License validation is a fully offline Ed25519 signature check performed inside your own deployment. It does not call out to a license server. - If your vendor bills by usage, ErezAgent can export a usage report for a month you choose (Revenue Center -> Billing -> Usage). The file holds aggregate figures only -- counts and totals such as AI usage, actions and capacity, with no customer names or other personal data -- plus a checksum and your attestation that it reflects your deployment. You decide whether and when to send it; the software never sends it automatically. - The outbound network calls the backend makes on its own initiative are an anonymous request to GitHub's public releases API to check for a newer version, a daily request to a public exchange-rate service for currency rates, and status checks to the AI providers you configure, using your own keys. No business data goes to Licensor, and no account data, hostnames or identifiers are sent with the first two. - If your provider enrols your installation, your owner can connect it in Settings -> Provider / Managed Service. The connection is off by default, needs the owner's consent, and can be paused or disconnected at any time. While connected, the installation reports version, health, a count-level security summary, AI and voice provider status, connector counts, readiness and licence/subscription state to that provider -- never prompts, business data, documents, e-mail, credentials or keys. The page shows the exact last report, and nothing the provider sends back changes your installation. - If you contact Licensor to purchase or renew a license, you may voluntarily share your machine fingerprint and contact email -- that is a normal sales inquiry, not something the software does automatically. - If you choose to enable billing (Settings -> Plan & Billing) and connect a payment processor (Stripe, Rapyd, PayPal, or Pelecard), payment data flows directly between your deployment and the processor *you* configure -- the same pattern as any other connector (Gmail, Slack, and so on). Licensor never receives or stores your payment details; that processor's own privacy policy and terms govern that relationship. The same is true if you enable a venture's own Venture Commerce subscription selling (v4.77.0) -- that venture's own connected payment processor handles its own customers' payments directly, never through Licensor. Usage statements, invoice drafts and billing documents you generate (including PDF or DOCX files and any email you choose to send) are produced and stored in your own deployment and contain the customer names or references you entered; webhooks and exports go only to the endpoints you configure. - If you configure a separate Admin/Management API key for Anthropic, OpenAI, or xAI to see real provider spend/balance (v4.77.0, opt-in, never your ordinary inference key), that lookup calls the provider's own API directly using your key. Licensor never sees it. - If you connect the WhatsApp channel or use Document Collection (v4.78.0, opt-in), inbound messages/media are fetched directly from Meta's API using your own connected account, and any document your customer submits is stored inside your own deployment's own local storage. Licensor never receives, stores, or has visibility into that content. - If you use a Business Record's e-signature field (v4.82.0, opt-in) to request a signature, the software facilitates that request -- sending your document to DocuSign under your own connected DocuSign account and recording the status DocuSign reports back. The signature itself, the signer's consent, and the legal effect of signing are governed entirely by DocuSign's own terms of service, not by this Agreement. The software does not independently verify a signer's identity beyond what DocuSign's own envelope completion provides. - If you turn on AI-analysis consent (Settings -> Data & Privacy, owner-only, off by default; v4.88.0) and use Build My Business or the document-reading features, the text or page images of the documents you upload are sent from your own deployment to the AI provider you have configured, with identifiers masked by default, or kept to local models only if you choose that mode. Features you start yourself on your own documents (for example requirements intake, contract analysis and knowledge generation) do not depend on that consent; they always mask identifiers first, and use local models only if you chose that mode. Names and free-text addresses are not masked. Those providers' own terms govern that use; Licensor receives none of it. Uploaded source files are kept in your own deployment and removed after the retention period you set (90 days by default). You are responsible for having the right to submit those documents for analysis. - When agents, chat, or voice features run, prompts and the data they contain are sent from your own deployment directly to the AI providers you enable (Anthropic, OpenAI, Google, DeepSeek, Mistral, and xAI) and to any voice providers you configure. Those providers' own terms and privacy policies govern that use; Licensor receives none of it. Because of this, **you are solely responsible for**: - Securing the host, network, and operating system ErezAgent runs on. - Patching the OS, Docker, and any infrastructure you operate. - Managing credentials, encryption keys, and access control for your deployment (including rotating the secrets generated at install time). - Backups, retention, and disaster recovery for your own database. - Complying with data protection law (GDPR, CCPA, HIPAA, or others) that applies to the data *you* choose to store in ErezAgent. Licensor is not a data processor or data controller for your operational data because that data never reaches Licensor's infrastructure. - Any tax you are legally required to collect from your own customers, whether billed through the platform's own Plan & Billing or through a venture's own Venture Commerce subscriptions (v4.77.0). ErezAgent's tax calculation is a tool that applies rates *you* configure, or an external service *you* choose to connect -- it is never a substitute for your own tax registration, advice, or compliance obligations in the jurisdictions you sell into. The usage statements and invoice drafts ErezAgent produces are not tax invoices; issue legally valid invoices from your own accounting system. See `PRIVACY_POLICY.md` for the narrower question of what happens if you directly contact Licensor (e.g., a support request or license purchase). ## 6. Support and Updates Support scope depends on your license tier (see `COMMERCIAL_LICENSE.md`). Licensor is not obligated to provide updates, patches, or new versions, though they are made available from time to time at Licensor's discretion. ## 7. Disclaimer of Warranty **THE SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.** Licensor does not warrant that the software will be uninterrupted, error-free, or fully secure. ErezAgent includes AI agents that can take real actions (subject to the approval and risk-tiering system built into the product) -- you are responsible for reviewing and approving actions before they execute, and for configuring autonomy tiers appropriately for your risk tolerance. A business model, configuration, or document extraction that ErezAgent proposes from your material is a suggestion: you are responsible for reviewing it before you approve it, and nothing is built until you do. ## 8. Limitation of Liability **TO THE MAXIMUM EXTENT PERMITTED BY LAW, LICENSOR'S TOTAL LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT OR THE SOFTWARE WILL NOT EXCEED THE AMOUNT YOU PAID FOR YOUR LICENSE IN THE 12 MONTHS PRECEDING THE CLAIM.** Licensor is not liable for indirect, incidental, consequential, special, or punitive damages, including lost profits or lost data, even if advised of the possibility of such damages. **HIPAA note:** ErezAgent is not designed, certified, or offered as a HIPAA Business Associate service. If you are a covered entity or business associate under HIPAA and intend to process protected health information (PHI) using ErezAgent, you do so at your own risk and are responsible for determining whether your deployment meets your regulatory obligations; Licensor makes no representation that it does. Contact Licensor before using ErezAgent with PHI so this can be discussed directly. ## 9. Term and Termination This Agreement remains in effect for as long as you use ErezAgent under a valid license. Licensor may terminate your license if you materially breach this Agreement or `COMMERCIAL_LICENSE.md` and do not cure the breach within 30 days of notice. On termination, you must stop using the software and delete your installation; your own data remains yours and is unaffected (it was never on Licensor's infrastructure to begin with). ## 10. Changes to This Agreement Licensor may update this Agreement for future versions. Material changes will be noted in `CHANGELOG.md`. Continued use after an update constitutes acceptance of the revised terms. ## 11. Governing Law This Agreement is governed by the laws of the jurisdiction in which Licensor resides, without regard to conflict-of-law principles, unless a signed Enterprise, MSP, or OEM agreement specifies otherwise. ## 12. Contact For licensing questions: erez.rozenbaum@gmail.com