Security at a glance
Security overview
A quick map of how Auris protects your conversations, the choices you control, and the evidence behind the design.
Protections at a glance
| What you want to protect | How Auris approaches it | Explore |
|---|---|---|
| Your identity | A locally generated ID and keys. No required phone number, email or address-book upload. Invitation-only discovery is available. | Identity choices |
| Conversation content | Endpoint encryption with hybrid classical and post-quantum key material, followed by evolving message keys. | Cryptographic construction |
| Routing information | Sealed sends omit the sender field. Per-contact queues omit an owner ID. IP addresses, timing and other routing paths remain relevant. | Observer ledger |
| Voice and video | The default path authenticates the transport fingerprint through the message session and adds endpoint frame encryption. A separate, visible classical fallback changes that extra layer. | Call protocol |
| History on your device | A separate history key can require biometrics, an Auris passphrase, or both. Device integrity and copies held elsewhere have separate boundaries. | History protection |
How the design is examined
- Implementation
- The reference documents the recorded beta and labeled development changes. Tests and executable models exercise selected protocol, recovery and storage behavior.
- Research
- The public R2 paper and frozen R3 symbolic model study a separate v5 candidate. Their results have explicit assumptions and do not prove the released pv4 app.
- Independent review
- Auris has not completed an independent product security audit. Its source is currently closed. The evidence record distinguishes source review, tests, proofs and independent assessment.
About this overview
This is product security documentation. It helps you find the right explanation without repeating the full protocol reference. Scientific papers, theorem statements and reproducibility artifacts live in Research & papers.
The baseline is the recorded build-147 beta, with build-148 development identified where relevant. See the version record for details.
Explore a security question
Reviewed · Review scope and versions