Do not use sensitive files for testing. There is no independent security certification or claim that the app has no flaws.
Approval and identity
QR invitations expire and can be used once. Windows explicitly approves phone requests. Protected routes require an approved session, and revocation rejects subsequent requests. Chat safety numbers use the full participant keys; changed peer keys pause communication and require review.
Transport is a separate requirement
The native desktop UI is restricted to loopback. Advanced phone-testing mode uses local HTTPS, which requires the phone to trust the app’s local certificate authority. QR approval alone does not authenticate an HTTP-delivered page. Reserving a port is not a replacement for trusted transport.
DNS/domain provisioning and native mobile development remain paused. A certificate-install-free phone-browser trust solution is not available in this preview.
Originals, checked before publication
Resumable transfers use per-chunk and complete-file SHA-256 checks. Native receiving syncs checkpoints, rechecks retained data after restart, verifies persisted destination bytes and refuses to overwrite existing filenames. A digest detects a mismatch relative to expected data; it does not authenticate a sender by itself.
Chat and shared files are different
Chat messages and attachments are encrypted by participating clients. Ordinary shared files use session and transport controls; they are not described as end-to-end encrypted chat. Chat attachments have a 256 MiB cap and broader mobile lifecycle acceptance is unfinished.
Windows protected storage
Native chat identity and receiver checkpoint metadata use Windows-backed protected storage. Shared files and staging bytes are not encrypted by a new application-level file encryption layer. Protect your Windows account and disk, and discard retained copies when no longer needed.
Remaining release gates
- Practical authenticated phone-browser onboarding.
- A legitimate publisher signature and verified distribution.
- Clean-machine Windows and physical phone acceptance.
- Remaining performance, accessibility and recovery acceptance.