# Data Processing and Security Data handling and security in beta prioritize simplicity and trust, balancing on-chain transparency with off-chain efficiency while adhering to 2025 regulatory standards like GDPR compliance for blockchain. * **Data Management**: On-chain data (e.g., $LUMI transactions, NFT ownership) is stored on BASE for immutability. Off-chain data, like Lumi’s sentiment analysis, is processed on centralized servers (e.g., AWS) in beta, with plans for decentralized storage (e.g., IPFS) in future releases. Basic oracles (e.g., Chainlink CCIP) fetch external data for Tenna’s analytics, ensuring verifiable inputs. * **Security Measures**: Agent communications use basic HTTPS encryption, with DID-based authentication for access control. Smart contracts undergo pre-launch audits, with a bug bounty program to address vulnerabilities. User privacy is protected via pseudonymized identifiers, and Tenna’s anomaly detection flags suspicious activity (e.g., unusual transaction patterns). In 2025, with Web3 hacks costing over $2 billion in Q1, these measures ensure a secure beta foundation, with plans for zk-proofs and decentralized key management post-beta. --- # Agent Instructions: 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: ``` GET https://lpc-ai-lumi.gitbook.io/lpc_ai_lumi/technical-implementation/data-processing-and-security.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.