# Security and Privacy

At Syrax, we place paramount importance on the security and privacy of our users, which is why we champion a decentralized framework for our prediction markets. This architecture eliminates the need for users to place their trust in any centralized entity or individual participant within the market ecosystem.

User assets are safeguarded within smart contracts on the blockchain, ensuring both transparency and verifiability. These contracts undergo rigorous scrutiny by independent auditors to preempt and rectify any potential security vulnerabilities, thereby fortifying the integrity of our platform.

Furthermore, the design of our system allows for complete traceability of your tokens, enabling you to monitor their movement and storage within the platform at any time. In alignment with our commitment to user privacy, the only information we require from our users is their wallet address, which is essential for facilitating payouts.

For market builders, who play a pivotal role in the ecosystem by generating and managing betting markets, a bit more information is necessary, such as an email address, to ensure effective communication. However, similar to our general user base, compensation for market builders is processed solely through their provided wallet addresses, maintaining our minimal data requirement philosophy. This approach underscores our dedication to upholding user privacy while ensuring a secure and transparent prediction market experience.

<br>


---

# 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://docs.syrax.io/syrax-market/whitepaper/how-syrax-works/security-and-privacy.md?ask=<question>
```

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.