Legal

Terms of Service

The plain rules for using Raven: what you agree to, what we are responsible for, and what stays entirely in your control.

LAST UPDATED · 2026-09-08 CONTACT · INFO@RAVEN-MESSENGER.COM

TERMS OF SERVICE · LAST UPDATED 2026-09-08

1. Acceptance of Terms

By using Raven, the terminal-native communication software ("the Service"), you agree to these Terms of Service. If you do not agree, please do not use the Service. The Service is currently in beta and features may change without notice.

2. Eligibility

You must be at least 13 years old to use Raven. If you are under 18, you must have parental or guardian consent.

3. Your Identity and Keys

Raven has no accounts, sign-up, or login. Your identity is a cryptographic keypair generated locally on the host machine. Its protection depends on the host, operating system, and selected storage implementation. You are solely responsible for the security of your host machine and these keys. We never receive, hold, or have any ability to recover your keys, and we are not liable for any loss resulting from loss of your host machine or keys.

4. Acceptable Use

You agree not to use Raven to:

  • Send spam, harassment, or threatening messages
  • Distribute illegal content
  • Impersonate other users or entities
  • Interfere maliciously with Raven nodes or exploit third-party systems without authorization
  • Interfere with the operation of the mesh network or relay systems
  • Use the Service for any purpose that violates applicable laws

Inspection, copying, modification, and redistribution of Raven source remain governed by the applicable AGPL license. These terms do not replace the permissions granted by that license.

5. Optional Transports and Relays

Raven hosts communicate through supported, configured carriers. A host may participate as a relay for sealed RVN1 envelopes when its operator enables that functionality. Bluetooth is optional, and actual carrier support depends on the implementation and host. Relaying consumes network and host resources.

6. Content

You retain ownership of all content you create and share through Raven. We do not claim any rights to your messages. The normal Raven message path requires authenticated session setup and seals messages for the peers you choose. Optional RDAP carriers and model providers have separate confidentiality and data-handling requirements, described on the privacy page.

7. Beta Service

Raven is currently in beta. The Service may contain bugs, be incomplete, or undergo significant changes. We provide the Service "as is" without warranty of any kind. We are not liable for any data loss or service interruptions during the beta period.

8. Termination

Because Raven has no accounts and stores no data on our servers, we cannot suspend or terminate an account. You may stop using Raven at any time: stop the Raven process, remove the software, and delete its local state and key material from the host, including any backups you control. Removing the executable alone may leave local state behind. Deleting your own data does not remove copies retained by peers.

9. Limitation of Liability

To the maximum extent permitted by law, Raven and its developers shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including loss of data, arising from your use of the Service.

10. Changes to Terms

We may update these terms from time to time. Continued use of the Service after changes constitutes acceptance of the new terms. Significant changes will be published on this website with an updated revision date.

11. Contact

For questions about these terms, contact us at info@raven-messenger.com.