How It Works

This patent extends the Bracket encryption system with a subscriber-based access model. Like the earlier encryption patents, data arrives from a sender’s browser, 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 subscriber verification—the system checks whether a recipient is a registered subscriber before processing. This enables differentiated handling: verified subscribers can get streamlined access to encrypted content, while the encryption flow remains seamless for everyone else.

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

What Makes It Different

• Subscriber verification: the system checks recipient subscriber status before processing, enabling differentiated encryption workflows.
• 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 optional 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

Enterprise encryption needs to be managed, not just deployed. Subscriber verification lets organizations differentiate between verified partners and ad-hoc recipients, enabling more sophisticated encryption workflows. Combined with browser-based access, it’s the most complete expression of Bracket’s encryption architecture.