The best privacy policy is having nothing to police.
Last updated 2026-09-03T00:00:00.000Z
Nothing. PlebChat has no analytics, no trackers, no cookies of ours, and no server that receives your data. The app is static files; once loaded, it runs entirely in your browser.
By its nature, using the network reveals some things to the parties you pick: your configured AI provider sees the prompts you send it; relays see your public key and event metadata; ecash mints see wallet operations (Cashu’s blind signatures prevent them linking tokens to you); media servers see the files you upload. All of these are your choice and swappable in settings.
When you generate a picture with PlebChat credits, the request passes through our paygate on its way to the vendor. Before it leaves your browser, every reference picture is re-encoded so camera and location metadata (EXIF) is stripped, and shrunk to at most 2048 pixels on its long edge; the original stays in your browser untouched. The paygate keeps a billing record for each request (cost, size, a refusal code when the vendor declined) and never stores your prompt, your reference pictures, or the result. With your own vendor key, the request goes straight from your browser to the vendor and we see nothing.
The one channel that intentionally sends us something is the feedback button. A report includes your description, app context (route, version, viewport), a redacted diagnostic log, and screenshots only if you attach them — encrypted to the developer’s key, delivered as a nostr message. Reports are sent only when you press send, and you can see everything a report contains before it goes.
The site is served by GitHub Pages, which, like any web host, sees standard request metadata (IP address, user agent) when your browser fetches the app. Their handling is governed by GitHub’s privacy statement.