Pairing
ECDH pairing, key derivation, and the short verification number make tampering visible.
Security Core
Pairing, signaling, and backend boundaries live in a separate public core. That makes the part responsible for security and privacy open to inspection.
Quick answers
Five plain answers about the product behind the open security core.
What is public?
The app interface stays separate. The logic that has to earn your trust is open.
ECDH pairing, key derivation, and the short verification number make tampering visible.
Clear contracts show which encrypted data moves between the app, Firestore, and a session.
Rules, data models, and automatic cleanup show what the server is allowed to do – and what it is not.
A secure connection
The four-character code is only a meeting point. The real security is created afterwards on both devices.
For developers
The core keeps the security-critical packages, backend contracts, and architecture documentation in one place.
Open the repository →For parents
The guides turn the same decisions into clear questions about pairing, privacy, and permissions.