1. Scope of Data Collection
We adhere to the principle of data minimization. When you use the Cross-Chain Bridge, we may collect:
- Public On-Chain Data: Your wallet address, transaction hash, token balance, and transaction timestamp.
- RPC Log Data: To maintain network security, our RPC nodes may temporarily log request metadata (such as IP address, device type) to prevent DDoS attacks and abuse.
- Authentication Credentials: Only ME ID verification information stored in encrypted form and Zero-Knowledge Proofs (ZK Proofs) required for on-chain verification.
2. How We Use Data
- Providing Services: To process your cross-chain requests and ensure the validity of proof credentials.
- Security and Compliance: To utilize services from security partners to scan on-chain data for identifying and blocking illicit fund inflows, fulfilling AML obligations.
- Responsive Compliance Verification: Only upon triggering specific compliance events, the system will process the new ZK Proof submitted by you to verify whether you are on a sanctions list.
3. Data Sharing and Disclosure
- Third-Party Service Providers: We may share non-personally identifiable on-chain data with providers offering node hosting and security scanning services.
- Legal Requirements: If we receive mandatory legal orders from competent judicial authorities, or to enforce our Terms of Service, we may be required to cooperate in disclosing specific on-chain interaction records. As we cannot decrypt your identity information, we are unable to provide your plaintext identity data and can only provide on-chain association data.
4. Data Security
The identity information you submit when minting your ME ID is stored after being encrypted by your public key. Only you, holding the private key, can decrypt this data. We employ industry-standard security measures to protect server data but cannot guarantee absolute security.