Specifications, encryption details, and libraries for anyone building on VeilComm.
Everything you need to integrate verify or extend the protocol.
Each message is sealed with a fresh elliptic-curve key exchange and AES-256-GCM encryption before it leaves the device.
VeilComm currently ships as a native Android library. An iOS release is not available yet it's planned for a future update.
There's no public server API yet. Today contacts and encryption keys are exchanged directly between devices using QR codes or encrypted file sharing with no hosted backend involved. Once sealed messages and files can be safely shared through apps like WhatsApp, Telegram, Signal, Discord, Messenger, email, cloud storage, or virtually any other platform without exposing their contents.
A plain language breakdown of how keys are generated and exchanged. Each message uses its own one-time key pair so no two messages share the same encryption key.
The numbers behind the chips on the home page.
