US 11,811,907 B2
Data processing permits system with keys
Yacov Salomon, Danville, CA (US); Seth Yates, Danville, CA (US); Maxwell Anderson, San Francisco, CA (US); Vivek Vaidya, San Francisco, CA (US); Anton Winter, San Mateo, CA (US); Samuel Alexander, San Francisco, CA (US); and Tom Chavez, San Francisco, CA (US)
Assigned to Ketch Kloud, Inc., San Francisco, CA (US)
Filed by Ketch Kloud, inc., San Francisco, CA (US)
Filed on Jun. 4, 2021, as Appl. No. 17/339,782.
Application 17/339,782 is a continuation of application No. 16/741,666, filed on Jan. 13, 2020, granted, now 11,032,062.
Claims priority of provisional application 62/901,648, filed on Sep. 17, 2019.
Prior Publication US 2021/0297237 A1, Sep. 23, 2021
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 21/00 (2013.01); H04L 9/06 (2006.01); H04L 9/08 (2006.01); G06F 21/60 (2013.01)
CPC H04L 9/0618 (2013.01) [G06F 21/602 (2013.01); H04L 9/0819 (2013.01)] 20 Claims
OG exemplary drawing
 
20. A non-transitory computer-readable medium storing code for managing data privacy at a system supporting a blockchain network, the code comprising instructions executable by a processor to:
store, at a set of peer nodes for the blockchain network, a smart contract configured for data processing permit management and a distributed ledger comprising a plurality of data processing permits and a plurality of permit keys, wherein each peer node of the set of peer nodes comprises the smart contract and the distributed ledger;
receive, at a peer node of the set of peer nodes, use r-specific data corresponding to a user;
query the distributed ledger of the peer node using the smart contract of the peer node for identifying a data processing permit of the plurality of data processing permits indicating permission to store the user-specific data;
identify, at the peer node and from the plurality of permit keys of the distributed ledger of the peer node, a permit key associated with the data processing permit in response to the querying identifying the data processing permit indicating the permission to store the user-specific data;
encrypt the user-specific data using a cryptographic nonce and encrypting the cryptographic nonce using the permit key based at least in part on the identifying the permit key; and
store the encrypted user-specific data and the encrypted cryptographic nonce in an encrypted database.