> For the complete documentation index, see [llms.txt](https://docs.code4rena.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.code4rena.com/legal/privacy-policy.md). # Privacy Policy ## Code4rena Privacy Policy and Data Practices for Personally Identifiable Information ### Collection and Use of Personal Information We collect certain personal information (PII) for specific, limited purposes: 1. To ensure compliance with OFAC (Office of Foreign Assets Control) regulations 2. To enable the submission of annual tax reports by authorized accountants ### Data Protection and Security We implement strict measures to protect your personal information: * All data is transmitted using end-to-end encryption * Information is stored in isolated data storage, separate from our main API * Access to the encryption key is extremely restricted ### Data Access and Disclosure Your personal information will only be accessed or disclosed under the following circumstances: 1. By authorized accountants (bound by Non-Disclosure Agreements) for tax reporting purposes 2. In response to a legal subpoena 3. In case of justified inquiries based on compelling evidence of grave ethical violations We do not use, share, or disclose your personal information for any other purposes. ### Your Rights and Choices If you have any questions about this privacy policy or wish to exercise your data protection rights, please contact us through the [help desk form](https://code4rena.com/help). --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.code4rena.com/legal/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.