Security that can be explained and verified
We describe only properties that actually work and avoid promises of absolute anonymity or universal deletion.
Claims do not replace controls
A corporate product needs predictable actions: who has access, which devices are active, and what happens after revocation or purge.
Independent layers
Organizations are isolated by server authorization and database policies. Credentials are stored as non-reversible hashes, connections use TLS, and session revocation reaches realtime connections.
Honest security boundaries
Remote wipe clears managed storage in an official client after command delivery, but cannot erase screenshots, manual exports, or third-party copies. E2EE is not claimed before its separate security gate.
Frequently asked questions
Does Tallkers already use E2EE?
No. The architecture targets MLS/OpenMLS, but the claim will wait for a native prototype and review.
Can a lost computer be revoked?
Yes. The server revokes the device and sessions; the official client performs local erasure after receiving the command.