> For the complete documentation index, see [llms.txt](https://dirolprotocols-organization.gitbook.io/dirol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dirolprotocols-organization.gitbook.io/dirol/legal/privacy-policy.md). # Privacy policy ## PRIVACY POLICY *Last Updated: June 15, 2026* DIROL PTE. LTD. ("we", "us", "our", or the "Company") is committed to protecting the integrity of our software network and respecting user data parameters. This Privacy Policy ("Policy") details how we collect, process, and manage technical data and metadata when you access or interact with our web interface located at dex.dirol.io (the "Interface"). This Policy applies strictly to data processed via the visual Interface. It does not apply to the underlying autonomous Monad blockchain network or the self-executing smart contracts (the "Protocol"), which operate publicly and independently of the Company. *** #### 1. THE NON-CUSTODIAL AND ANONYMOUS NATURE OF DEFI 1.1. No Real-World Personal Information. We do not operate a centralized database that requires traditional "Know Your Customer" (KYC) onboarding. We DO NOT collect, store, or process your real-world personal identity data, such as your legal name, physical home address, government-issued identification cards, passports, phone numbers, or biometric data. Your interaction with the Interface remains primarily pseudonymous via your connected public Web3 wallet address. #### 2. CATEGORIES OF TECHNICAL DATA WE COLLECT AUTOMATICALLY 2.1. Technical Access Logs. When you access specific modules of the Interface, our web servers and performance monitors automatically save technical transaction metadata in encrypted log files. This data includes: * The precise date and time of network access; * The transmission protocol used (e.g., HTTP/1.1 or HTTP/2); * Browser fingerprints, user agent details, operating system architecture, and language configurations; * API endpoint requests and corresponding payloads. 2.2. On-Chain Information. We read and display public blockchain metadata to ensure the Interface works correctly. This includes your public cryptographic wallet address (e.g., Monad/EVM-compatible addresses), historical token balances, and public on-chain smart contract transaction hashes. #### 3. COMPLIANCE, ANTI-VPN, AND GEOGRAPHIC VERIFICATION DATA 3.1. Geo-Location and Network Verification. To maintain high security standards, prevent illicit activities, and comply with international sanctions and regulatory restrictions regarding decentralized margin trading software, we process geographic access metrics. 3.2. Integration of Compliance APIs. The Interface integrates specialized third-party geo-location APIs and forensic network security services (such as MaxMind GeoIP2 or equivalent solutions). These services analyze technical parameters, including your Internet Protocol (IP) address and Autonomous System Number (ASN). 3.3. Purpose of Processing. This analysis is executed programmatically and in real-time solely to verify that the node connecting to the Interface is not located within a Restricted Jurisdiction and is not utilizing commercial data-center VPN networks, proxy nodes, or routing systems configured to bypass geographic limitations. #### 4. COOKIES AND LOCAL STORAGE 4.1. Functional Storage. We may use functional cookies or browser local storage features to store your non-personal interface preferences (such as dark mode settings, selected language, or connected wallet type). These elements do not track your internet behavior across third-party websites. #### 5. THIRD-PARTY SERVICES AND ANALYTICS 5.1. Decentralized RPC Providers. When you submit transactions through the Interface, you connect directly to public or private Remote Procedure Call (RPC) nodes on the Monad network. The data processing practices of external RPC providers are governed by their respective privacy policies, and the Company is not responsible for their data collection. #### 6. DATA RETENTION AND EXTRACTION LIMITS 6.1. Retention Periods. Technical server log files and network metadata are retained only as long as necessary to fulfill security auditing, technical troubleshooting, and automated compliance verification goals, typically not exceeding 30 to 90 days, after which they are permanently deleted or fully anonymized. 6.2. On-Chain Immutability. Please note that public blockchain data (wallet addresses, transactions, liquidations) is immutable and recorded permanently on the public Monad blockchain. The Company has no technical ability to delete, modify, or censor data embedded directly within the blockchain network. #### 7. DATA SECURITY MEASURES 7.1. Protection Architecture. We implement standard, industry-recognized technical and organizational security measures to protect server log parameters against unauthorized access, leaks, destruction, or alterations. However, no internet-based transmission system or decentralized cloud network is 100% secure. #### 8. USER RIGHTS AND COMPLIANCE ENQUIRIES 8.1. Pseudonymous Parameters. Because we do not store real-world personal identification records, we cannot verify requests to "delete or modify" real-world identity profiles. For any technical enquiries regarding Interface data processing, you may consult our open-source documentation repositories. #### 9. AMENDMENTS TO THIS POLICY 9.1. Right to Update. The Company reserves the right to modify this Policy at any time. Any changes will become effective immediately upon being posted on this page. Your continued interaction with the Interface indicates your acceptance of the updated privacy architecture.