UseCrypt Messenger patents: distinct application-protection mechanisms

Notifications and a locked database: US 11,122,014 B2

The full US11122014B2 record describes notifications in different application states. An authorisation token supports call handling while the database remains encrypted, with displayed information depending on the application state. This separates signalling from archive access; it is not a general RSA split-key mechanism.

Distress response: US 11,210,407 B2

The full US11210407B2 record documents coordinated device and infrastructure behaviour in response to a distress indication. Technical conclusions should identify the specific embodiment. Recording an invention does not establish that every described variant is deployed in the current application.

Interface and operating modes: US 11,341,218 B2

The full US11341218B2 record concerns a messaging interface and distinct operating modes, including behaviour associated with coercion. The engineering question is which data and functions the application exposes in each mode, not an increase in encryption key length.

Device security conditions: US 11,228,910 B2

The US11228910B2 record is a separate portfolio document. Its full description and claims are the starting point for mechanism analysis, rather than a slogan about resistance to every form of device compromise.

Safe HVKM is a separate subject

The HVKM, RSA and key-capsule analysis is based on UseCrypt Safe 1.3 documentation. We do not attribute that mechanism to all four Messenger patents. The Messenger technical explanation separately examines SQLite, AES-256, application passcodes, key storage and notifications.

Patent document, implementation and assessment

A patent records an invention. A specification describes a product. Testing provides observations about a particular version. These evidence layers should be connected, not substituted for one another. Current legal status and maintenance fees require verification in the official USPTO register; this page does not declare that legal protection is currently in force.

UseCrypt Editorial Team, 8 October 2026. Continue with the UseCrypt patent index, assessment scopes and Safe and Messenger's full technical workflow.

How can a patent record be connected to product documentation?

Start with the specific document number and mechanism under examination. Identify the application version, configuration and behaviour that should implement it. Observation of that version then connects the invention description to the working product. For example, notifications should be examined before and after unlocking, while database access is tested separately from call signalling. This creates an evidence path from document to technical requirement to repeatable test, rather than treating a portfolio number as a universal product guarantee.