# Privacy Policy **Last Updated:** December 11, 2025 This Privacy Policy explains how we collect, use, store, and protect information when you interact with our website and services. We value your privacy and design our systems to collect only the minimum data necessary to operate and improve our platform. By accessing or using our website, you agree to the practices described in this policy. *** ### **1. Information We Collect** #### **1.1 Information You Provide Directly** Some parts of our platform may allow you to provide information voluntarily (for example, through forms or account-related communication). Any data you submit is used only for the purpose you provided it. #### **1.2 Automatically Collected Technical Data** When you interact with our website, certain technical data is automatically collected to ensure functionality, security, and performance. This includes: * IP address (processed temporarily for routing and security) * Browser type and version * Operating system * Device information * Pages or resources requested * Referring URLs * Basic performance measurements (e.g., request timing, load time) We do **not** collect names, emails, wallet addresses, or any personal identifiers unless you explicitly provide them. *** ### **2. Cookies and Tracking Technologies** We do **not** use cookies for analytics, advertising, or cross-site tracking. If cookies are used at all, they are strictly necessary for basic site functionality and are not used to identify or track users. We do **not** use: * Google Analytics * Cloudflare Analytics or Cloudflare RUM * Advertising trackers * Cross-site tracking technologies *** ### **3. Self-Hosted RUM (Real User Monitoring) and Telemetry** We use a self-hosted RUM system to understand how our website performs and to diagnose technical issues. This system runs entirely on infrastructure we operate. #### **3.1 What RUM Collects** RUM collects technical data such as: * Pages and resources accessed * Browser and device type * Operating system * Screen resolution * Performance metrics (load times, latency, script errors) * Referring URLs * IP address (used briefly for routing and security) RUM data does **not** include names, wallet addresses, emails, or other personal identifiers. #### **3.2 How RUM Data Reaches Us** Telemetry is sent directly from your browser to servers that we operate.\ Standard internet infrastructure (such as DNS and routing providers) is used only to direct traffic and does **not** process or access telemetry content. #### **3.3 How RUM Data Is Used** We use telemetry exclusively for: * Operating and securing the website * Measuring performance * Identifying and fixing errors * Ensuring reliability * Detecting abnormal or malicious traffic RUM data is **not** used for: * Advertising * Profiling * Behavioral tracking * Cross-site tracking #### **3.4 Where RUM Data Is Stored** All telemetry is stored on servers we operate.\ We do **not** share telemetry with third-party analytics providers or data brokers. #### **3.5 Data Retention** Telemetry logs are retained only as long as needed for monitoring, debugging, and operational analysis. We minimize retention wherever possible. *** ### **4. How We Use Your Information** We use the information we collect to: * Operate and maintain our website * Ensure uptime, stability, and security * Diagnose issues and improve performance * Respond to user requests or support inquiries * Protect our systems from abuse or malicious activity We do **not** use your information for advertising or user profiling. *** ### **5. How We Protect Your Information** We implement multiple technical and organizational safeguards, including: * HTTPS encryption * Secure ingress via HAProxy * Access controls and authorization policies * Infrastructure security measures * Log minimization and limited retention Only authorized personnel may access operational telemetry. *** ### **6. Sharing of Information** We do **not** sell or share your information with advertisers, analytics providers, or external third parties. We only share information in the following circumstances: #### **6.1 Infrastructure Providers** We use standard internet infrastructure providers (such as DNS or networking services) to route traffic. These providers do **not** process or access telemetry or analytics data. #### **6.2 Legal Compliance** We may disclose information if required to comply with legal obligations or lawful requests. #### **6.3 Protecting Our Rights** We may disclose information to enforce our Terms of Service or protect the integrity and security of our platform. *** ### **7. International Data Transfers** Our servers may be located in regions outside your jurisdiction.\ Any data processed outside your region is handled in accordance with applicable privacy requirements. Because we self-host telemetry, cross-border transfers occur only as part of normal internet routing when you connect to our servers. *** ### **8. Your Rights** Depending on your location, you may have the right to: * Access information we hold about you * Request correction * Request deletion of log data where feasible * Request details about our data practices We will respond to legitimate requests in accordance with applicable laws. *** ### **9. Children’s Privacy** Our website is not directed to children under age 13 (or the equivalent required age in your jurisdiction).\ We do not knowingly collect personal information from children. *** ### **10. Changes to This Privacy Policy** We may update this Policy periodically to reflect service or legal changes.\ The updated version will always include a revised “Last Updated” date. *** ### **11. Contact Us** If you have questions or requests related to privacy, you may contact us at: [**privacy@derpbirds.io**](mailto:privacy@derpbirds.io) --- # 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://guide.derpbirds.io/derp-birds/more/privacy-policy.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.