Zero Cloud Accounts
No phone numbers, SMS verification codes, emails, or central directory servers. Your identity is a cryptographic P-256 keypair generated strictly inside your phone's hardware security chip.
Establish private communication channels exclusively through an in-person Mutual Physical Handshake. No central servers, no phone numbers, no cloud metadata. Ratcheted AES-256-GCM message keys over signed relay envelopes.
Unlike commercial chat apps that store graph telemetry, contact lists, and message queues on central servers, Entangl enforces pure peer-to-peer security.
No phone numbers, SMS verification codes, emails, or central directory servers. Your identity is a cryptographic P-256 keypair generated strictly inside your phone's hardware security chip.
Contacts physically scan each other's visual public keys in person. Neither user can send a message until both devices verify a matching 60-digit Safety Number, eradicating remote spam and MITM attacks.
Chain ratchet deriving a unique AES-256-GCM key per message with wire sequence binding. Chains never reset per send and self-heal after peer restart or rescan.
Signed envelopes fan out across redundant relays under blinded per-device inbox topics with fixed-size padding. Local encrypted direct transfer covers device migration.
All database tables, message logs, and contact records are encrypted at rest with SQLCipher (AES-256). Master keys are wrapped by the hardware-backed Android Keystore with StrongBox support.
Window enforcement with FLAG_SECURE blocks screenshots and screen recording. Cryptographic keys reside in off-heap native memory buffers (NativeKeyBuffer) and are zeroed immediately after use.
Per-contact delete, clear-history, and block/unblock with muted enforcement both ways, live presence from fresh verified traffic, and self-destruct timers with bilaterally enforced vaporization.
In the Entangl Android application, each node selects a codename and a profile color with hue/saturation sliders or direct hex entry. The profile is covered by the handshake signature to prevent identity spoofing.
Click any preset to dynamically re-theme this website and preview the node signature:
Active Profile Hex: #00F0FF
Connecting with a peer takes under 15 seconds, requires zero Internet connectivity, and guarantees immunity against remote surveillance.
Alice initiates the handshake. Her device generates a rolling nonce, exports her public P-256 identity key, and displays a dynamic QR code.
Bob scans Alice's QR code. Bob's phone validates Alice's signature, signs both nonces with his private key, and renders a response QR code.
Alice scans Bob's QR code. Both devices compute a deterministic 60-digit Safety Number (12 blocks of 5 digits) to verify channel integrity.
Both devices initialize ratchet session keys after mutual scans. Messages route as signed envelopes over redundant relays with per-message keys.
Every packet, payload, and cryptographic primitive is transparent and auditable. Inspect real wire payloads below:
{
"protocol_version": 1,
"action": "INITIATE | CONFIRM",
"uid": "node-a1b2c3...",
"identity_pub": "P-256 ECDSA (Keystore)",
"nonce": "32-byte rolling, 60s TTL, single-use",
"signature": "ECDSA-SHA256 over canonical bytes"
}
Free, open-source, and verifiable. Available via Google Play Store, direct APK download, and source code build.
Standard installation with automatic security updates and verified signatures through Google Play Protect.
Standalone installation with no Google Play Services dependency. Verifiable against published SHA-256 checksums.
Clone the repository, audit the cryptographic primitives, and build using Kotlin 2.0 and Gradle.
1288AEDE9F651FFC42912693423F671780EB9E730B3A15658741F4EB0692CBC8