PRIVACY BY ARCHITECTURE
Your private life should stay yours.
Privacy starts with how a service is built. Here’s how SafeCall is designed to connect people while keeping conversation contents on their devices.
Conversations stay on your devices.
SafeCall’s infrastructure coordinates accounts, device discovery, and connection setup. Private messages, files, audio, and video are not stored on SafeCall servers. Message history lives in encrypted local storage on user devices.
Direct first. Encrypted relay when needed.
Devices prefer direct WebRTC connections. When network restrictions prevent that, TURN can relay encrypted packets without reading the encrypted content or storing conversations. Direct connections can expose participants’ network addresses to each other. Peer-to-peer communication is not a promise of anonymity.
Offline messages wait with the sender.
Undelivered messages remain in the sender’s encrypted local outbox. Push services carry wake-up or rendezvous signals rather than private message text or files. Delivery requires both devices to be reachable at overlapping times. Operating-system scheduling and network conditions can delay or prevent background delivery.
Your device keeps your private keys.
SafeCall uses established cryptographic primitives and platform security facilities. The server distributes public device keys; private keys remain on user devices. Independent security review and platform acceptance testing remain release requirements. We do not claim an independent security audit or certification.
Less metadata, with clear limits.
Accounts, device registration, contact matching, connection signaling, and push routing require some metadata. The architecture calls for minimizing its collection and retention. Push providers can still observe installation tokens, timing, and routing information. Contact discovery is not described as zero knowledge.
This website keeps things simple.
This landing page includes no analytics SDKs, advertising trackers, embedded third-party media, or marketing forms. Its fonts and brand assets are served from the same origin. As with any website, the hosting infrastructure receives network requests; hosting log retention must be defined by the operator.
This is a product architecture overview, not a complete legal privacy notice. SafeCall is in development. Operator details, processing purposes and legal bases, retention periods, rights, and contact information need to be included in the approved privacy notice before public production launch. See release status and terms.