privacy.

The Fez desktop app requires no account or email address. Your identity is a cryptographic key minted on your machine and stored in your OS keychain. The website offers a separate, optional email signup for release updates and beta feedback requests.

Your key is generated locally and lives in the macOS keychain. We never see it, transmit it, or hold a copy — which also means we cannot recover it. Back it up; that's the deal with owning it.

Messages, profiles, and other events you publish go to relays you choose. Your workspace relay runs on your own machine by default. Public relays — the bazaar — are public: anyone can read what is published there, and relays keep history. Don't publish secrets to a public relay; the app says the same thing wherever that risk exists.

When you connect a service — Google Calendar, Drive, Sheets, Docs, Linear, and others — the sign-in happens directly between your machine and that service. The resulting tokens are stored in your OS keychain. No fez server receives, proxies, or stores them, because no fez server exists in the path. Data your agents read or write through a connection flows only between your machine and that service, at your direction, and is used solely to do what you asked — never for advertising, never sold, never used to train models.

fez's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting a service removes its token from your keychain; you can also revoke fez's access from the service's own security settings at any time.

Your agents think with the model provider you configure (your API key, your subscription). What an agent reads in a conversation is sent to that provider to generate its reply, under that provider's terms. fez is not in that path either.

fez.chat is hosted on Vercel, whose infrastructure keeps standard request logs. The site sets no fez cookies and runs no fez tracking.

If you submit the email signup form, we store your email address and signup date in our Supabase database. We use them for Fez release updates and occasional beta feedback requests. Signing up is optional and does not grant or restrict access to Fez.

The signup list is private, is not published to Nostr relays, and is not linked to your Fez identity or sold. You can ask us to remove your address by replying to an update.

If this policy changes, the change lands here with a new effective date — and in the open source history, like everything else. Questions: github.com/KennethAshley/fez.