Pair Your Devices
Pair supported Core clients with a QR code. Device-first pairing keeps key material on the clients; browser and account features require sign-in.
- Device-first QR pairing
- Supported Core clients
- Verified native releases only
Pair your iPhone with any computer. Send clips, file bytes, and screenshots with end-to-end encryption, so the relay cannot decrypt their contents.
Privacy is the foundation, not a feature
Pair supported Core clients with a QR code. Device-first pairing keeps key material on the clients; browser and account features require sign-in.
Clips, files, screenshots, links — send them between your devices with one action. Free up to 25MB, 100MB on Pro.
Clipboard bodies and transferred file bytes are encrypted before they leave your device. The server relays ciphertext and cannot decrypt these payloads.
Verified native clients can live in the system tray or menu bar and expose intentional shortcuts for common actions.
Your recent clips and transfers are stored locally with encryption. Search and re-send anything from your history.
Encrypted transfer between supported clients
Open the authenticated browser companion now. Install a native client only when the download page lists a verified artifact, then connect supported clients.
Copy text, send files, or create secure links from screenshots. Quilon keeps flows fast and encrypted.
Open Quilon on your other device to paste instantly, or send a secure link to anyone when needed.
Only the browser companion is marked available here. Native clients remain in validation until signed release artifacts are published.
Free for personal use. Pro when you need more.
Everything you need to move stuff between your devices, encrypted by default.
For power users who live across many devices.
$2.92/mo billed annually
Free forever for 2 devices. No credit card required.
Encryption-first architecture, zero-knowledge design
AES-256-CBC encryption on all clipboard data. Only your devices can decrypt.
Clipboard bodies and Private Share bytes are client-encrypted and relay-only. Account and routing metadata is still processed by the service.
We don't hold the keys needed to decrypt protected content payloads. Operational metadata remains visible to the service.