Token-based secure data management

A computer-implemented method, comprising:

• under control of one or more computer systems configured with executable instructions,
• generating a first token for sensitive data, the first token identifying a data type of the sensitive data;
• storing, in a memory, in association with the first token, the sensitive data as secure data in an encrypted form;
• providing nonsensitive data related to the sensitive data, and the first token in place of the sensitive data, to a first entity authorized to receive the nonsensitive data;
• identifying a set of secure data from the secure data stored in the memory, individual secure data of the set of secure data having a data type that matches the data type identified by the first token;
• generating a hash for individual secure data in the set of secure data;
• and
• providing the hash for individual secure data in the set of secure data to a second entity not authorized to receive the sensitive data associated with the set of secure data.

One or more non-transitory computer-readable media storing computer-executable instructions that, as a result of being executed, cause one or more processors to:

• generating a first token for a first piece of sensitive data;
• storing, in a memory, the first piece of sensitive data as secure data;
• providing, to a first entity, a first nonsensitive data associated with the first piece of sensitive data, and the first token in place of the first piece of sensitive data;
• generating a second token for a second piece of sensitive data;
• providing the second token in place of the second piece of sensitive data to a second entity that maintains nonsensitive data associated with the second piece of sensitive data;
• generating a first hash associated with the first piece of sensitive data;
• generating a second hash associated with the second piece of sensitive data;
• determining that the first hash matches the second hash;
• and
• as a result of having determined that the first hash matches the second hash, indicating to the second entity that the first piece of sensitive data and the second piece of sensitive data are linked.