Hey,
this is the creator of convro. First of all – thanks for even being here.
convro was born out of a very simple frustration: I was tired of messengers that say “privacy” on the landing page while shipping tracking SDKs, analytics everywhere and logging every tiny thing you do in the app. I wanted a tool that treats your conversations as something obviously worth protecting – not as raw material for dashboards.
That’s why:
• the client and backend are developed as open-source,
• the protocol has a name and a face: Convro6Protocol,
• identity is based on a virtual +99 number, not the SIM card number your provider owns,
• DMs and groups run on modern crypto primitives (X25519 / Ed25519, HKDF-SHA256, ChaCha20-Poly1305, PFS / PCS),
• channels are designed to be scalable while still keeping metadata to a minimum.
convro is not “yet another messenger with stickers”. The goal is to make it:
• understandable for regular users,
• but at the same time fully auditable for people who like reading specs and code.
If you’re “just” a user – you have every right to expect that your messages won’t become someone’s analytics dataset someday.
If you’re a dev / researcher – treat convro as an invitation: you can run your own node, review the protocol, question the crypto decisions, open issues, send PRs and help shape the threat model with us.
convro will change. We’ll break things, fix them, refactor and rewrite parts from scratch. One thing is non-negotiable: the priority is security and honesty towards the user – not engagement, retention or ad inventory.
If you want to be closer to the project:
• join our Telegram group,
• check out the GitHub repo, read the code, leave a star or open an issue,
• drop an email if you have feedback, technical criticism, ideas or want to help.
Thanks for testing convro at such an early stage.
This project only makes sense because there are people on the other side who genuinely care about their digital privacy.
– creator of convro