FAQ
Direct answers to the questions we get asked most.
Can RVNT read my messages?
No. Messages are encrypted on your device using keys that only you and your contact possess. RVNT servers relay encrypted ciphertext. We do not have the keys. We cannot read your messages. We cannot be compelled to read your messages. The encryption is not optional and cannot be disabled.
What happens if RVNT shuts down?
Your messages are stored locally on your device, encrypted with SQLCipher. They do not depend on RVNT servers to exist. The RVNT protocol supports peer-to-peer and mesh connectivity. If our servers go offline, devices that can reach each other directly (via local network, Bluetooth, or WiFi Direct) can continue to communicate. The source code is open and anyone can run a relay node.
Is RVNT legal?
RVNT is a communications application that uses encryption. Encryption is legal in most jurisdictions. Some countries restrict or ban encryption (e.g., certain provisions in China, Russia, and others). It is your responsibility to comply with local law. We do not provide legal advice.
Why does RVNT not require a phone number?
A phone number is a government-issued identifier tied to your real identity. Requiring one for a privacy tool defeats much of the purpose. RVNT uses cryptographic key pairs for identity. Your identity is a public key, not a phone number. You can verify contacts through QR code scanning or safety number comparison.
What if I lose my device?
If you have not created an encrypted backup, your messages are lost. This is by design. There is no "forgot password" or "account recovery" because there is no account and no server-side data to recover. Your cryptographic identity lives on your device. Back up your recovery phrase. We cannot help you if you lose it.
Can law enforcement access my messages?
Not through us. RVNT servers do not store message plaintext, encryption keys, sender identity, or IP addresses. A subpoena served to RVNT yields encrypted blobs and public prekey material. Law enforcement could attempt to access your physical device, which is why RVNT includes SQLCipher encryption, panic mode, and travel mode. We publish a warrant canary.
Why Tor instead of a VPN?
A VPN shifts trust from your ISP to the VPN provider. The VPN provider sees all your traffic. Tor distributes trust across three independent relays, none of which sees both the source and destination. No single Tor relay can identify both who you are and what you are doing. VPNs are a single point of trust failure. Tor is not.
How is RVNT funded?
RVNT is funded through optional donations and the RVNT payment protocol (a small fee on optional in-app transfers). We do not sell user data because we do not have user data. We do not serve ads. We do not have investors who demand growth metrics. If this model proves unsustainable, we will say so publicly.
Has the code been audited?
The code is open source and available for anyone to audit. We are pursuing formal third-party security audits and will publish the results in full, including findings we disagree with. Until then, the code speaks for itself: 522+ tests, 91.6% coverage, 500M+ fuzz iterations with zero crashes. We run a bug bounty program for independent researchers.