# Ghostline — full notes for agents > Anonymous, encrypted, ephemeral chat. No accounts or sign-up. This file expands https://ghostline.chat/llms.txt. It describes what the official web app actually does as of the source in this project. It is documentation, not a public API. ## Product Ghostline is a free web app at https://ghostline.chat. Chat happens in temporary rooms called lines. Anyone can create or join a line without an email, phone number, or account. A per-line session is created automatically when you start or join. There is no public HTTP API and no MCP server. The supported way for a human or an agent to participate is to open the web app in a browser. ## How a line URL works Creating a line: open https://ghostline.chat, choose Start a chat, set options, and create the line. The app navigates to a ghostlink and offers a share sheet. Ghostlink format: - https://ghostline.chat/line/{lineId}#{passcode} - Optional invite nonce: https://ghostline.chat/line/{lineId}?n={inviteNonce}#{passcode} `{lineId}` is a UUID. `{passcode}` is chosen by the host or generated by the app (8 characters) if the host leaves it blank. The passcode is placed in the URL fragment. Browsers do not send the fragment to the server. The official web client reads it, then strips it from the address bar so it is less likely to linger in history. `?n={inviteNonce}` is an invite token issued when the line is created. The official client uses it to join, then removes it from the URL. Links without a nonce can still try an open join. Joining: open the ghostlink. On a first visit the app asks you to accept the terms, then enters the room. If the host enabled join approval, you wait until they approve. If the line is locked, non-hosts cannot send. If the line is missing, expired, wiped, or the token is rejected, the app shows that the line is not available. Older bookmarks under `/chat/{lineId}`, `/voice/{lineId}`, and `/active-line/{lineId}` redirect to `/line/{lineId}`. ## Encryption (official web client) Do not treat the following as a supported integration API. It is how the official client protects message bodies. Text messages: - Algorithm: AES-256-GCM, 256-bit key, 12-byte random IV per message. - Key derivation: PBKDF2 with SHA-256, 100,000 iterations, salt = UTF-8 bytes of the line ID, password = the line passcode. - Stored payload format: `ivBase64:cipherBase64` (two Base64 strings separated by a colon). This is not a single Base64 blob of IV+ciphertext. - The derived CryptoKey is non-extractable and kept only in memory on the device. Voice notes and file drops: - File bytes are encrypted with the same key. The binary wire format is raw bytes: 12-byte IV followed immediately by the AES-GCM ciphertext. - The encrypted blob is uploaded to object storage. The chat message itself is a short encrypted text pointer such as `[voice:{filename}]` or `[file:{filename}:{originalName}]`. - The official client rejects file drops larger than 25 MB. Older messages may have been encrypted with a legacy static salt (`ghostline-v1-salt`). The official client tries the per-line salt first, then falls back to that legacy salt when decrypting. What the server holds: - New lines write `passcode` as null in the database. The encryption key is not stored. - The official web client currently also sends the passcode to the join endpoint so older lines that still have a server-side passcode can be checked. For new lines that value is not stored or compared. A server that sees a join request could in principle observe that passcode. This file does not claim a stronger guarantee than the code provides. - Message rows store the ciphertext (or an encrypted pointer to an encrypted blob), not plaintext. ## Ephemerality and limits These caps are enforced by the server. The create form may still show longer fields; values above the caps are rejected. - Line duration: 1 second to 7 days (604,800 seconds). When the line expires or the host ends it, stored messages are deleted. - Optional per-message burn timer: 0 to 24 hours (86,400 seconds). 0 means no per-message timer; messages last until the line ends or is wiped. - The host can wipe messages or end the line early. - There is no message recovery after erase or expiry. - Loaded history in the official client is capped at 2,000 messages per line. ## Accounts, identity, and sessions - No signup. Optional display name is stored locally on the device and can be left blank (anonymous). - Joining or creating a line issues a session for that line (about 24 hours, refreshable while the line is open). That is not an account. - Device-local settings (display name, saved lines, word filter, and similar) stay on the device. ## Honest limits - Infrastructure providers (Vercel, Supabase) keep standard access logs, including IP addresses and timestamps, under their own policies. - Screenshots and device-level recording cannot be prevented. - Ghostline does not claim anonymity against a serious investigation. For network-level anonymity, use a VPN or Tor. - There is no public programmatic API. Direct use of backend tables or keys is unsupported. ## Links - Short index: https://ghostline.chat/llms.txt - Manifest: https://ghostline.chat/.well-known/agent.json - App: https://ghostline.chat/ - Wiki: https://ghostline.chat/wiki - Privacy: https://ghostline.chat/privacy - Terms: https://ghostline.chat/terms - Contact: ghostlineops@gmail.com