Skip to content

Privacy Policy

Privacy Policy

This website does not collect your personal information. Below is what the site and the software each come into contact with.

Last updated: October 7, 2026

1. This website

This is a purely static site: no server-side database, no cookies of its own, and no advertising or third-party fonts. Cloudflare, which hosts the site, adds its Web Analytics script to each page to count visits and page load times; it sets no cookies. The data on the account pages is read by your browser directly from the sync service; see section 3.

  • Your language and appearance preferences are stored in your browser's localStorage (keys quetzal.lang and quetzal.theme), only on your device, and can be cleared in the browser at any time.
  • The download page requests release information and packages from this site in your browser; this site does not record who you are and sets no cookies. When this site's release endpoint is unreachable, your browser reads GitHub's public API (api.github.com) directly instead and caches the result in the browser session for 10 minutes. The star count and latest version on the home page also come straight from GitHub's public API in your browser, cached the same way; GitHub sees your IP address when this happens.
  • The site is hosted on Cloudflare. As the hosting and network provider, Cloudflare may process connection logs (such as IP addresses) under its own privacy policy; this project does not read or keep those logs.
  • The typeface (Inter) is self-hosted; nothing is requested from third parties.

2. The Quetzal software

All of Quetzal's runtime data stays on your device (the QUETZAL_HOME directory; on Windows, %LOCALAPPDATA%\Quetzal\home): configuration, conversations, timeline, audit log, vault and the local soul directory. Apart from a sync service you choose to use (see section 3, which does not receive any of this either), the author runs no server that receives any of it.

  • Model providers: whichever provider you configure receives the content of conversations and introspection, under that provider's privacy policy. API keys are encrypted on the device.
  • Soul repository (optional): personality and memory sync to a private git repository you choose, held by your git host.
  • Feishu (optional): once connected, messages pass through the Feishu platform under Feishu's privacy policy.
  • Device capabilities: camera, microphone, location and screen control go to an independent review model by default, or can be set to ask you every time; captured content is used on the device only, according to your permission settings.
  • Secret passing: passwords and tokens handed to the agent through pass_secret are stored only in the local vault and never enter the conversation or the model context.
  • Multiple bodies (optional): conversations, sessions, timeline and settings (including model keys) travel directly between your bodies, end-to-end encrypted, only to bodies registered in your soul repository, and are not stored on any server.

3. Sync service (optional)

Signing in, creating the soul repository automatically and linking several bodies all go through a sync service. The author of this project personally runs one that is open to everyone, and the app uses it by default; you can also host your own from sync/ in the source code, or not sign in at all. When you use the sync service run by this project:

  • Sign-in: with a Causally account (id.causally.xyz, the shared account service run by Causally). The account service keeps your email, your sign-in methods and sign-in records. At sign-in the sync service reads the account id, username, display name and email from the account service once, and keeps none of its tokens. When you permanently delete your account there, the account service notifies the sync service, which then deletes your account and the agents and devices registered under it.
  • GitHub app: the first time a soul repository is created, GitHub asks you to install the Quetzal app and choose which repositories it may manage. Its permission is write access to Administration on those repositories: under GitHub's rules it can create repositories, add deploy keys and change repository settings, including deleting those repositories; it cannot read the files inside. Quetzal uses it only to create the repository and add deploy keys. The sync service does not keep the app's private key and holds no credential that can touch your repositories day to day; only after you approve a body does it use a short-lived token GitHub issues on the spot to create the repository or add that body's public key, then revokes it at once. You can uninstall the app any time under Settings → Applications on GitHub; deploy keys already added keep working.
  • What is stored: your account; the agents you bind (name, id and soul repository name); each body's name, kind, software version, node public key and last-seen time; sign-in sessions, console sign-ins (which body, when signed in and last used) and body tokens as hashes only; binding codes expire after 15 minutes.
  • Account pages: sign-in, account management and device approval live on this site (quetzal.plutokeating.beer/account), and your browser reads the data directly from the sync service; your sign-in is kept in a cookie of the sync service (used only for sign-in, valid for 30 days). This site sets no cookies of its own and keeps no account data.
  • What is not stored: IP addresses and network endpoints (used only while a body is online to set up connections, never written to disk or logs), conversations, memory, personality, model keys. Traffic relayed through the server when no direct connection is possible is end-to-end encrypted and invisible to the server.
  • Deletion: on this site's account page (quetzal.plutokeating.beer/account) you can unbind a body, delete an agent or delete the whole account at any time, effective immediately.
  • The server and network providers hosting the sync service may process connection logs under their own policies; this project does not read or keep those logs.

4. Minors

This website and software are not directed at children under 16, and we do not knowingly collect their information.

    5. Changes

    Updates to this policy take effect when published on this page, with the date shown at the top.

      6. Contact

      Privacy questions go through GitHub Issues.