Privacy

bcat is built privacy-first. This page explains what data the chat.bcat.app surface actually collects and stores. The brodycat.com marketing site you are reading right now sets no cookies, runs no analytics, and loads no third-party scripts.

What chat.bcat.app stores

• Conversations. When you sign in with Google, your messages and bcat's replies are stored in a SQLite database on the Aegyrix VPS so you can resume conversations across sessions.
• Email + Google subject ID. Used to identify your account. Nothing else from Google is requested.
• Self-learned patterns. When bcat extracts a high-confidence reasoning pattern from a response, it saves an abstract description of the pattern (not the conversation text). This helps it answer future prompts better. You can opt out from the chat settings.

What bcat does not do

• No third-party analytics, no ad networks, no fingerprinting.
• No telemetry pings. The server logs only HTTP method + path + status (no message bodies).
• No model-provider call-outs. Inference runs on the same VPS via Ollama; messages do not leave the machine.

Self-host it

The strongest privacy guarantee is to run bcat yourself. The full source is at github.com/aegyrix/bcat.app — one VPS, one Ollama install, one deploy/deploy-vps.sh.

Contact

Questions or a deletion request: privacy@aegyrix.com.