Privacy Model
Last updated
Last updated
The privacy model of the MetaID protocol is designed by the application developers. If application developers do not want their users' data to be public, the following methods are recommended:
Set the node's encryption to 1: Use ECIES encryption. This ensures that only the user can view the data. For detailed information on ECIES encryption and decryption, please refer to the .
Set the node's encryption to 2: Use the ECDH key agreement method. This ensures that only the user and the application can view the data. Users can also authorize or delegate the application to grant access to third parties. For detailed information on ECDH encryption and decryption, please refer to .
The data structure relationship of the MetaID tree is transparent. Some users do not want their MetaID tree data structure relationship information to be exposed. In this scenario, the link mode can be used. By setting the operation to link, the node is set as a link node, pointing to another dataset, which can be another MetaID or another anonymous dataset. This way, users can selectively use anonymous nodes and MetaID protocol nodes.
It is also worth mentioning that when the operation in the PIN transaction is hide, it is also a way of privacy model. At this time, the PIN will declare not to be indexed and referenced by applications, which can be used in scenarios where local applications are used and do not want to be referenced by indexers and third-party applications.