# Security measures The Russian Roulette team prioritizes the security of player funds and in-game assets. Here are some key security measures in place: ### **Unbreachable User Wallet Protection** User wallet private keys are never stored within the game's database. Instead, they are encrypted using AES-256, a robust industry-standard encryption method. Even if someone were to gain unauthorized access to the database, they would be unable to decrypt the private keys and steal user funds. ### **Smart Contract Audits** The underlying smart contracts that govern the game's logic are rigorously audited by independent security experts to identify and address any potential vulnerabilities. ### **Continuous Monitoring** The development team actively monitors the platform for any suspicious activity, further safeguarding the integrity of the game. The provably fair algorithms, robust security measures like AES-256 encryption, and continuous monitoring employed by Russian Roulette help create a secure environment for players to enjoy the thrill of the virtual game. --- # 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://russian-roulette.gitbook.io/russian-roulette-game/security-and-fairness/security-measures.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.