Our privacy commitment.
RavenFlo provides a private, enterprise messenger that is installed inside the infrastructure of the organisation that has licensed it. Our core principle is simple: your organisation owns the data, not RavenFlo.
We have engineered the on-premise edition so that messages, calls, files and audit logs stay in the customer’s environment. RavenFlo staff cannot read the contents of those conversations. Encryption keys for everyday messages are created and kept on the devices in the conversation, not in a RavenFlo cloud.
Two relationships.
There are two distinct relationships covered by this notice:
- This website. When you request a demo, write to us, or ask for product updates, RavenFlo collects the fields you submit. For that website activity, RavenFlo is the organisation deciding why the data is used.
- The RavenFlo product. When people at a customer use RavenFlo inside their workplace, the customer is the organisation deciding how that data is used. RavenFlo supplies the software. We do not host the message content in the on-premise edition, and we do not hold the keys that read it.
If a signed customer agreement says something different about product data, that agreement prevails for the product. This page is the notice for website visitors, and a plain-language description of the product’s privacy design.
Who controls product data.
When you use RavenFlo at work, the organisation that employs you (or authorised you to use the platform) is the data controller for the communications on that deployment. RavenFlo acts only as the technology provider.
- User accounts are created and managed by the customer’s administrators.
- Messages, calls, files and related metadata are stored on infrastructure the customer operates.
- RavenFlo cannot read, export or share the contents of those conversations.
Questions about how your employer monitors, retains or opens records on RavenFlo should go to your organisation’s IT, HR or compliance team. RavenFlo cannot answer them on their behalf.
What the website collects.
If you request a demo, early access, a reply, or product updates, we collect the fields on that form. Those typically include:
- Full name and work email (personal email domains are refused on the form).
- Organisation, role, and the answers you choose to give about size or deployment preference.
- Any free-text message you choose to write.
- The consent you give by ticking the box, which starts unticked.
The host that serves this website also keeps ordinary technical logs, such as the time of a request and a network address, for a short period so the site can be operated and protected. We do not invent a visitor profile from those logs for advertising.
Why we use website data.
We use the information you submit on this website to:
- Answer you and arrange the demo or conversation you asked for.
- Send an occasional product note, only if you confirmed that you want updates.
- Keep a record of the request for a limited time, so we can resume the conversation if you write again.
We do not sell personal data. We do not use website submissions to build advertising profiles for someone else. We do not buy lists to cold-email people who never wrote to us.
How long we keep it.
An unanswered or unconverted demo, contact or early-access request is kept for 24 months and then deleted, unless you ask us to delete it sooner. If you become a customer, the signed contract governs what is kept after that. Product-update subscriptions are kept until you unsubscribe or ask us to delete them.
Cookies and analytics.
This marketing website does not set advertising or tracking cookies. We do not run an advertising network on these pages. If we add a cookieless, self-hosted analytics tool later, this notice will name it and explain what it counts. Until then, treat the statement as: no non-essential cookies.
The RavenFlo product clients may use local storage or cookies strictly to keep a person signed in, remember preferences, and protect the session. Those are part of the customer’s deployment, not this website, and they are not used for third-party advertising.
How the product protects data.
The on-premise edition is built around privacy by design, not only by contract:
- Messages, files, voice notes and calls are encrypted on the sender’s device and readable only on the recipients’ devices.
- Each device creates its own keys. A lost device can be revoked. Keys for everyday conversations are not kept by RavenFlo so that we can read the chat.
- A separate compliance copy can be sealed to a key the customer holds in its own hardware security module. Opening it needs two authorised people of the customer, and the opening is logged.
- Servers handle sealed envelopes, delivery and policy. They do not need to read the message content in order to deliver it.
More detail is in the public security whitepaper and on the security page. The trust centre lists only certifications that exist, and says so when a test is still outstanding.
Data location.
In the on-premise edition, the customer chooses where RavenFlo runs: a data centre, a disaster-recovery site, branch edge nodes, or a private cloud the customer controls. Message content and the keys that open everyday conversations stay in that environment. RavenFlo does not require a RavenFlo-operated public cloud in order for the product to keep running.
Website form submissions are processed so that we can answer you. They are not mixed into a customer’s messenger database.
Third parties.
On this website we may use a hosting provider and a mail or CRM system to receive and answer forms. Those providers process only what is needed to deliver that service to us, under their own terms. We do not hand website leads to an advertising network.
Inside a customer’s RavenFlo deployment, optional services such as SMS one-time passcodes or directory sync may be configured by the customer. Those providers are engaged for the customer’s environment, under the customer’s control, and are not a backdoor for RavenFlo to read conversations.
Your rights.
For website data we hold about you — for example a demo request — you can ask for a copy, a correction, or deletion by writing to privacy@ravenflo.io. If you are in India, you may also raise a grievance with us at that address. We will answer.
For data inside your organisation’s RavenFlo deployment — access, correction, deletion or objection should be directed to your organisation’s designated privacy or IT contact. They are the controller. We cannot open their archive for you.
Children.
This website and the RavenFlo product are for organisations. They are not directed at children.
Updates.
We may update this notice when the website, the product, or the law changes. The effective date at the top of the page will change when we do. The current version is always the one published here.
Contact.
For privacy questions about this website, or about RavenFlo as the technology provider, write to privacy@ravenflo.io. For questions about your own messages inside a customer deployment, contact your organisation.
If you want to see the design behind these statements, read the whitepaper or request a demo and walk the architecture with an engineer.
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.