How Benefic Protects Your Privacy
How Benefic keeps your data private — direct WebRTC peer-to-peer connections, DTLS-SRTP end-to-end encryption, and no port forwarding.
1 min read
Benefic is built from the ground up with privacy as a core principle. Here’s exactly how your data stays protected.
Direct Peer-to-Peer Connections
Benefic uses WebRTC to create direct, encrypted connections between your devices:
- No port forwarding — connections are established via STUN/TURN signaling
- No central server — after the initial handshake, traffic flows device-to-device
- No DNS, firewall rules, or reverse proxies to configure
In certain edge cases (e.g. iOS background audio), data may be relayed through Benefic’s infrastructure to maintain the connection. Even then, all data remains end-to-end encrypted — Benefic cannot read your content regardless of the connection path.
End-to-End Encryption
Every WebRTC session is secured with DTLS-SRTP, which provides:
- Authentication between your devices
- Integrity protection for all transmitted data
- End-to-end encryption for all content types — text, audio, video, images, 3D
- Benefic never holds your encryption keys
Comparison: Benefic vs. Cloud-Based Tools
| Feature | Benefic | Cloud note apps (Notion, etc.) |
|---|---|---|
| Data location | Your devices | Third-party servers |
| Sync model | Direct P2P (WebRTC) | Cloud relay |
| Internet exposure | No open ports | Vendor-controlled |
| Privacy | E2E encrypted — we can’t read your data | Vendor has full access |
| Encryption | End-to-end DTLS-SRTP | At rest (vendor-held keys) |
| Setup | Simple sign-in | Account + trust vendor |