Transparency
How Konvella is run and secured
Last updated 2026-11-06
This is written by the people who run Konvella, about Konvella. It is not an independent audit, and it does not pretend to be one — where that matters, it says so below. Every claim here comes with the way you can check it for yourself, and there is a plain list of what we do not have. A page that only lists strengths is marketing; this one lists the gaps too.
Who runs it
Konvella is built and operated by an independent developer, not a large company. That is the honest shape of it: a small, independently run service rather than a funded startup with a legal department. One upside is that there is a real person answering support@konvella.com; one downside is that there is no 24/7 operations team, and you should weigh that for what you use Konvella for. The company details that apply to you, and your rights over your data, are in the privacy policy.
Encryption, exactly
"Encrypted" is a word that gets stretched. Here is precisely what each kind of encryption does and does not cover, and the honest limits.
Verified
Calls and video are end-to-end encrypted.
Voice, video and screen share flow directly between the people on the call (WebRTC, DTLS-SRTP). The server only helps the two devices find each other; it never carries the audio or video and could not listen in if it wanted to. Each call shows a
safety number both sides can read aloud — if they match, nobody is in the middle, not even us.
Check it: in any call, open the call menu and compare the safety number. It is derived from the two devices' keys, which the server never sees.
Important limit
Messages and files are encrypted at rest, but not end-to-end.
Everything you send is stored encrypted with AES-256-GCM, so a stolen copy of the database is unreadable noise. But the key lives on the server, which means
Konvella's operator can technically read messages and files — to run moderation, answer a report, or comply with a valid legal order. This is the single most important thing to understand, and we would rather say it plainly than hide behind the word "encrypted". If you need a messenger whose operator
cannot read your messages at all, Konvella is not that, and we will not pretend otherwise. Use end-to-end calls for anything that must stay only between you and the other person.
This is a design choice, not a secret: the homepage and privacy policy say the same thing.
Verified
Passwords are never stored.
Only an Argon2id hash is kept — a one-way fingerprint. Even we cannot turn it back into your password. Reset codes and recovery codes are stored the same one-way way.
If anyone ever emails you your actual password, it is not us, and it is a scam.
Verified
Everything travels over HTTPS.
Every connection between your device and Konvella is encrypted in transit (TLS), and browsers are told to refuse plain HTTP to us for a year (HSTS). Sign-in uses short-lived tokens, two-factor authentication is available, and you can see and end every signed-in session.
What we hold, and for how long
The full table — every field, why we keep it, and when it is deleted — is in the privacy policy, and it is specific on purpose. In short: your account and messages until you delete them, security and anti-abuse records for a bounded time, and as little else as the service can work with. We do not sell data, and we do not run advertising or tracking profiles.
Who else is involved
Konvella runs on a small number of named providers, each doing one job. We do not share your data for their own purposes; they process it to deliver the service.
- Render — runs the server.
- MongoDB Atlas — stores the database (encrypted fields as described above).
- Cloudflare — DNS, protection in front of the site, and forwarding support email.
- Resend — sends account emails (password resets, security notices), from the EU.
- Paddle — handles payments, if you subscribe. Konvella never sees your full card number.
- Google and Apple — deliver push notifications to phones.
- Giphy — the GIF picker, when you open it.
What we do not have
This is the part most services leave out. Being straight about it is the point of this page.
We don't have this
No independent third-party security audit.
Konvella's security has been reviewed carefully, but that review is our own, not an outside firm's. We have not paid for, and cannot show you, an independent penetration test or cryptography audit. Do not take "we checked it ourselves" as the same thing as an external audit — it is not, and we are not going to badge this page with one we did not have.
If that changes, this line changes, and the auditor and report will be named here.
We don't have this
The server and app source code is not public.
So you cannot independently read the code behind these claims today. What
is public is the desktop app's released builds and their signatures, so a desktop update can be checked to be genuinely from us and unmodified.
Treat the encryption claims above as our statement, verifiable in the ways noted, not as something you can yet read line by line.
We don't have this
No end-to-end encryption for messages, and no "we can't read it" guarantee.
Repeated here because it belongs in the list of limits, not only in the encryption section.
Reporting a security problem
If you find a weakness, please tell us before anyone else and give us a fair window to fix it — we will not pursue good-faith research done under this policy. The machine-readable version is at /.well-known/security.txt; the address is support@konvella.com.
When this page is wrong
If anything here stops matching how Konvella actually works, it is a mistake to fix, not spin to keep. Point it out to support@konvella.com and we will correct it and update the date above.