Skip to main content
Security & privacy

Built so we couldn't read your clipboard if we tried

Your clipboard sees passwords, addresses and private messages all day. So Clypy encrypts every clip on the device that copied it, and our servers only ever carry what you see on the right.

On your devicereadable here

Encrypted in your browser as you type, with AES-256-GCM and a fresh IV, the cipher Clypy uses. The key was made on this page and never leaves it. Nothing is sent anywhere.

The full detail, from device keys to pairing, is in how Clypy sync works.

Where your clip can be read

On your devices. Nowhere else.

  1. Readable

    The device you copied on

    Encrypted here, with keys held in the OS secure store.

  2. Not readable

    Your network

    Ciphertext only. At home, devices talk directly.

  3. Not readable

    Clypy relay

    Passes sealed frames along. It holds no keys.

  4. Not readable

    Clypy servers

    No stored clipboard history to read or hand over.

  5. Readable

    Your other devices

    Decrypted only there, with keys shared at pairing.

Secrets

Detected secrets stay concealed

Clypy conceals newly detected secrets on sight and leaves them out of search, backups and agent results. They stay concealed on every device they sync to, and revealing one asks you to authenticate first. Mark one This device only and it never leaves the device that copied it.

Never captured

Copies from password managers, anything your system marks as concealed, and apps you exclude.

Concealed on every device

Card numbers, IDs, API and auth tokens, sign-in links, credentials, licence keys.

Secret · auth tokenExpires in 59:12
••••••••••••
Concealed on every deviceReveal
On-device AI

Smart search that never phones home

Search by meaning, text recognition in images and working out what each clip is all run on your hardware. No clip is sent to a model, ours or anyone else's, and all of it works offline.

  • Search by meaning
    Local embeddings, searched locally
  • Text in images
    Read on your device as images arrive
  • Clip types
    Links, code, secrets, recognised locally
What we do keep

No product holds nothing. Here's our list.

Privacy claims are only worth something if the exceptions are written down too.

Relay routing metadata

While a frame is in flight: a device's public key, an opaque group tag, the IP address, and the frame's size and timing.

Never: keys, clip contents, previews, titles or file names.

Relay logs

Structured events for keeping the service running: timestamps, device and session ids, error codes.

Never: payloads.

Purchase records

Pro purchases create receipt and licence records with the payment provider, tied to your purchase email.

Never: a password or a public profile. The purchase identity can be deleted separately.

Plain-language commitments

No fine print, no asterisks

  • We cannot read your clips because our servers only ever carry ciphertext.
  • No Clypy profile or password. Purchases still create receipt and license records with the payment provider.
  • On the same network, clips sync device-to-device and skip our servers entirely.
  • Files you send between your devices travel only over your local network, encrypted for that pair of devices, and never reach our servers.
  • AI runs on your device; clip contents are never sent for processing.
  • Configured password-manager sources are ignored; newly detected secrets are concealed on every device they sync to, or kept on one device if you mark them local-only.
  • Export or delete everything whenever you want. Deletion is permanent.