About AegisMeetings
We don't ask for your trust.
We ask you to verify us.
Why AegisMeetings Exists
There is no such thing as absolute security on the internet. AegisMeetings responds not with empty promises, but by grounding the system in Zero Trust Architecture and mathematical cryptography — making protection come from verifiable technical design, not from trust in any person or organization.
The protection this architecture provides is grounded in the current code implementation — a premise any web-based encryption service must honestly face. That is why open, well-established standards are used and the whitepaper is published for everyone: at any time, anyone can independently verify whether the protection remains valid, without taking anyone's word for it.
If law enforcement or judicial authorities present lawful credentials demanding cooperation, only what the law requires can be provided: basic account information and IP records. For what you actually care about — meeting audio and transcripts — the architecture makes it technically impossible to produce any plaintext.
Even the highest-privileged administrator cannot decrypt your transcripts without modifying the code — that is the technical guarantee the cryptographic architecture provides, independent of any individual's intentions or promises. If you don't trust promises, the whitepaper is there to verify.
Cryptographic Design, Independently Verifiable
Cannot Produce Plaintext Even for Courts
The architecture does not hold your vault private key — the sole decryption key for your sealed transcripts and summaries. Even if compelled to cooperate with an investigation, only ciphertext can be handed over.
Open Standards, Independently Verifiable
Encryption is based on open standards including RSA-4096 and XChaCha20-Poly1305, reviewable by any cryptographer.
Server Breach Cannot Reach Your Transcripts
Even if all servers were simultaneously compromised, attackers cannot obtain your vault private key — the keys for sealed transcripts and summaries never exist on any server.
Public Document
System Architecture & Security Whitepaper
Complete encryption boundaries, data flows, and safeguards — published for anyone to read and challenge. The design rests on open cryptographic standards; details are in the whitepaper body.
Read the Full WhitepaperContact Us
Customer Service
Accounts, billing, refunds, transcription or vault issues, and security disclosures — write to us; we reply within 3 business days.
[email protected]