> For the complete documentation index, see [llms.txt](https://docs.snake-os.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snake-os.com/legal/privacy.md).

# Privacy

Snake OS is pseudonymous. We treat your wallet address as your identity and minimize data collection elsewhere.

## What We Collect

* **Wallet address** (you provide it)
* **Wallet signature** on the auth message (for ownership verification)
* **Username + selected cosmetics** (you choose them)
* **Gameplay data** (scores, match history, achievements — generated by you playing)
* **Chat messages** (you post them)
* **Friend connections** (you initiate them)
* **TOS acceptance** (version + timestamp)
* **Aggregate IP-based rate-limit counters** (transient, in-memory, not linked to wallet identity in any persistent store)

## What We Don't Collect

* Email addresses
* Phone numbers
* Real-world identity (KYC)
* Persistent IP-to-wallet mappings
* Wallet activity outside Snake OS interactions
* Browser fingerprints beyond what's needed for session continuity

## How We Use the Data

* **Wallet address** → identifies your account
* **Signature** → verifies you own the wallet
* **Gameplay data** → leaderboards, friends, achievements
* **Chat** → moderation + spam prevention (rate limits)
* **Rate-limit counters** → preventing abuse

## What We Don't Sell or Share

We do not sell any user data. We do not share user data with third parties for marketing. The only third-party services that touch user data are:

* **Solana mainnet** (your TX signatures, public anyway)
* **Helius/Solana RPCs** (read-only balance lookups, public anyway)
* **Supabase** (our database provider — your data lives in our DB, not shared)
* **Cloudflare** (our hosting + edge) — standard request logging

## Cookies & Local Storage

* **sessionStorage** stores your signed wallet auth (1-hour cache)
* **localStorage** stores UI preferences (sound, theme, last-active app)
* **No tracking cookies**, no third-party analytics during beta
* **No Google Analytics**, no Meta pixel, no Hotjar

## Data Retention

* **Account data** kept while your account exists
* **Chat messages** kept for 90 days, then archived
* **TX signatures** are immutable on-chain (we can't delete them; nobody can)
* **Achievement claims** kept permanently

## Account Deletion (Post-Launch Feature)

A self-serve account delete will wipe:

* Profile (username, cosmetic equips, friends, chat history)
* Cached signatures
* Rate-limit counters

It does NOT delete:

* On-chain TX history (public, immutable)
* `market_purchases` (we keep purchase records for accounting; you can request anonymization)

## Compliance Notes

* We are not subject to GDPR data-deletion requests for on-chain data (it's public + immutable)
* We will honor data-export requests for your profile data — report it in the support topic on Telegram

## Contact

Privacy questions → post on X ([@SnakeOS\_SOL](https://x.com/SnakeOS_SOL)) or email us via [Contact](/legal/contact.md).


---

# 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://docs.snake-os.com/legal/privacy.md?ask=<question>&goal=<endgoal>
```

`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.