Secure healthcare file sharing should protect the file in transit and at rest, restrict access to the intended recipient, minimize unnecessary copies, support required record handling, and use appropriate vendor agreements. AliasCloak supports browser-based encrypted transfers up to 4GB.
Why ordinary email attachments create problems
Attachment limits can push users toward personal drives, consumer file-sharing links, compressed archives with separately emailed passwords, or multiple copied messages. Even when transport is encrypted, downloaded files may remain in inboxes, sent folders, local download directories, backups, or forwarded threads.
Secure file-sharing checklist
- Confirm the intended recipient and the authorized purpose.
- Send only the minimum information required.
- Use a channel approved for the sensitivity and size of the file.
- Protect decryption keys, mailbox links, devices, and local downloads.
- Set expiration, deletion, or retrieval rules appropriate to the workflow.
- Record required clinical or administrative documents in the proper system.
- Review the vendor’s role, subprocessors, incident procedures, and BAA status.
- Train users not to re-upload or forward files through unapproved channels.
How AliasCloak file delivery works
Share a mailbox route
Provide a generated mailbox identifier, custom alias, or public key.
Encrypt and deliver
The sender uses the browser workflow to send a message or file up to 4GB.
Decrypt and handle
The recipient decrypts with the appropriate private key, then stores or records the file according to policy.
Limited server retention helps—but is not a records policy
Limited encrypted retention can reduce long-term server exposure, but it is not a records policy. Current AliasCloak deployments can use a seven-day hot-retention cutoff for unacknowledged one-shot messages and, when configured, up to 30 additional days of encrypted cold storage before final deletion. The receiving organization still needs to move records that must be retained into an approved system before working copies expire.
Good use cases
- Intake forms and supporting documentation
- Referral packets and care-coordination files
- Large image, archive, or document delivery
- Private delivery where exposing a normal email address is unnecessary
- One-directional or occasional encrypted transfer
End-to-end encryption does not protect a file after an authorized recipient decrypts it on an infected, shared, or poorly secured device.
Official sources
Use primary guidance when building a healthcare communication workflow.