Send a file. Keep the key.

The file is encrypted here, in your browser, with its name inside the ciphertext. The server gets bytes it cannot read. You get a link, a QR code, or a token you can say aloud; whoever has it gets the file, and nobody else does, the server included.

Drop a file here, or click to choose Encrypted in this browser before upload · under 4 MB for a one-off transfer · any size into a vault

Where it lives

One transfer: uploaded once, handed over once, expires Into a vault: versioned, updatable, clonable with sgit

Expires

Downloads

How to hand it over

A link with the key in it (and a QR code) A friendly token you can say aloud, river-cloud-3847 A link, with the key sent separately

For a vault the link carries the read key; the vault key stays on this device.

to the server set in Settings

What happens, in one table

Step	Where	What the server gets
The name goes inside an envelope in front of the file	this browser	nothing
The whole thing is encrypted with AES-256-GCM under a fresh key	this browser	nothing
The ciphertext is uploaded as one transfer, or committed into a vault	the server you chose	ciphertext, its size, a hashed sender IP, a content type hint you choose
The link is built with the key after the `#`	this browser	nothing: browsers never send the fragment
The link is drawn as a QR code	this browser	nothing

How it works · What the server sees · Vaults and keys · the code this page runs is api.send.sgit.ai v0.1.1, pinned.