# US 2022/0035949 A1 · Data clean room

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

- Number: US 2022/0035949 A1
- Document ID: US20220035949A1
- Status: Published application
- Kind: A1
- Application number: 17/160,924
- Filed: 2021-01-28
- Published: 2022-02-03
- Earliest claimed: 2020-07-31
- Assignees: Snowflake Inc.
- Applicants: Snowflake Inc.
- Inventors: Rachel Frances Blum; Joshua James Chacona; Christian Kleinerman; Justin Langseth; William L. Stratton, JR.
- Web page: https://patentgrep.com/patent/US20220035949A1

## CPC

- G06F 21/6254: {by anonymising data, e.g. decorrelating personal data from the owner's identification}
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F 16/2455: Query execution
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 21/6263: {during internet communication, e.g. revealing personal data from cookies}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments of the present disclosure may provide a data clean room allowing secure data analysis across multiple accounts, without the use of third parties. Each account may be associated with a different company or party. The data clean room may provide security functions to safeguard sensitive information. For example, the data clean room may restrict access to data in other accounts. The data clean room may also restrict which data may be used in the analysis and may restrict the output. The overlap data may be anonymized to prevent sensitive information from being revealed.

## Claims

### Claim 1

A method comprising:
providing a first party data in a first account in a network-based data system;
providing a second party data in a second account in the network-based data system;
executing, by a processor, a secure function using the first party data to generate a first result, including creating links to the first party data and anonymizing identification information in the first party data;
sharing the secure function with the second account;
executing the secure function using the second party data to generate a second result and restricting the second account from accessing the first party data;
generating a cross reference table with the first and second results, the cross reference table providing anonymized matches of the first and second results;
receiving a query request related to the first and second party data;
based on the cross reference table and the first party data, executing a first portion of the query request to generate results of the first portion of the query request;
sharing a secure query request and the results of the first portion of the query request with the second account, the secure query request including instructions to execute a second portion of the query request; and
receiving final results of the query request from the second account.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
generating an interim table with the results of the portion of the query request; and
sharing the interim table with the second account.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
at the second account, executing the secure query request and joining results of the secure query request with the results of the first portion of the query request from the interim table to generate the final results of the query request.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
generating dummy matching information in the second result for an instance of no match.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
restricting the second account from accessing a code of the secure function; and
restricting the second account from logs related to execution of the first portion of the secure function.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
generating a summary report of the anonymized matches; and
restricting access to the anonymized matches when the number of matches is below a minimum threshold.

### Claim 7 (depends on 1)

The method of claim 1, wherein providing the first party data includes:
uploading a load file to a secure cloud storage location;
storing data from the load file into an enclave account; and
setting access restrictions for the data from the load file based on control information.

### Claim 8

A machine-storage medium embodying instructions that, when executed by a machine, cause the machine to perform operations comprising:
providing a first party data in a first account in a network-based data system;
providing a second party data in a second account in the network-based data system;
executing a secure function using the first party data to generate a first result, including creating links to the first party data and anonymizing identification information in the first party data;
sharing the secure function with the second account;
executing the secure function using the second party data to generate a second result and restricting the second account from accessing the first party data;
generating a cross reference table with the first and second results, the cross reference table providing anonymized matches of the first and second results;
receiving a query request related to the first and second party data;
based on the cross reference table and the first party data, executing a first portion of the query request to generate results of the first portion of the query request;
sharing a secure query request and the results of the first portion of the query request with the second account, the secure query request including instructions to execute a second portion of the query request; and
receiving final results of the query request from the second account.

### Claim 9 (depends on 8)

The machine-storage medium of claim 8, further comprising:
generating an interim table with the results of the first portion of the query request; and
sharing the interim table with the second account.

### Claim 10 (depends on 9)

The machine-storage medium of claim 9, further comprising:
at the second account, executing the secure query request and joining results of the secure query request with the results of the first portion of the query request from the interim table to generate the final results of the query request.

### Claim 11 (depends on 8)

The machine-storage medium of claim 8, further comprising:
generating dummy matching information in the second result for an instance of no match.

### Claim 12 (depends on 8)

The machine-storage medium of claim 8, further comprising:
restricting the second account from accessing a code of the secure function; and
restricting the second account from logs related to execution of the first portion of the secure function.

### Claim 13 (depends on 8)

The machine-storage medium of claim 8, further comprising:
generating a summary report of the anonymized matches; and
restricting access to the anonymized matches when the number of matches is below a minimum threshold.

### Claim 14

A system comprising:
one or more processors of a machine; and
a memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations comprising:
providing a first party data in a first account in a network-based data system;
providing a second party data in a second account in the network-based data system;
executing a secure function using the first party data to generate a first result, including creating links to the first party data and anonymizing identification information in the first party data;
sharing the secure function with the second account;
executing the secure function using the second party data to generate a second result, and restricting the second account from accessing the first party data;
generating a cross reference table with the first and second results, the cross reference table providing anonymized matches of the first and second results;
receiving a query request related to the first and second party data;
based on the cross reference table and the first party data, executing a first portion of the query request to generate results of the first portion of the query request;
sharing a secure query request and the results of the first portion of the query request with the second account, the secure query request including instructions to execute a second portion of the query request; and
receiving final results of the query request from the second account.

### Claim 15 (depends on 14)

The system of claim 14, the operations further comprising:
generating an interim table with the results of the first portion of the query request; and
sharing the interim table with the second account.

### Claim 16 (depends on 15)

The system of claim 15, the operations further comprising:
at the second account, executing the secure query request and joining results of the secure query request with the results of the first portion of the query request from the interim table to generate the final results of the query request.

### Claim 17 (depends on 14)

The system of claim 14, the operations further comprising:
generating dummy matching information in the second result for an instance of no match.

### Claim 18 (depends on 14)

The system of claim 14, the operations further comprising:
restricting the second account from accessing a code of the secure function; and
restricting the second account from logs related to execution of the first portion of the secure function.

### Claim 19 (depends on 14)

The system of claim 14, the operations further comprising:
generating a summary report of the anonymized matches; and
restricting access to the anonymized matches when the number of matches is below a minimum threshold.

### Claim 20 (depends on 14)

The system of claim 14, wherein providing the first party data includes:
uploading a load file to a secure cloud storage location;
storing data from the load file into an enclave account; and
setting access restrictions for the data from the load file based on control information.
