# US 12,602,512 B2 · Data resolution using user domain names > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,512 B2 - Document ID: US12602512B2 - Status: Granted - Kind: B2 - Application number: 17/848,773 - Filed: 2022-06-24 - Published: 2023-12-28 - Granted: 2026-04-14 - Earliest claimed: 2022-06-24 - Assignees: Unstoppable Domains Inc. - Applicants: Unstoppable Domains, Inc. - Inventors: Lisa Seacat DeLuca; Braden Pezeshki - Web page: https://patentgrep.com/patent/US12602512B2 ## CPC - G06F 21/6254: {by anonymising data, e.g. decorrelating personal data from the owner's identification} - G06F 9/451: Execution arrangements for user interfaces - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract According to a present invention embodiment, a system for securing user data comprises one or more memories and at least one processor coupled to the one or more memories. The system receives a domain name provided by a user on a user interface in place of user data requested by the user interface to perform an operation. The system retrieves the user data requested by the user interface based on the domain name. The system provides the user data to perform the operation. Embodiments of the present invention further include a method and computer program product for securing user data in substantially the same manner described above. ## Claims ### Claim 1 A method of securing user data comprising: receiving, via at least one processor, a non-fungible token domain name provided by a user in one or more data fields on a user interface in place of user personal data requested by the one or more data fields of the user interface to perform an operation, wherein the user personal data requested by the one or more data fields is different than the non-fungible token domain name of the user provided in the one or more data fields of the user interface; retrieving, via the at least one processor, the user personal data requested by the one or more data fields of the user interface from a blockchain based on the non-fungible token domain name and a particular data field in which the non-fungible token domain name is provided; and providing, via the at least one processor, the user personal data to perform the operation. ### Claim 2 (depends on 1) The method of claim 1, further comprising: determining that a requesting entity is authorized to receive the user personal data by obtaining permission, from the user, for the requesting entity to be provided the user personal data. ### Claim 3 (depends on 1) The method of claim 1, further comprising: determining that a receiving entity is authorized to receive the user personal data based on a provided use case for the user personal data. ### Claim 4 (depends on 1) The method of claim 1, wherein each of the one or more data fields is selected from a group of: a name field, an email address field, a mailing address field, a credit card field, a phone number field, a billing address field, a government identifier field, a national identifier field, and a cryptocurrency wallet address field. ### Claim 5 A system for securing user data comprising: one or more memories; and at least one processor coupled to the one or more memories, the at least one processor configured to: receive a non-fungible token domain name provided by a user in one or more data fields on a user interface in place of user personal data requested by the one or more data fields of the user interface to perform an operation, wherein the user personal data requested by the one or more data fields is different than the non-fungible token domain name of the user provided in the one or more data fields of the user interface; retrieve the user personal data requested by the one or more data fields of the user interface from a blockchain based on the non-fungible token domain name and a particular data field in which the non-fungible token domain name is provided; and provide the user personal data to perform the operation. ### Claim 6 (depends on 5) The system of claim 5, wherein the at least one processor is further configured to: determine that a requesting entity is authorized to receive the user personal data by obtaining permission, from the user, for the requesting entity to be provided the user personal data. ### Claim 7 (depends on 5) The system of claim 5, wherein the at least one processor is further configured to: determine that a receiving entity is authorized to receive the user personal data based on a provided use case for the user personal data. ### Claim 8 (depends on 5) The system of claim 5, wherein each of the one or more data fields is selected from a group of: a name field, an email address field, a mailing address field, a credit card field, a phone number field, a billing address field, a government identifier field, a national identifier field, and a cryptocurrency wallet address field. ### Claim 9 A computer program product for securing user data, the computer program product comprising one or more non-transitory computer readable media having instructions stored thereon, the instructions executable by at least one processor to cause the at least one processor to: receive a non-fungible token domain name provided by a user in one or more data fields on a user interface in place of user personal data requested by the one or more data fields of the user interface to perform an operation, wherein the user personal data requested by the one or more data fields is different than the non-fungible token domain name of the user provided in the one or more data fields of the user interface; retrieve the user personal data requested by the one or more data fields of the user interface from a blockchain based on the non-fungible token domain name and a particular data field in which the non-fungible token domain name is provided; and provide the user personal data to perform the operation. ### Claim 10 (depends on 9) The computer program product of claim 9, wherein the instructions executable by the at least one processor further cause the at least one processor to: determine that a requesting entity is authorized to receive the user personal data by obtaining permission, from the user, for the requesting entity to be provided the user personal data. ### Claim 11 (depends on 9) The computer program product of claim 9, wherein the instructions executable by the at least one processor further cause the at least one processor to: determine that a receiving entity is authorized to receive the user personal data based on a provided use case for the user personal data. ### Claim 12 (depends on 9) The computer program product of claim 9, wherein each of the one or more data fields is selected from a group of: a name field, an email address field, a mailing address field, a credit card field, a phone number field, a billing address field, a government identifier field, a national identifier field, and a cryptocurrency wallet address field.