HaloChat is built on a privacy-by-design principle. All communications are protected through End-to-End Encryption (E2EE), ensuring that message content can only be decrypted on the communicating devices. Servers do not access or process plaintext data.
Within its Web3 architecture, HaloChat supports a wallet-based identity framework. Users may authenticate through wallet addresses, reducing reliance on centralized accounts and minimizing the concentration of personally identifiable information.
At the data management level, HaloChat does not retain chat content. Users can independently configure message retention and deletion policies, lowering the risks associated with long-term data storage.
For essential system logs and security monitoring, HaloChat applies de-identification measures wherever possible. Such data is used strictly for maintaining network security and service stability, and is not utilized for user profiling or content analysis.