CliperYour content.
Only you can unlock it.
Cliper is designed to keep clipboard content and attachments unreadable to the server.
Separate account login from vault unlocking
Email verification confirms your identity. The first native device generates and securely stores keys. New devices gain access through an existing device or a recovery file. The website keeps content keys only in memory during an approved session.
Encrypt before uploading
Clipboard content, attachments and device names are encrypted on the client, then uploaded to the sync service and private R2 storage. The server retains necessary account, device ID, size, sync time and billing metadata.
Clear security boundaries
End-to-end encryption cannot protect a compromised device, malicious client update, an unlocked device used by another person, or a leaked recovery key. This implementation has not undergone an independent security audit. Development builds are not an absolute-security vault.
You keep the recovery key
Without plaintext content keys, the server cannot restore your data using only an email code. Keep your recovery key in a trusted separate location. Removing a device blocks future server access but cannot erase content already downloaded.
Account and payment data
The account service handles email, sessions and minimal activity records. Stripe handles payments; card details never enter Cliper's database. This development notice needs formal operator details, privacy policy and terms before launch.