OpenE2EE Relay Service Terms
These Terms govern a project's Development and production OpenE2EE Relay environments.
Relay activation records the version you accept. The permanent copy of this version is at /legal/relay-terms/2026-08-26.
1. Agreement and project scope
These Terms are a binding agreement between OpenE2EE LLC, a Minnesota limited liability company (“OpenE2EE,” “we,” “us,” or “our”), and the person or entity that creates or owns an OpenE2EE Relay project (“Customer,” “you,” or “your”). You accept these Terms when you activate a Relay project or accept a paid Relay order. If you act for an organization, you represent that you can bind it.
Each Relay project has one qualified plan ID, a catalog version, an owner, and separate development or production credentials. A signed order form controls over conflicting language in these Terms.
2. Service and customer responsibilities
OpenE2EE Relay provides encrypted device mailboxes, delivery and pull, group fan-out, private encrypted attachment storage, push wakes, exact usage controls, and lifecycle operations for the OpenE2EE Signal Protocol SDK. The current documentation defines the supported interfaces and limits.
Customer owns account authentication, authorization, lawful end-user notices, device trust decisions, plaintext processing, private keys, backup policy, client security, application behavior, and compliance for its use case. Customer must use stable request identifiers and supported SDK behavior where the service contract requires them.
3. Plans, limits, and billing
The Relay pricing page defines the current plan prices, included Relay monthly active accounts, delivery units, attachment operations, exact live encrypted storage, and overage rates. The meter definitions there form part of these Terms. An exact retry with the same stable operation identifier is not charged twice.
Attachment operations are a hard cap. Free production has hard caps and no automatic charge. Paid plans may reserve approved overage spend up to the project spend limit. The service can reject new work or enter a defined drain state when a hard cap, spend limit, payment failure, policy change, or security control requires it. A drain does not make Stripe or another billing provider the authority for message delivery.
Paid plans are billed monthly in advance, plus usage overage and applicable taxes. Subscriptions renew monthly until canceled. Cancellation takes effect at the end of the current paid period unless law requires another result. Fees are non-refundable except as required by law or a signed order form. Enterprise pricing and commitments require a signed order form.
4. Project commercial SDK license
While a Relay project remains active and compliant, OpenE2EE grants Customer a limited, non-exclusive, non-transferable, non-sublicensable commercial license to use @open-e2ee/signal-protocol-sdk in one proprietary application that connects to that project. The license includes Free production. It grants no self-hosting right, no right for another project, and no right to redistribute the SDK as a standalone product or service.
The project license ends when the project is deleted or 30 days after its production plan ends, whichever occurs first. During that transition, Customer may export configuration and move to an AGPL-compliant deployment or a separate self-hosted commercial license. The transition does not extend Relay capacity or data retention. The AGPL remains available under its own terms.
5. Customer data and deletion
Customer retains its rights in encrypted content and project data. Customer instructs OpenE2EE to process that data only to provide, secure, meter, support, and improve Relay, comply with law, and enforce these Terms. The Privacy Notice, Subprocessor List, and Relay Retention Statement describe the processing boundary.
Account deletion removes the account-owned inbound mailbox and objects. It does not recall messages from another recipient’s mailbox or delete shared group ciphertext only because one member leaves. Project deletion enters a fenced drain and purge process. Narrow security, billing, reconciliation, and legal records may survive payload deletion for the periods stated in the retention policy.
6. Security and acceptable use
Customer must protect credentials, use least privilege, install security updates, and promptly report suspected compromise. Customer must follow the Acceptable Use Policy. OpenE2EE may rate-limit, suspend, or isolate activity that threatens the service, another customer, or the public.
7. Beta availability and support
Relay is a pre-release beta until OpenE2EE announces a generally available service. The Development environment and Free production plan include no service-level agreement. Paid beta plans include the support shown in the applicable order, but no uptime credit or response guarantee unless a signed order form says otherwise. The Beta Service Limits describe current operating constraints.
8. Disclaimers and liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, RELAY IS PROVIDED “AS IS” AND “AS AVAILABLE.” OPENE2EE DISCLAIMS IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND ANY WARRANTY THAT THE SERVICE IS ERROR-FREE, UNINTERRUPTED, OR SUITABLE FOR A PARTICULAR THREAT MODEL.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR LOST PROFITS, REVENUE, DATA, GOODWILL, OR BUSINESS INTERRUPTION. EACH PARTY’S TOTAL AGGREGATE LIABILITY UNDER THESE TERMS WILL NOT EXCEED THE FEES PAID OR PAYABLE FOR THE AFFECTED RELAY PROJECT DURING THE 12 MONTHS BEFORE THE EVENT. THESE LIMITS DO NOT APPLY TO PAYMENT OBLIGATIONS, FRAUD, WILLFUL MISCONDUCT, OR LIABILITY THAT CANNOT LAWFULLY BE LIMITED.
9. Suspension and termination
Either party may terminate for a material breach that remains uncured 30 days after written notice. OpenE2EE may suspend sooner for nonpayment, unlawful activity, sanctions risk, abuse, credential compromise, or a material threat. Where safe and lawful, we will give notice and a reasonable opportunity to cure before termination.
After termination, Customer must stop using Relay credentials. Data follows the documented drain, retention, and deletion process. Accrued fees and provisions that by their nature should survive remain in effect.
10. Changes and general terms
We may publish a new version for future activations and renewals. An accepted paid order remains under its recorded version until Customer accepts a later version or law requires a change. We may change Free or beta capacity with reasonable notice when practicable, including to protect service integrity.
Minnesota law governs. The state and federal courts in Hennepin County, Minnesota have exclusive jurisdiction. The parties are independent contractors. If one provision is unenforceable, the remainder stays effective. Neither party is liable for delay caused by events beyond reasonable control.
These Terms, the recorded project order, the linked policies, and any signed order form are the entire agreement about Relay. Send legal notices to licensing@open-e2ee.dev. We may send service notices to the project owner’s console email.