> For the complete documentation index, see [llms.txt](https://docs.miuro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miuro.ai/appendix/appendix-a-security-privacy-and-compliance-notes.md). # Appendix A · Security, Privacy and Compliance Notes MIURO places high importance on user data security, hardware security, fund security and overall compliance. The following outlines our main measures for security and privacy, as well as key information users should understand. ### 1. Data Privacy Protection #### Local Inference First MINI and ORIGIN devices are equipped with high-performance NPUs and support local large-model inference. User voice samples, training data and generated works are processed on the device by default and are not automatically uploaded to the cloud. Related content is uploaded only when the user actively chooses to publish or distribute it. #### Data Control Rights Users have full control over their own voice models and creative data. Any data upload or sharing requires explicit secondary confirmation from the user. Content stored through distributed storage uses AES-256 encryption and sharded storage. ### 2. Hardware and Device Security #### Industrial-Grade Security Design Devices use industrial-grade motherboards and components that have passed long-term stability testing. Each device is burned with a unique device ID at the factory, which cannot be tampered with after binding. Devices are equipped with tamper-resistant casing. Opening the casing triggers the protection mechanism and automatically disconnects the device from the network. #### Firmware Security All firmware upgrades require dual-signature verification to prevent malicious downgrades or tampering. Secure OTA, or Over-The-Air, update mechanisms are supported. ### 3. Smart Contract and Fund Security #### Multiple Security Audits Before TGE, MIURO will complete dual audits by top security firms such as Trail of Bits and OpenZeppelin. Audit reports will be made public and transparent. #### Bug Bounty Program MIURO will launch a bug bounty program on Immunefi with rewards of up to $500,000. The program will cover key areas such as smart contracts, protocol logic and permission management. #### Fund Custody and Multi-Signature Management Important funds, including the Treasury, Premium Pool and MU reserves, are managed by Cayman Foundation multi-signature custody. Critical smart contract operations require multi-signature confirmation, reducing single-point risk. ### 4. Network and Anti-Cheating Mechanisms #### Task Verification Mechanism Nodes must complete real tasks, such as AI generation, audio processing and enterprise services, to receive rewards. This avoids ineffective incentives based on “online-to-mine” participation. SIG minting includes a four-layer verification mechanism to prevent fake traffic and cheating. #### Slashing Mechanism Nodes that maliciously go offline, falsify data or violate rules will be subject to penalties. Penalties may include reward deductions, reputation reduction or a mining ban. ### 5. Legal and Compliance Framework #### Entity Structure MIURO Foundation is registered in the Cayman Islands and is responsible for token issuance and protocol governance. Hardware Co. is registered in Hong Kong and is responsible for hardware production and sales. Operating entities are established locally in different regions according to regional requirements and applicable regulations. #### Regional Compliance Strategy **South Korea:** An operating entity has been established to comply with local virtual asset regulations. **European Union:** MIURO will comply with MiCA regulatory requirements. **United States:** MIURO does not sell to US retail investors and only engages qualified investors through compliant channels. **Mainland China:** The brand, physical entities and sales will not enter the Mainland China market. #### User Responsibility Users must understand and comply with the laws and regulations of their own country or region. Users are responsible for the relevant legal and tax obligations arising from activities such as mining and token trading. ### 6. User Safety Recommendations To protect their own interests, users are advised to follow these practices: * Do not disclose wallet private keys, seed phrases or device binding information to others. * Connect devices to a stable network and use a UPS, or uninterruptible power supply, when possible. * Follow official announcements and security alerts regularly, then update firmware in time. * Purchase devices and trade tokens only through official channels, including the official website and in-app links, to avoid third-party scams. * If any abnormal situation is detected, contact official support at immediately. ### Statement The above security measures and compliance arrangements are designed to protect user interests as much as possible. However, no technical system can guarantee absolute 100% security. Users should evaluate risks rationally and make participation decisions based on their own circumstances. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.miuro.ai/appendix/appendix-a-security-privacy-and-compliance-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.