UseCrypt’s engineering history extends beyond encryption in transit. Four US patent documents describe combinations involving application views, local data, notifications, emergency actions and device checks. A separate security-assessment record examines the behaviour of a specific Messenger release.
Four patent records, four sets of mechanisms
US11341218B2 describes messaging interfaces with different access modes. US11210407B2 concerns an electronic communications device and messaging application, including an emergency-code response. US11122014B2 addresses notification behaviour linked with application and database states. US11228910B2 describes secure communication mechanisms involving device checks and access to the microphone. The public records name Kamil Kaczyński and Michał Glet as inventors.
The documents record grants in 2021 and 2022. They are linked as historical engineering and patent records. Current enforceability, maintenance fees and ownership should be checked in the relevant register rather than inferred from the B2 publication number alone.
Why the combinations matter to a user
A private message can leak through a notification even when its transport was encrypted. A phone can retain a database after a conversation ends. Another application can reach a microphone before voice data is encrypted. A person under pressure can be forced to open an interface.
These are state-transition problems. A useful security design considers what the application exposes when closed, what becomes available when opened and what the server will do after an emergency response. Patent claims are valuable here because they record combinations and sequences, not only short feature labels.
The dated Messenger assessment
AVLab’s report on the October 2020 assessment identifies Oded Vanunu and Roman Zaikin and the then-current iOS version 2.34. It describes black-box work, penetration and functional testing, protected voice communication and local-database behaviour. The database finding depended on configuring an application PIN.
That configuration detail is part of the finding, not a footnote to remove. The publication is a route into a dated assessment; it is not a claim that Check Point issued a product certificate or that every subsequent version was tested.
Privacy is a sequence of application states
An encrypted connection protects data while it travels. A messaging application also displays data, keeps local records, handles incoming events and obtains audio from a microphone. Those operations create separate opportunities for disclosure. A message may remain encrypted on the network while its sender appears in a notification on a borrowed phone.
That distinction is the engineering context of these patent records. They describe coordinated behaviour across the interface, database, device and service. The useful question is what happens at a transition: when an application opens, when it closes, when another code is entered or when an incoming call arrives. The design cannot be understood by reading only the name of its transport encryption.
For an evaluator, a state model should identify inputs, available secrets, visible information and persistent changes. Two screens that look similar can expose different information. Two encrypted databases can behave differently when an application is closed. The analysis therefore follows the mechanism and its observable effects, rather than treating a list of feature names as a security result.
US11341218B2 and controlled views of message data
US11341218B2, claim 1, combines an encrypted local message database, access-code requirements and different interface modes. One mode gives access to all stored message data; another gives access to a subset. The claim also coordinates a different code with database deletion and communication to the administering server to unregister the identity. The grant publication is dated 24 May 2022.
The engineering importance is the coordination. Changing what a screen shows is not necessarily enough to change what an incoming event reveals. An evaluator should therefore observe both the local interface and subsequent service behaviour. A narrow viewing mode, an emergency response and a server notification policy are different controls whose interactions matter.
A practical test can create distinguishable conversations, enter each documented mode and record the visible set. Then send fresh messages from controlled test accounts and compare the notifications. Repeat after closing and reopening the application. These are proposed tests of a current implementation, not results implied by the patent grant.
US11210407B2 and an emergency-code response
US11210407B2, claims 1 and 7, describes encrypted message storage, a normal access code and a different predetermined code. Entering the latter triggers deletion of the encrypted database and a request to unregister the identity so that the service subsequently stops sending notifications to it. The grant publication is dated 28 December 2021.
This mechanism addresses a problem which a stronger transport cipher cannot solve by itself: a person can be pressured to operate an authorised device. The patent’s response is an application and service workflow. It is not an assertion that software can prevent every form of coercion or guarantee a person’s physical safety.
Testing a destructive emergency feature requires disposable accounts and data, never a reader’s live archive. Observe the device result and server response separately, including the case where the network is unavailable. Distinguish logical removal of a file from a forensic assessment of recoverable copies. Record retries, restored backups and other authorised installations. Otherwise one successful screen demonstration leaves the most important persistence questions unanswered.
US11122014B2 and notifications while the application is closed
US11122014B2, claims 1 and 2, coordinates launched and unlaunched states, encrypted database handling, authorisation-token storage and displayed notifications. The closed-state path permits a notification without revealing the contact information; the launched-state path can display the calling party. The message-related dependent claim extends the distinction to contact information and message previews.
The engineering problem is not merely whether an alert is sent. It is which information becomes available before the user has entered the application. A device can need to signal an incoming event without exposing the sender or content on its screen. That creates a useful separation between delivery awareness and access to the conversation.
For a contemporary test, compare foreground, background, locked-screen and fully closed states using documented platform behaviour. Capture what is visible and what is retained in notification history. The patent describes a particular coordination; the result of a build-specific test must show how that coordination survives the operating system’s actual lifecycle.
US11228910B2 and the microphone before encryption
US11228910B2, claims 1 to 5, concerns device-security checks and microphone access. Its claimed combinations include operating-system indicators, root-related capabilities and unexpected components, with a warning when compromise conditions are detected. They also check exclusive microphone access before an incoming call; the dependent claims address continued checks during a call.
Its relevance is where audio originates. Encrypting a voice stream protects the resulting stream; another route that obtains sound before that encryption is a different problem. A device-level check is therefore aimed at the boundary around capture, not just the boundary around transmission.
A test should identify the operating-system permissions and behaviours it relies on. A controlled conflicting application, a clean device and a deliberately altered test device can provide comparison cases. Record cancellation, warning and recovery behaviour. Root detection is a signal to evaluate; it is not a universal proof that every undetected device is uncompromised.
The four mechanisms protect different moments
The records should not be collapsed into four names for one cipher. Interface modes concern the set of information presented to a user. Emergency codes concern a particular input and coordinated local and service action. Notification controls concern information visible outside the open conversation. Device and microphone checks concern the environment in which a session begins.
That creates a layered design narrative. Before access, minimise unintended information on the screen. During access, decide which view is available. Under an emergency condition, define the local and service response. Before a voice session, inspect the capture environment. Each mechanism addresses a different moment in a person’s use of a phone.
Layering is meaningful only when interactions are tested. For example, an emergency local response that is followed by an identifying server notification may fail the intended user scenario. A private interface mode with an ordinary message preview may have a similar mismatch. These examples explain what to look for; they do not allege measured defects in UseCrypt.
From a patent document to a tested product
A patent document and a product build have different identities. The document is found by its publication number. The build is found by its version, platform and preferably a reproducible identifier. An evaluator needs a map connecting the claimed mechanism to the behaviour actually implemented in that build.
That map should say which features are mandatory, configurable or absent on a particular platform. It should also distinguish an independent claim’s combination from examples and dependent claims. A product carrying the same name across releases may change implementation details; testing one historical version does not automatically test the next.
This is where detailed documentation earns its value. Instead of saying that a product has patents and is therefore secure, it lets a reviewer trace a particular problem to a mechanism, a configured function and an observation. The resulting argument is specific enough to reproduce and challenge.
What the historical security assessment adds
The separately linked AVLab publication identifies a dated assessment of iOS version 2.34 by Oded Vanunu and Roman Zaikin. Its reported local-database protection depends on an application PIN. That condition belongs beside the finding because a reader needs it to understand which configuration was examined.
The distinction between a named expert’s work and an employer’s corporate certification is important. A professional affiliation provides context about experience. It does not change who commissioned, conducted or signed a particular report. The strongest public description retains the testers, date, version, method and configuration together.
A later assessment should examine the current build, not merely cite the earlier names. A patent explains a design combination; a historical test explains observed behaviour in a defined sample. Together they supply more information than either alone, but they answer different questions.
A test record professionals can reproduce
The OWASP Mobile Application Security Testing Guide provides a public testing reference. It is not a UseCrypt audit or endorsement. Its role here is to direct reviewers to established mobile-testing material rather than rely on a vendor-created checklist alone.
For each product scenario, define the starting state, test account, data, device and application settings. Identify the action being exercised and the result expected at the screen, database and server. Capture enough evidence to distinguish a failed operation from a successful operation that merely produced a different visual message.
Repeat across lifecycle changes and failure conditions. An interrupted network request, restart or restored copy can reveal whether the controls remain coordinated. Publish the result and its scope. A clear record of what was and was not exercised is more useful to an engineer than a broad badge labelled military-grade.
Historical grants and current patent status
A granted publication number is a stable route to a historical invention record. It is not, by itself, proof that the right is currently enforceable or owned by a particular party. The Google Patents entry for US11341218B2 currently displays a fee-related expired status and explicitly warns that its legal-status information is not a legal conclusion.
USPTO’s patent-maintenance resources provide the official starting point for current maintenance and ownership enquiries. Legal diligence should use the relevant official record rather than infer active protection from a grant date or an originally projected expiry year.
That distinction preserves the genuine engineering history. The public descriptions, drawings and claims remain valuable documents for understanding what was proposed and granted. Their technical content and the present legal position should be reported as separate matters.
These Messenger patents are not a specification of HVKM
The four records discussed here concern messaging applications and devices. They should not be used as a substitute for the split-key file-protection explanation in the UseCrypt Safe HVKM analysis. Product-family branding does not turn one mechanism into another.
For the founder’s history, Paweł Makowski’s biography describes building and promoting the venture. The patent records name Kamil Kaczyński and Michał Glet as inventors. Keeping those contributions distinct gives the project a more substantial account: entrepreneurship, research, implementation and evaluation are visible rather than compressed into one person’s role.
Further design and assessment records
A patent records an invention’s claimed scope. A product specification explains an implementation. A test report records what was examined and found under particular conditions. None of these can simply replace the other two.
The UseCrypt patent register and security-review register provide further routes to the documents. For the different file-encryption design, read the Safe and HVKM guide. The founder’s biography distinguishes the commercial venture from the named researchers’ inventive work.