Your conversations.
Between you.

SafeCall is built around peer-to-peer communication. Our infrastructure helps your devices find and connect to each other. Messages, files, audio, and video are not stored on SafeCall servers. Your conversation history lives on your devices.

Your message waits in the encrypted outbox on your device. A notification can help the other person reconnect without including your message in the push payload. Delivery needs both devices to be reachable at overlapping times. Background delivery depends on the operating system and is not guaranteed.

SafeCall prefers a direct WebRTC connection. If a firewall or network prevents that, an encrypted TURN relay can carry the packets. The relay cannot read the encrypted content and does not store your conversations. Direct connections can expose your network address to the other participant.

SafeCall imposes no file size limit. Practical limits depend on the available storage, capabilities of both devices, and network conditions. Transfers support pause, resume, and integrity checks; both devices need to be reachable to exchange the file.

The service handles information needed for accounts, device public keys, contact matching, connection setup, and push routing. This means peer-to-peer does not mean zero metadata. SafeCall’s architecture calls for minimizing metadata collection and retention. Private keys and conversation contents stay on user devices.

You can visit the development preview using the Try SafeCall button. SafeCall is still in development, with Android as the first validation target. Production authentication and further security and platform validation remain release requirements. Group conversations and multi-device history synchronization are future work.

An independent security review is a release requirement. We are not claiming an independent audit or certification. The architecture uses established cryptographic primitives, authenticated device connections, and encrypted local storage.