Journey.ai

Michael Joseph Frendo

Alexander John Shockley

Shmuel Shaffer

James M Behmke

Brett Shockley

Kenneth Keiter

Robert Taylor Bartlett

In one embodiment, the techniques herein are directed to coordinating conveying a reason for a call from a user device. For instance, an illustrative method herein may comprise: receiving, at an intermediate service device, a message from a user device, the message informative of a second device to participate in a call with a user of the user device and a reason for the call; and conveying, from the intermediate service device, the user device, the user, and the reason for the call to the second device, wherein the second device initiates the call to the user device and is aware of the user and the reason for the call prior to initiating the call.

Coordinating conveying a reason for a call from a user device

In one embodiment, a method herein may comprise: receiving, at a first device, an encrypted private key of a second device encrypted using a public key of the first device, wherein the second device encrypted data into encrypted data using a public key of the second device and stored the encrypted data on a storage server; and decrypting, by the first device, a private key of the second device from the encrypted private key using a private key of the first device; and accessing, by the first device, the encrypted data on the storage server by utilizing the private key of die second device.

Storing encrypted data for access by a trusted device

The techniques herein are directed generally to a 'zero-knowledge' data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Receiving information through a zero-knowledge data management network

Sourcing information for a zero-knowledge data management network

The techniques herein are directed generally to personalized secure communication session management, such as for virtual private networks (VPNs). In one embodiment, a user is authenticated at a client device to verify that the user is present at the client device and authorized to access one or more secured resources, and in response, a secure communication session is established for the client device to access the secured resources. At a later time during the secure communication session, it is determined whether the user is still authenticated at the client device, such that if so, access to the one or more secured resources is maintained on the secure communication session, or else access is restricted to the one or more secured resources (e.g., the session is terminated, or access is otherwise limited).

Personalized secure communication session management

Controlling transmission of information through a zero-knowledge data management network

The techniques herein are directed generally to a 'zero-knowledge' data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data-all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

Growing community of inventors

Boulder, CO, United States of America

Michael Joseph Frendo