Proof
Don't trust. Check.
How AMNESIA is built, what each part can see, and how to verify it yourself in two minutes.
The path of one message
Your browser tab
Holds the whole conversation in memory. Nothing written to disk by the site. Burn = gone.
HTTPS · the conversation so far
AMNESIA server (Vercel function)
Counts 1 message on a hashed counter. Forwards. Streams back. Never logs or stores content.
HTTPS · zdr: true, data_collection: deny
OpenRouter
Routes only to zero-retention endpoints. Does not store prompts (logging off).
inference
Model host (e.g. Mistral, DeepInfra, Bedrock)
Runs the model on your message under a zero-retention agreement and its own safety rules.
Live settings of this deployment
Model providerOpenRouter
Modelmistralai/mistral-small-3.2-24b-instruct
Zero Data Retention forced on every requestyes (provider.zdr = true)
Conversation content logged by our serverno
CoinEMMhTzFsu37rPfu5bCRaWeesKd7jxJnkUEPyVbc7pump
Free messages / day10
Holder fair-use ceiling / day300
Minimum holding1 $AMNESIA
Counter & link storagePostgres (rows expire)
Ghost link lifetimefirst open, or 24 h
Same data as JSON: /api/status
Why signing in can't touch your funds
Chatting never needs a wallet. Holders sign in to unlock unlimited messages, and the only thing AMNESIA ever asks your wallet for is to sign this text:
getamnesia.com wants you to sign in with your Solana account: 7xKX…your wallet…f9Qz Sign in to AMNESIA to show you hold $AMNESIA. This is a message, not a transaction: it cannot move funds. URI: https://getamnesia.com Version: 1 Chain ID: mainnet Nonce: 4fJ9kQ2xR7mT1vB8 Issued At: 2026-10-15T12:00:00.000Z
- On Solana, tokens move only with a signed transaction: a binary instruction list the network executes. A signed text message is not a transaction; the network has nothing to execute.
- The message names this site, your address, a one-time code (used once, valid 5 minutes) and the time. Our server checks the ed25519 signature against your public key, then reads your $AMNESIA balance with a read-only RPC call.
- The site's code has no function that builds or requests a transaction. If your wallet ever shows “Approve transaction”, a balance change, or a token approval on this site: reject it — it isn't us.
Ghost links, step by step
- Your browser generates a random AES-256 key and encrypts the question and answer (Web Crypto, AES-GCM).
- Only the ciphertext goes to our server, which returns a random 128-bit id.
- The link is /g/<id>#<key>. Browsers never send the part after # to servers, so we never see the key.
- Opening the page doesn't burn it (so X or Telegram previews can't). Tapping “Reveal” fetches and deletes the ciphertext in one database statement. A second open finds nothing.
- Unopened links are deleted after 24 hours.
Check it yourself
- Open your browser's DevTools → Application. Local storage, session storage and IndexedDB for this site are empty. The only cookies are the random device id (and the holder session if you signed in).
- DevTools → Network, send a message: one request to /api/chat with your conversation, a streamed text answer. No other domain is contacted.
- Create a ghost link: the request to /api/links contains only an unreadable blob. The key never leaves your browser.
- Sign in as a holder: your wallet shows a message to sign, with the text above. Never a transaction.