Amazon Technologies, Inc.

Planetscale, Inc.

Salesforce, Inc.

Slack Technologies, Inc.

Jordan Tyler Williams

Manoj Aggarwal

Korwin Jon Smith

Jason Garfield

Patrick A Reynolds

Nicholas Diego Van Wiggeren

Sam George Lambert

Shlomo Noach

Faisal Yaqub

Wayne Fan

Milo Watanabe

Patrick Kane

Adam Cole

Oluwatosin Afolabi

Marcel Weekes

Fayaz Ashraf

Bernadette Le

Ayesha Bose

Dilip Kumar

Gerard Guy Medioni

Igor Kviatkovsky

Nadav Israel Bhonker

Alon Shoshan

Sanjay Dash

Sarath Geethakumar

Venkatraman Srinivasan

Tamer Avci

Aneeta Bhattacharyya

Oron Anschel

Shunit Haviv Hakimi

Adam Botach

A biometric identification system may store biometric data for later assessment. Data storage parameters, such as cryptographic keys used to encrypt and decrypt the biometric data, may be determined based on the biometric data. In one implementation, the biometric data comprises embedding data in an embedding space. During enrollment and storage, the embedding data is assessed to determine nearest anchor data in the embedding space. Cryptographic parameters, such as an encryption key, are determined based on 'k' anchor data that are within a threshold distance of the embedding data in the embedding space. During query, query embedding data is similarly processed to determine cryptographic parameters, such as a decryption key. The decryption key may then be used to attempt decryption of the encrypted at-rest biometric data. If successful, the decrypted biometric data may then be compared to the query embedding to assert an identity.

System for determining storage parameters for biometric data

This disclosure describes techniques for identifying users that are enrolled for use of a user-recognition system and updating enrollment data of these users over time. To enroll in the user-recognition system, the user may initially scan his or her palm. The resulting image data may later be used when the user requests to be identified by the system by again scanning his or her palm. However, because the characteristics of user palms may change over the time, the user-recognition system may continue to build more and more data for use in recognizing the user, in addition to removing older data that may no longer accurately represent current characteristics of respective user palms.

Utilizing sensor data for automated user identification

A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Database schema branching workflow, with support for data, keyspaces and VSchemas

A biometric input device is used to obtain biometric data from a user. The biometric data is used to determine host card emulation (HCE) parameters that are associated with the user and are used to access a payment account. An interface device that is associated with the biometric input device receives the HCE parameters. The interface device includes a secure execution environment (SEE). A processor in the SEE decrypts and stores the HCE parameters in the memory of the SEE and executes an HCE instance. The HCE instance uses a communication interface to interact with a payment terminal using a contactless communication protocol. The interaction provides payment data to the payment terminal, which is then sent along a payment channel for processing. The HCE instance is then erased, and the SEE is then available for use by another user for another transaction using a different payment account.

Stateless secure payment system

A group-based communication interface with subsidiary file communications is described. A request to share a file in a feed of a group-based communication platform can be received, wherein the feed comprises a channel, a thread, or a direct message associated with a group of the group-based communication platform. A representation of the file can be rendered in a user interface presented via client device(s) of user(s) associated with the group, wherein the representation of the file is associated with an engageable link for accessing the file, and wherein a thread summary indicator, representing a thread of message(s) associated with the file, is presented proximate the representation of the file. Based at least in part on receiving an indication of an interaction with the thread summary indicator, the message(s) associated with the thread can be rendered in the user interface proximate the representation of the file.

Group-based communication interface with subsidiary file communications

Provided is a group-based communication interface configured to efficiently share files among a plurality of group-based communication feeds. Each file share may initiate a subsidiary group-based communication feed to organize and manage discussions regarding shared files. The subsidiary group-based communication feed is unique to the particular file share. Subsequent file shares of the file initiate additional subsidiary group-based communication feeds, such that each discussion stemming from a file share does not overlap with another discussion regarding a different file share of the same file.

Growing community of inventors

San Francisco, CA, United States of America

Jordan Tyler Williams