This is an outline.
Buyers and counsel need a clear picture before they open a redline. This page gives that picture. It does not replace negotiation, and it does not add promises that are missing from the signed documents. If you need the agreement itself, ask — we would rather send the document than pretend this summary is it.
What is granted.
A customer receives a non-exclusive licence to run the RavenFlo software on infrastructure that customer controls, for the number of people and the term set out in the order. The licence is not a sale of the software. Title to the software remains with RavenFlo (and its licensors).
Typical deployments include a primary site, a disaster-recovery site and branch or edge nodes, as described in the order and the sizing materials. Use beyond the licensed quantities needs an amendment.
What the customer keeps.
- The customer owns its content: messages, files, voice notes, call recordings it chooses to keep, and the organisational data it loads into the system.
- In the on-premise edition, that content stays on infrastructure the customer operates. RavenFlo does not receive message content in order to provide the licence.
- Encryption keys for everyday conversations are created on devices. A customer-held compliance key, where enabled, lives in hardware the customer controls.
What the customer does.
The customer is responsible for:
- Operating the servers, directories, directory and devices that RavenFlo runs on.
- Deciding who may join, what may be shared, how long records are kept, and who may approve archive access.
- Complying with the laws that apply to its own processing of personal data and regulated information.
- Keeping credentials, HSM material and administrative access under its own control.
What RavenFlo does.
RavenFlo provides the software, documentation, and the support and updates described in the order. We do not operate the customer’s messenger as a multi-tenant cloud in the on-premise edition. We do not hold a master key that lets us read customer conversations.
Restrictions.
Unless the signed agreement or applicable law says otherwise, the customer may not:
- Resell, rent or host the software as a service for unrelated third parties.
- Reverse engineer the software except where the law allows that activity anyway.
- Remove proprietary notices that travel with the software.
- Use the software to build a competing product by copying its design or code.
Support and updates.
Support hours, severity definitions, update channels and any on-site assistance are set in the order or a support schedule. Signed releases and, on request, a software bill of materials are part of how we ship updates; details live in the trust and security materials.
Warranty and disclaimer.
Any warranty about the software is only the warranty written in the signed agreement. These website pages do not add a promise that the software is unhackable, uninterrupted, or sufficient for a particular law or certification. The customer’s counsel decides whether the controls meet the customer’s obligations. Marketing phrases such as “designed for 30,000 people” describe intended scale, not a performance guarantee for every network.
Term and ending.
The licence runs for the term in the order. On ending, the customer’s rights to run the software end as the agreement provides. The customer’s content remains the customer’s. RavenFlo does not need a copy of that content back, because in the on-premise edition we did not host it.
How to get the agreement.
Ask during a demo, or write to sales@ravenflo.io. Partners who deploy for customers should use partners@ravenflo.io. Related reading: privacy notice, trust centre, whitepaper.
Last updated 11 November 2026. If a signed customer agreement says something different about the product, that agreement prevails for the product. These pages govern the website, and summarise the product only where they say so.