bleep / Privacy
Privacy
bleep is built to be trusted with your inbox. This page says what it reads, where it keeps it, and what leaves your Mac.
The short version
- bleep has no server. There is no bleep account and no telemetry in the app.
- Your data stays on your Mac. Mail summaries, memory, reminders, settings and logs are in
~/.bleep. Google tokens and API keys are in the macOS Keychain. - The model gets only what it needs. When bleep thinks, it sends the text it needs to the model you picked, through your own Claude Code login or API key. With a local model in Ollama or LM Studio, nothing leaves your Mac.
Google data
If you connect Google, bleep asks for read access to Gmail, permission to create Gmail drafts, Google Calendar events and, if you turn it on, Google Drive. bleep reads this data on your Mac to answer you and to notice what needs you. It never sends mail, moves events or deletes anything without your tap on the exact action. It does not sell your data or use it for ads. You can disconnect Google in Settings at any time and remove access in your Google account.
Voice
The wake word is off by default. When it is on, speech to text runs on your Mac. Audio is never saved or sent anywhere.
Updates
bleep checks GitHub for a new release every few hours. That request carries no personal data. You can turn off automatic updates in Settings, Updates.
This website
This site uses Vercel Web Analytics, which counts page views without cookies. It has no ads and no third-party trackers.
Remove everything
Run brew uninstall --cask --zap bleep, or quit bleep, drag it to the Trash and delete ~/.bleep. Remove the Claude Code and Codex hooks first in Settings, Agents.
Contact
Questions or a security report: report privately on GitHub or open an issue.