Send business documents. Retire the password-ZIP routine.
Create one encrypted link with an optional password and a clear expiry. Your recipient opens it in a browser.
Send and receive, end to end
See browser encryption, link creation, and receipt in one illustrated flow.
Animated demo · actual speed depends on your connection
Send to a device with Beam.
Beam tries a direct WebRTC path between devices. When that is unavailable, configured TURN may relay data that remains encrypted at the application layer.
Compare the verification codes
Compare both devices' codes through a trusted channel before approving the transfer.
Transfer multiple files between devices
Follow transfer progress and cancel a transfer when needed.
Connect nearby or remote devices
Use same-network discovery or pairing codes and QR codes. Connectivity depends on the network environment.
Free · no app or account · both devices must be online
A browser toolkit for document handoffs
Choose encrypted delivery, local PDF work, or live collaboration for the task at hand.
Encrypted in the browser
Contents and filenames are encrypted with AES-256-GCM before upload. Stored file bytes are ciphertext.
Share with an expiring link
Choose deletion after a completed download or a time-based expiry when you send.
No recipient account
Recipients use a current browser, the complete link, and the password if one was set.
One link for several files
Bundle and encrypt several files in the browser, then share them through one link.
Process PDFs on-device
Organize, compress, and check PDFs in the browser without uploading them unless you explicitly choose Send.
Collaborate in real time
Rooms synchronizes encrypted document changes between participant browsers without a server-side document copy.
A clear handoff for both sides
Choose the file and expiry, then share the complete link through a trusted channel.
Choose files
Select one or more files, then add a password and expiry if needed.
Encrypt in the browser
Contents and filenames are encrypted before ciphertext is uploaded.
Share the complete link
The recipient decrypts in a supported browser. In burn mode, server-side deletion begins after download completion is confirmed.
What the link protects
Contents and filenames are encrypted in the browser. The complete link contains the key; password and expiry add separate access controls.
Questions before use
Does DocuChan verify recipient identity?
No. Anyone with the link and password can attempt access. Add a separate identity check when required.
Is the password the encryption key?
No. The key follows # in the complete link. The password is an additional server check.
Does expiry remove the recipient's copy?
No. It controls access to ciphertext on DocuChan. The recipient controls saved copies.
Is data guaranteed to stay in Japan?
No such guarantee is made. Confirm deployment details when storage region is a requirement.
Does the recipient need an account?
Not for a normal sharing link. They need a current browser, the complete link, and any password.
What should I tell the recipient?
Provide the complete link, expiry, and password if set. Choose a separate password channel based on your policy.
Share one document securely
Select a file, set an optional password and expiry, then share one link.