# US 2026/0064863 A1 · System and method for operating a secure database

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0064863 A1
- Document ID: US20260064863A1
- Status: Published application
- Kind: A1
- Application number: 19/381,167
- Filed: 2025-11-06
- Published: 2026-03-05
- Earliest claimed: 2021-09-24
- Assignees: The Ethical Identity Company
- Applicants: The Ethical Identity Company
- Inventors: Jonathan Chan; Travis Howe
- Web page: https://patentgrep.com/patent/US20260064863A1

## CPC

- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F 21/6254: {by anonymising data, e.g. decorrelating personal data from the owner's identification}
- H04L 9/0869: {involving random numbers or seeds}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Various implementations of a system and method may include a secure database that can be structured with a strong emphasis on individual entity permissions and enforcement of read, write, and audit policies relative to individual database record entries to close security and privacy gaps that exist in current database systems.

## Claims

### Claim 1

An active node of a secure database system, comprising:
at least one processor; and
at least one memory that stores computer executable instructions, wherein, when the computer executable instructions are executed by the at least one processor, the at least one processor are configured to:
receive a request to store a private data record;
encrypt the private data record with a first randomly generated data key to result in an encrypted private data record;
encrypt the first randomly generated data key using a first type of encryption and a second randomly generated data key to result in a first encrypted system access key;
encrypt the second randomly generated data key using a second type of encryption to result in at least one second encrypted system access key, wherein the second type of encryption uses a public key from a randomly selected node of a plurality of nodes that, with the active node, form part of the secure database system;
transmit the encrypted private data record to a plurality of nodes for validation;
add the encrypted private data record to a datastore in the node based on validating that the encrypted private data record can be written to a datastore and receiving messages from the plurality of nodes that the encrypted private data record can be written to the datastore, wherein the datastore mirrors other datastores associated with respective nodes of the plurality of nodes;
store the first encrypted system access key and the at least one second encrypted system access key in an external access key database; and
enable decryption access to the encrypted private data record using the at least one second encrypted system access key based on consensus authorization with the plurality of nodes.

### Claim 2 (depends on 1)

The active node of the secure database system of claim 1, wherein the datastore is a blockchain ledger.

### Claim 3 (depends on 1)

The active node of the secure database system of claim 1, wherein encrypting the second randomly generated data key using a second type of encryption results in at least two second encrypted system access keys.

### Claim 4 (depends on 3)

The active node of the secure database system of claim 3, wherein the at least two second encrypted system access keys further comprise an encrypted active node system access key and an encrypted audit node system access key.

### Claim 5 (depends on 4)

The active node of the secure database system of claim 4, wherein the encrypted active node system access key and the encrypted audit node system access key contain different portions of second randomly generated data key.

### Claim 6 (depends on 3)

The active node of the secure database system of claim 3, wherein the encrypted active node system access key is encrypted with a public key associated with the active node.

### Claim 7 (depends on 3)

The active node of the secure database system of claim 3, wherein the first encrypted system access key, the encrypted active node system access key, and the encrypted audit node system access key comprise an external access key, wherein the external access key is stored in the external access key database.

### Claim 8 (depends on 7)

The active node of the secure database system of claim 7, wherein the external access key database is separate from the datastore, wherein records are permitted to be deleted from the external access key database, and wherein entries in the datastore are not permitted to be deleted from the datastore.

### Claim 9 (depends on 1)

The active node of the secure database system of claim 1, wherein the request to store the private data record is logged.

### Claim 10 (depends on 7)

The active node of the secure database system of claim 7, wherein the request to store the private data record is logged in the datastore, wherein the datastore is a blockchain ledger.

### Claim 11

A method of operating a secure database system, comprising:
receiving a request to store a private data record;
encrypting the private data record with a first randomly generated data key to result in an encrypted private data record;
encrypting the first randomly generated data key using a first type of encryption and a second randomly generated data key to result in a first encrypted system access key;
encrypting the second randomly generated data key using a second type of encryption to result in at least one second encrypted system access key, wherein the second type of encryption uses a public key from a randomly selected node of a plurality of nodes that, with the active node, form part of the secure database system;
transmitting the encrypted private data record to a plurality of nodes for validation;
adding the encrypted private data record to a datastore in the node based on validating that the encrypted private data record can be written to a datastore and receiving messages from the plurality of nodes that the encrypted private data record can be written to the datastore, wherein the datastore mirrors other datastores associated with respective nodes of the plurality of nodes;
storing the first encrypted system access key and the at least one second encrypted system access key in an external access key database; and
enabling decryption access to the encrypted private data record using the at least one second encrypted system access key based on consensus authorization with the plurality of nodes.

### Claim 12 (depends on 11)

The method of operating the secure database system of claim 11, wherein the datastore is a blockchain ledger.

### Claim 13 (depends on 11)

The method of operating the secure database system of claim 11, wherein encrypting the second randomly generated data key using a second type of encryption results in at least two second encrypted system access keys.

### Claim 14 (depends on 13)

The method of operating the secure database system of claim 13, wherein the at least two second encrypted system access keys further comprise an encrypted active node system access key and an encrypted audit node system access key.

### Claim 15 (depends on 14)

The method of operating the secure database system of claim 14, wherein the encrypted active node system access key and the encrypted audit node system access key contain different portions of second randomly generated data key.

### Claim 16 (depends on 13)

The method of operating the secure database system of claim 13, wherein the encrypted active node system access key is encrypted with a public key associated with the active node.

### Claim 17 (depends on 13)

The method of operating the secure database system of claim 13, wherein the first encrypted system access key, the encrypted active node system access key, and the encrypted audit node system access key comprise an external access key, wherein the external access key is stored in the external access key database.

### Claim 18 (depends on 17)

The method of operating the secure database system of claim 17, wherein the external access key database is separate from the datastore, wherein records are permitted to be deleted from the external access key database, and wherein entries in the datastore are not permitted to be deleted form the datastore.

### Claim 19 (depends on 11)

The method of operating the secure database system of claim 11, wherein the request to store the private data record is logged.

### Claim 20 (depends on 17)

The method of operating the secure database system of claim 17, wherein the request to store the private data record is logged in the datastore, wherein the datastore is a blockchain ledger.
