Guide
Questions and answers
The practical limits behind the short product description.
Identity and devices
How do friends find me without a phone number?
Share an Auris ID or invitation. Invite-only discovery requires the appropriate capability. A directory ID is still a handle the service can observe. Identity guide.
What happens if I lose my phone?
The released app has no account-recovery or linked-device mechanism. Device-bound identity keys and local history may be lost. A replacement identity needs to be added and verified again. Reinstallation on the same phone is not a reliable Keychain-erasure method.
Can I use one identity on my phone and Mac?
Linked devices are not a released capability. Native Mac development uses a separate identity; it is not synchronization of the phone's account.
Security and evidence
Is Auris quantum-proof?
No. ML-KEM and ML-DSA address specified cryptographic threats. Auris's custom composition, endpoint storage, identity binding and metadata need their own evidence. The ledger distinguishes mechanisms, conditional arguments and open proofs.
Has Auris been independently audited?
No independent implementation audit is recorded. Internal reviews and reproducible research are useful evidence with narrower scope; they do not substitute for one.
What can the service disclose?
Its protocol does not give it normal plaintext conversation content or endpoint private keys. It does hold operational data and may observe directory, routing, connection and push metadata. Encryption is not a promise that there is no information to disclose. See the privacy policy and observer ledger.
Does Lockdown turn off all notifications and receipts?
No. It omits the anonymous-queue wake token and selects generic local message notices. Directory APNs/VoIP registration and receipt/typing settings are separate. Read the actual preset matrix.
Can Auris protect a phone infected with spyware?
It cannot guarantee confidentiality while an attacker controls an endpoint that sees plaintext or keys. The history vault's stored-data protection and the app's screen lock have narrower, documented boundaries.
Service and roadmap
Is the code open?
The application source remains closed. Public explanations and research artifacts improve inspectability, but they do not let readers audit the entire app. Open source, reproducible source builds and independent audit remain roadmap work.
Are there groups or Android support?
Neither is a released capability covered here. They require separate architecture, implementation and validation work.
Can relays make Auris unblockable?
No. They provide additional paths with their own operator and network assumptions. This review did not establish availability in every country or network.
How do I report a problem?
Use the support or beta-feedback channel supplied with your invitation or installed build. Share only the diagnostic information needed for the report. A public security-contact address is not invented here.
Released beta · Reviewed · Review scope and versions