How It Works

This patent extends the Bracket^® encryption system with a sender-validation model. Like the earlier encryption patents, data is encrypted with a sender key, wrapped with an asymmetric key pair, protected by a master key, and delivered to the recipient via a hyperlink.

The key addition is sender validation: before encrypting, the system sends a one-time code to the sender and confirms that the code is associated with the sender’s email address. Only after that validation succeeds does the encryption flow proceed. This binds every encrypted message to a verified sender identity rather than relying on the underlying email envelope alone.

The system incorporates the browser-based access model while adding the sender-validation layer on top of the proven key hierarchy.

What Makes It Different

• Sender validation via one-time code: the encryption flow only proceeds after the sender proves control of their email address through a returned one-time code.
• Browser-based sender interface: data originates from a sender’s browser, consistent with the cloud-native approach introduced in Patent 03.
• Same proven key hierarchy: Master Key, asymmetric key pair, sender key, and Personal Data Key architecture from the foundational patents.
• Hyperlink-based delivery: encrypted content accessed via generated hyperlinks, maintaining the zero-installation recipient experience.

Why It Matters

Encryption protects content in transit and at rest, but it doesn’t, on its own, prove who actually sent the message. Adding a one-time-code validation step ties every encrypted message to a verified sender identity, raising the bar against impersonation and account abuse. Combined with browser-based access, it’s the most complete expression of Bracket’s encryption architecture.