# Contact ## For Users * **Telegram (primary support):** [t.me/snakeOS\_sol](https://t.me/snakeOS_sol) — use the **support topic** to report bugs, refund issues, or anything else * **X:** [@SnakeOS\_SOL](https://x.com/SnakeOS_SOL) — announcements + community * **In-app:** HELP screen → contact link ## For Beta Testers (OGs) You have a direct line to the founder via our Telegram support topic. Don't hesitate — your feedback is what makes the public launch good. ## For Security Reports Report it in the support topic on Telegram with the word "security" in the message. Responsible disclosure of vulnerabilities = bug bounty rewards (amount based on severity). ## For Press / Partnerships / KOL Slots Report it in the support topic on Telegram. Be specific about what you want — vague "partnership" DMs get deprioritized. We're particularly interested in: * Solana ecosystem cross-promotions * Founding-KOL slots for genuine Solana CT accounts who actually play * Media coverage of fair-launch mechanics ## For Anything Treasury-Related If you suspect a payout / refund issue: * Include your wallet address * Include the match ID or TX signature * We can verify on-chain quickly ## What We Will NOT Do * ❌ DM you first asking for your seed phrase (we never need it) * ❌ Promise pre-launch allocations of tokens in private (fair launch, no presale, ever) * ❌ Send you "verification" links to a fake snake-os.com * ❌ Charge you for support Anyone claiming to be Snake OS staff doing any of the above is impersonating us. Report and block. --- # 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.snake-os.com/legal/contact.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.