DocuChan · Powered by Bekito

Business file sharing guide

DocuChan replaces the two-message password-ZIP routine with one browser-encrypted delivery link. The recipient needs a supported browser, the complete link, and the password if you set one.

Sender checklist

1. Select the files. DocuChan encrypts the contents and filenames in your browser before upload.
2. Choose burn after download for a one-time handoff, or set an expiry window when the recipient may need to retry.
3. Add a password when you need a separate access check. Share it through a different trusted channel when your risk assessment calls for that.
4. Send the complete link. The part after # contains the decryption key and is as sensitive as the document.

Recipient steps

1. Open the complete link in a supported browser.
2. Enter the password if prompted, then download. Decryption happens in that browser.
3. Store or delete the downloaded copy according to your organization's rules. DocuChan cannot control copies after download.

Security and hosting boundary

For link delivery, DocuChan stores encrypted file bytes plus limited transfer metadata until download deletion or expiry. It does not receive the fragment decryption key or plaintext file contents. The password is an additional server-enforced gate, not the encryption key.

The complete link is a bearer capability: anyone who receives it can attempt access. Passwords can be forwarded, recipient identity is not verified, and an authorized recipient can retain the downloaded file. Expiry is a delivery control, not remote deletion from a recipient's device.

This edition does not promise storage in Japan, a compliance certification, or a particular service level. Confirm your organization's requirements before sharing regulated or highly sensitive material.

Send a file · Technical security model · Privacy details

DocuChan is built and published by Masterbek. This Japanese edition is localized and presented under the Bekito brand.