> For the complete documentation index, see [llms.txt](https://captain-tsubasa-rivals.gitbook.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captain-tsubasa-rivals.gitbook.io/en/security.md). # Security #### Private Key Management of Privileged Accounts Private keys of privileged accounts are distributed among the three companies using MPC (Multi-Party Computation) and carefully managed. Private keys will never be exposed to third parties or accessed by unauthorized users. \ \ Additionally, since it is impossible to use the private key to request an arbitrary transaction, the CAPTAIN TSUBASA -RIVALS- operations team is not able to control funds. #### Game Program Management The private keys for the privileged accounts above could only be used by request from the game program. The source code of the game program can only be updated by the approval of both companies participating in the management, reducing centralized risk. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://captain-tsubasa-rivals.gitbook.io/en/security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.