Skip to content
OpenE2EE

Policies and agreements.

Versioned terms govern the OpenE2EE Signal Protocol Relay. The privacy and service policies explain the managed data boundary. Each accepted agreement remains at a permanent URL.

  • OpenE2EE Signal Protocol Relay Service Terms

    The project-scoped Relay service, capacity, billing, data, suspension, and beta-support contract.

  • Privacy Notice

    What we collect, why, which providers process it, how long it is kept, and how to make a request. The SDK runs in your environment; this covers the parts that do not.

  • Data Processing Agreement

    The Article 28 terms for personal data we process on a Relay customer’s instructions, with the standard contractual clauses for transfers. It binds when the Relay terms are accepted; there is nothing to sign and nothing to request.

  • Acceptable Use Policy

    Service safety and enforcement, plus the current subprocessor list, retention statement, and beta limits.

  • Pinned Relay terms relay-2026-09-22

    The permanent copy the console records when an organization accepts this service agreement before its first Relay project. The superseded versions, relay-2026-09-10 and relay-2026-08-26, keep their own addresses, and so do the policies the terms incorporate: the retention statement 2026-09-27 and the beta limits 2026-09-10.

  • Pinned notice 2026-09-27

    The immutable copy of the notice in force. Each version from 2026-08-26 onward keeps its own address, so what a notice said while it applied stays readable after it is replaced.

  • Pinned agreement 2026-09-27

    The permanent copy of the version in force, for a procurement file that needs an address rather than an attachment. The superseded version, 2026-09-10, keeps its own address.

  • Security and legal questions

    Report a vulnerability to security@open-e2ee.dev. Send licensing and contract questions to licensing@open-e2ee.dev.

LicensingPricingSecurity model