Encrypted before upload
Messages and files are encrypted on your device before they leave it. The server can deliver the ciphertext, but cannot decrypt your content.
Send files and text
between your own devices — privately.
SendSelf is a private, end-to-end encrypted space for your phone, laptop, and tablet. No account required: your content is encrypted on your device before upload, and the server never receives it in readable form.
Personal
Your content stays yours
Messages and files are encrypted on your devices before they leave them. The server can deliver ciphertext, but cannot decrypt it.
No account required
No email or server password. Optionally protect this device with a passphrase, PIN, or passkey.
As many spaces as you need
Keep work, home, and one-off transfers apart: each space has its own devices, history, and encryption keys.
Pair with a QR code
Link a new device through an out-of-band QR flow that securely transfers access to it.
Files up to 50 MiB
Send documents, images, or archives. The server copy is removed after all active recipients acknowledge delivery, or cleaned up within 24 hours.
Local history & offline queue
Your history stays on your devices. Messages and selected files can wait locally, but uploading and delivery require a connection.
Up and running in three steps
- Step 01
Create a private space
Start on any device without an account, email, or server password.
- Step 02
Link your devices
Scan a QR code to add your phone, laptop, or tablet to the same private space.
- Step 03
Send without waiting
Send text and files when connected; if a recipient is offline, delivery waits until it reconnects, with undelivered server copies cleaned up within 24 hours.
Let your agents send you things
Reports, screenshots, builds and logs: whatever an AI agent or a script on your server produces can land on your phone, end-to-end encrypted like everything else.
npx -y sendself link <code>Get the code in the app, under Devices → Add device → Agent. It joins as a send-only device: it never receives anything.
npx -y sendself send report.pdfFiles up to 50 MiB each, text with -m. Encrypted and signed on the machine that sends it.
Built so the server cannot decrypt your content
Messages, files, and file metadata are encrypted on your devices. The service receives ciphertext, public keys, authentication data, and delivery metadata — but not readable content or private device keys.
Read the full security model- Content encryption (AES-GCM 256)
- A local group key encrypts messages, files, and file metadata. Keys rotate when a device is revoked.
- Device identity (ECDH P-256)
- Each device creates its own P-256 key pair. Private keys are never sent to the server; an optional encrypted recovery file can restore a device.
- Encrypted device pairing
- A QR code binds the new device's public key to the pairing. The shared group key is sent only inside an encrypted package.
- Temporary server storage
- Delivered messages and files are purged when active recipients acknowledge them; a scheduled cleanup removes anything older than 24 hours.
Questions, answered
Is SendSelf end-to-end encrypted?
Yes. Messages, files, and file metadata are encrypted on your device with AES-GCM before upload. The server receives ciphertext and cannot decrypt the content.
Do I need an account?
No account, email, or server password is required. You can optionally protect this device with a passphrase, PIN, or passkey.
Can the server read my messages or files?
It cannot decrypt your content. It does receive ciphertext and the protocol metadata needed to authenticate requests and deliver messages.
What is the maximum file size?
You can share files up to 50 MiB. The server copy is purged when active recipients acknowledge delivery; anything left over is cleaned up within 24 hours.
Does it work offline?
Partly. The installed PWA keeps local history available and can save outgoing messages or selected files locally, but nothing is uploaded or delivered until you reconnect.
Can I install it as an app?
Yes. SendSelf is a progressive web app. In Chrome, Edge, or Samsung Internet, use the install button the browser offers; on iPhone and iPad, choose Share → Add to Home Screen; in Safari on a Mac, choose File → Add to Dock. Installed, it opens in its own window, keeps local history available offline and, on Android, shows up in the system share sheet.
How do I add another device?
On the new device, choose to link an existing space and show its QR code. Scan it from a linked device; the shared group key is transferred in an encrypted pairing package.
Can a script or an AI agent send me files?
Yes. The sendself command line links a server, a script or an agent to a space as a send-only device: it can send there but never receives anything. In the app, open Devices → Add device → Agent and copy the setup prompt for your agent, or run the command yourself. Everything is encrypted and signed on that machine, like in the app.
Where are the encryption keys kept?
Private device keys are generated locally and never sent to the server. The shared group key is transferred only to linked devices through encrypted pairing and key-rotation packages. An optional encrypted recovery file can carry a copy for restoring a device.