Protected before it leaves your device
Files and text are protected in the browser before they are sent, so privacy stays part of the product from the start.
Security
Security and privacy for temporary encrypted file transfer.
PairSend is designed so you can move something from one device to another without turning the process into cloud storage or a confusing setup flow.
Start on one device.
Open it on the other with a code or QR.
Send what you need.
Let the session end cleanly.
Not another place to keep your files
PairSend is built for the handoff itself. It is not meant to become a long-term storage layer or another folder to manage.
Sessions end on purpose
Every session is temporary by design, so the transfer finishes cleanly instead of hanging around afterward.
The privacy promise stays the same
Paid plans are about convenience and more room to send. They do not change the core privacy model of the product.
What PairSend is designed to protect against
- People watching network traffic along the way.
- The service handling connection setup.
- The systems helping traffic get from one device to the other.
What still depends on your own device habits
- A device or browser that is already compromised.
- Sharing a pairing code with the wrong person.
- Trusting a device you do not actually control.
Key lifecycle
The session stays tied to the handoff
- The connection is created when the two devices pair.
- The active session is meant for the current handoff, not for long-term access later.
- Trusted devices can make repeat handoffs quicker on your own devices.
- Passkeys can add another layer of convenience and protection where supported.
Metadata rules
Privacy is also about keeping the experience simple
- Pairing codes should be treated like private access, not shared casually.
- The product avoids turning transfer details into a visible trail wherever possible.
- Paid plans do not change what the product promises about privacy.