> For the complete documentation index, see [llms.txt](https://seat-airlines.gitbook.io/seat-airlines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seat-airlines.gitbook.io/seat-airlines-docs/safety/wallet-safety.md). # Wallet safety Exactly what Seat Airlines asks your wallet for — and what it never will. ## Seat Airlines never asks for a transaction Nothing on the site sends, swaps, approves or spends anything. Connecting a wallet shares your **public address** and nothing else, and every signature the site asks for is a **plain-text message** you can read in full in your wallet before you approve it. {% hint style="danger" %} If a page claiming to be Seat Airlines asks you to **approve a transaction**, to sign something you cannot read, or for your **seed phrase** or **private key** — stop and reject it. That is not Seat Airlines, which never asks for any of them. {% endhint %} ## The only three messages you will be asked to sign **1. Putting an advert on your seat** — every time you publish one: ``` SEAT AIRLINES Publish this advert on my seat. wallet: image: sha256: issued: ``` **2. Taking your advert down** — when you press **Remove**: ``` SEAT AIRLINES Take the advert off my seat. wallet: advert: issued: ``` **3. Signing in to the cabin directory** — once a day at most: ``` SEAT AIRLINES Sign in to the cabin directory. This lets you publish your card, read your section, and send and receive introductions for one day. It authorises no transaction. wallet: issued: ``` All three are checked by the server, and all three expire: a signature more than five minutes old is refused. A directory sign-in can be used **once** — a copy of it cannot open a second session. An advert signature covers **one exact image**, so it cannot be reused to put up a different picture, and a takedown names **one exact advert**, so it cannot take down one you put up later. ## Check you are in the right place * The site is **seat-airlines.space**. * The token's contract address is on the **CA** strip at the top of the site. Compare the **whole** address before you buy — see [The token](/seat-airlines-docs/getting-started/the-token.md). ## What is public * **Your seat, rank, address and balance.** Balances are public on Solana, and the wall shows them for every seated holder. * **Your advert**, with its description and link, for everyone. * **Your card's name and role**, for every holder signed in to the directory, and **its contact details** for your own section only — see [Your seat is which room you are in](/seat-airlines-docs/section-network/how-far-you-can-see.md). ## What is stored, and where **On the Seat Airlines server** (a Cloudflare Worker): * your published adverts, and their pictures, which stay in storage after you take an advert down until you ask for them to be deleted; * your card and the messages you send; * your directory sessions, each stored only as a one-way fingerprint (SHA-256), so a copy of the session table cannot be used to get into anybody's account; * your game runs for 24 hours, with a keyed hash of your IP address that caps how many flights one connection can start in an hour; * your best score and every score you post; * the share picture or seat card for a post on X, for 90 days; * if you connect X, your encrypted X token, your X username and the times of your recent posts; * for one minute, your IP address as a count in the rate limiter on balance lookups and email-wallet requests; * the operator's private notebook, which only the operator's wallet can open, and which can mention what was said in a cabin room the operator can see. The [Privacy Policy](https://seat-airlines.space/privacy/) has the full list, how long each is kept, and how to ask for any of it to be shown to you or deleted. **In your browser:** | Stored | For | How long | | ---------------------- | --------------------------------------------------------------- | ---------------------------------------------------------- | | Your directory session | Staying signed in to the directory | 24 hours, or until you press **Sign out of the directory** | | Adverts saved locally | Kept on this device when the advert server could not be reached | Until you take them down | | The token's address | Clearing the two above when the token changes | Until the next change | {% hint style="warning" %} Links in adverts and on cards are published by other holders. Only `http://` and `https://` links are accepted, but treat them like any link from a stranger. {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://seat-airlines.gitbook.io/seat-airlines-docs/safety/wallet-safety.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.