The software collects nothing.

$ quire --sbom | jq '.components[].name'
  # 31 packages, no analytics SDK

$ sudo lsof -i -P | grep quire
  # nothing, on the default config

1. The CLI and the local server

No accounts, no licence keys, no activation, no version-check ping, no crash reporting, no usage counters. Your documents, your questions and your answers stay in the SQLite file next to your documents. The maintainers have no infrastructure capable of receiving any of it.

2. Where data can leave your machine

Three places, all of which you configure and none of which are on by default:

• A hosted model. If you set answer = "anthropic/…" or any other hosted endpoint, the selected spans and your question go to that provider under their terms. Only the retrieved spans are sent, never your whole corpus. Their retention policy is theirs, and you should read it.
• Connectors. If you index a remote source, Quire talks to that source with credentials you supplied.
• Agent outputs. If you configure an agent to post to Slack or a webhook, it posts to Slack or that webhook.

Setting offline = true makes all three a hard error where it would otherwise fall back silently, which is the setting to use when the guarantee needs to be provable instead of assumed.

3. Package registries

When you pipx install quire, PyPI sees the download: an IP address and a user agent, as with any package. That's PyPI's logging, not ours, and we don't have access to it. The same applies to Homebrew, npm and the container registry. Download counts are the only usage signal that exists, and they're public.

4. This website

Static HTML on GitHub Pages. No cookies, no analytics, no tag manager, no consent banner, because there is nothing to consent to. GitHub serves the files and keeps its own server logs, which are subject to GitHub's privacy statement.

One caveat we'd rather state than hide: the pages load Geist from Google Fonts, so your browser makes a request to fonts.gstatic.com. Self-hosting the font would remove that, and it's an open issue.

5. Community spaces

GitHub, Discord and the mailing list are third-party services with their own policies. If you file an issue, your username and what you wrote are public forever. If you join Discord, Discord's terms apply to you. We can delete things we host; we can't delete you from someone else's platform.

The mailing list is the only place we hold an email address. It's stored with a European provider, used to send that list and nothing else, never shared, and unsubscribing deletes the record instead of flagging it.

6. Security reports

If you mail security@quire.dev, we keep the thread until the issue is fixed and disclosed, then archive it for the advisory record. Tell us if you want to be credited anonymously and we'll honour that permanently.

7. GDPR, briefly

For the software, there is no controller and no processing, because there is no data collection. For the mailing list and security correspondence, the maintainers are joint controllers and the legal basis is consent, withdrawable at any time by replying. Requests to privacy@quire.dev, answered within 30 days and usually within three.

8. Changes

If this page ever changes materially, it changes in a commit with a message explaining why, and it's noted in the release notes. The git history of this file is the change log. There's no "we may update this policy from time to time" clause, because you can watch the file.

This is a demonstration site for a fictional project. The text above is illustrative and is not legal advice or an actual privacy policy.