# US 2022/0035941 A1 · Data protection query interface > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2022/0035941 A1 - Document ID: US20220035941A1 - Status: Published application - Kind: A1 - Application number: 17/145,272 - Filed: 2021-01-08 - Published: 2022-02-03 - Earliest claimed: 2020-07-31 - Assignees: Mx Technologies, Inc. - Applicants: MX Technologies, Inc. - Inventors: DANIEL D. JONES - Web page: https://patentgrep.com/patent/US20220035941A1 ## CPC - G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes} - G06F 21/6254: {by anonymising data, e.g. decorrelating personal data from the owner's identification} - G06F 16/2455: Query execution - G06F 16/2457: with adaptation to user needs - G06F 16/248: Presentation of query results - H04W 12/02: Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] - G06N 20/00: Machine learning - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS ## Abstract Apparatuses, methods, program products, and systems are disclosed for data protection query interface. An apparatus includes a processor and a memory that stores code executable by the processor to receive, via a query interface, a query from a third-party to verify sensitive data associated with a user, analyze the query to identify a type of the user's sensitive data to verify, and generate a verification response to the query based on verifying the user's sensitive data related to the type of sensitive data to verify without exposing the user's sensitive data to the third-party. ## Claims ### Claim 1 An apparatus, comprising: a processor; a memory that stores code executable by the processor to: receive a query from a third-party to verify sensitive data associated with a user, the query received via a query interface; analyze the query to identify a type of the user's sensitive data to verify; and generate a verification response to the query based on verifying the user's sensitive data related to the type of sensitive data to verify without exposing the user's sensitive data to the third-party. ### Claim 2 (depends on 1) The apparatus of claim 1, wherein the code is executable to: login to at least one user account at a third-party system using previously-stored electronic credentials for the user in response to receiving and analyzing the query; access the user's sensitive data from the third-party account; and analyze the accessed sensitive data to generate the verification response to the query. ### Claim 3 (depends on 1) The apparatus of claim 1, wherein the query comprises an identifier for the user, the code executable by the processor to parse the query to identify the identifier for the user, the identifier used to access the user's sensitive data related to the type of sensitive data to verify. ### Claim 4 (depends on 1) The apparatus of claim 1, wherein the type of the user's sensitive data to verify comprises identification information for the user. ### Claim 5 (depends on 1) The apparatus of claim 1, wherein the type of the user's sensitive data to verify comprises financial information for the user. ### Claim 6 (depends on 1) The apparatus of claim 1, wherein the code is executable by the processor to reject the query in response to a result of the query exposing the user's sensitive data. ### Claim 7 (depends on 1) The apparatus of claim 1, wherein the type of the query is determined based on identifying at least one of a command type, a request identifier, and a user selection that is received as part of the query via the query interface. ### Claim 8 (depends on 1) The apparatus of claim 1, wherein the verification response comprises a Boolean response indicating a verification of the user's sensitive data related to the query. ### Claim 9 (depends on 1) The apparatus of claim 1, wherein the code is executable by the processor to receive and set privacy settings for accessing the user's sensitive data, the privacy settings defining at least one of user accounts that queries are allowed to run on, transaction types that queries are allowed to run on, third-parties that are authorized to submit queries, and types of queries that are allowed. ### Claim 10 (depends on 9) The apparatus of claim 9, wherein the code is executable by the processor to set the privacy settings on one of a per account basis and a per third-party basis. ### Claim 11 (depends on 1) The apparatus of claim 1, wherein the code is executable by the processor to prompt the user for authorization to process the query in response to receiving the query. ### Claim 12 (depends on 1) The apparatus of claim 1, wherein the code is executable by the processor to translate the received query into a query language that is used to access a data store for the user's sensitive data. ### Claim 13 A method, comprising: receiving a query from a third-party to verify sensitive data associated with a user, the query received via a query interface; analyzing the query to identify a type of the user's sensitive data to verify; and generating a verification response to the query based on verifying the user's sensitive data related to the type of sensitive data to verify without exposing the user's sensitive data to the third-party. ### Claim 14 (depends on 13) The method of claim 13, further comprising: logging in to at least one user account at a third-party system using previously-stored electronic credentials for the user in response to receiving and analyzing the query; accessing the user's sensitive data from the third-party account; and analyzing the accessed sensitive data to generate the verification response to the query. ### Claim 15 (depends on 13) The method of claim 13, further comprising parsing the query to identify an identifier for the user, the identifier used to access the user's sensitive data related to the type of sensitive data to verify. ### Claim 16 (depends on 13) The method of claim 13, wherein the type of the user's sensitive data to verify comprises one or more of identification information for the user and financial information for the user. ### Claim 17 (depends on 13) The method of claim 13, wherein the verification response comprises a Boolean response indicating a verification of the user's sensitive data related to the query. ### Claim 18 (depends on 13) The method of claim 13, further comprising receiving and setting privacy settings for accessing the user's sensitive data, the privacy settings defining at least one of user accounts that queries are allowed to run on, transaction types that queries are allowed to run on, third-parties that are authorized to submit queries, and types of queries that are allowed. ### Claim 19 An apparatus, comprising: means for receiving a query from a third-party to verify sensitive data associated with a user, the query received via a query interface; means for analyzing the query to identify a type of the user's sensitive data to verify; means for generating a verification response to the query based on verifying the user's sensitive data related to the type of sensitive data to verify without exposing the user's sensitive data to the third-party. ### Claim 20 (depends on 19) The apparatus of claim 19, further comprising: means for logging in to at least one user account at a third-party system using previously-stored electronic credentials for the user in response to receiving and analyzing the query; means for accessing the user's sensitive data from the third-party account; and means for analyzing the accessed sensitive data to generate the verification response to the query.