Security summary

AliasCloak is designed around end-to-end encrypted message and file content, recipient private-key decryption, generated or custom aliases, browser-based delivery, file transfers up to 4GB, and automatic deletion of encrypted content after delivery. Limited metadata, including timestamps, may not be end-to-end encrypted.

Security model at a glance

End-to-end encrypted content

Message and file content is designed to be encrypted so that the intended recipient’s private key is required for decryption.

Private-key responsibility

The recipient must protect the private key and the device or browser environment where content is decrypted.

Reduced identity exposure

Generated mailboxes, aliases, and public keys can be shared instead of a normal email address or phone number.

Automatic content deletion

Encrypted messages and files are designed to be deleted from the delivery service after receipt.

Large encrypted delivery

Files up to 4GB can be transferred through the browser workflow.

Metadata limitations

Timestamps and other operational metadata may be processed separately from end-to-end encrypted message content.

Threats this design may reduce

  • Exposure of a personal email address or phone number to a sender.
  • Server-side access to end-to-end encrypted message and file content.
  • Long-lived encrypted content remaining in the delivery layer after receipt.
  • Insecure workarounds caused by ordinary attachment-size limits.

Threats users still need to manage

  • Lost, copied, or exposed private keys.
  • Malware, browser extensions, screen capture, or compromised endpoints.
  • Wrong recipients or the wrong public key.
  • Sensitive information revealed in message text, filenames, or external notifications.
  • Downloaded files copied into unmanaged storage or forwarded through another channel.
  • Payment and transaction records associated with a purchased custom alias.
  • Required backups, records, legal holds, or access that automatic deletion could disrupt.

HIPAA and security

Encryption and data minimization can be important safeguards, but they do not create HIPAA compliance on their own. A regulated organization should conduct its own risk analysis, evaluate the vendor relationship and BAA requirements, define authorized use, train users, secure endpoints, and document how records and incidents are handled.

Security questions for AliasCloak deployments

  • Who generates, stores, and backs up the private key?
  • What happens when a device is lost or a team member leaves?
  • Which metadata and payment information are processed?
  • What is the exact deletion lifecycle before and after receipt?
  • Which subprocessors support hosting and payment?
  • How are security reports and incidents communicated?
  • Is a BAA available and appropriate for the intended ePHI use?
Truthful security language

Use specific statements about architecture and controls. Avoid unqualified promises such as “unhackable,” “100% anonymous,” or “HIPAA compliant” without the supporting operational and contractual context.

Official sources

Use primary guidance when building a healthcare communication workflow.