Privacy

bb runs on your own machines. Your prompts, your code, and your files go to the bb server that you run, and from there to the AI provider that you choose. They do not come to us.

This policy covers three separate things. You can use the first one alone.

  1. The bb apps — the desktop app, the CLI, and the iOS app.
  2. bb connect — the optional relay at getbb.app that lets you reach your own machine from somewhere else.
  3. This website — getbb.app.

1. The bb apps

The apps talk to a bb server that you run. We do not operate that server and we do not receive its data. This includes your prompts, your agent conversations, your source code, your files, your terminal output, and your provider API keys.

The iOS app keeps this on the device:

  • Server profiles — the address of each bb server you added, and the credential that reaches it. These live in the iOS Keychain.
  • Preferences and drafts — your theme, your list order, and unsent message drafts. These live in the app’s own storage.

The iOS app sends no analytics, no telemetry, and no crash reports to us.

The app asks for the camera, the microphone, and the photo library only when you attach an image or dictate a prompt. That content goes to your bb server. It does not go to us.

2. bb connect

bb connect is optional. It gives your machine an address such as yourhandle.getbb.app, so the iOS app can reach it from a phone network. If you only use bb on your own network, you never touch it.

When you sign in to bb connect, we store:

  • Your GitHub account details: name, email address, GitHub login, and avatar URL.
  • The access tokens that keep you signed in to GitHub, and your bb sign-in sessions. A session record includes the IP address and the browser user agent that created it.
  • Your handle, and a record of each machine and server you enroll: its name, its subdomain, and a hash of its credential. We do not store the credential itself.
  • Short-lived pairing codes, and an audit log of account actions such as enrolling or revoking a machine.

What the relay can see. Traffic between the app and your machine passes through the relay while it is in flight. TLS protects it from the network, but the relay terminates that TLS, so the relay handles the content. We do not record it and we do not store it. The only thing the relay keeps is an edge cache of immutable static assets, such as the app’s own JavaScript and images. Treat the relay as a trusted intermediary rather than as end-to-end encryption, and do not use it if your threat model forbids that.

You can revoke any machine at any time from the connect dashboard. Revoking it ends its address immediately.

3. This website

The marketing pages use PostHog to measure how people find bb. Automatic event capture is off. The pages send page views, the referrer and any campaign parameters in the URL, and a small set of named events, such as a click on a download link or a copy of the install command.

If you give us your email address to follow releases, we keep it to send you those emails, and nothing else. Every email has an unsubscribe link.

What we do not do

  • We do not sell your data.
  • We do not share it with advertisers.
  • We do not read, store, or train on your prompts, your code, or your agent conversations.

Keeping and deleting data

We keep your bb connect account data until you delete the account. Sign-in sessions and pairing codes expire on their own. Write to us at the address below to delete your account, and we will remove your account record, your machines, and your handle.

Data held by the bb apps is yours. Deleting the iOS app removes its profiles, preferences, and drafts from the device.

Children

bb is a developer tool. It is not directed at children under 13, and we do not knowingly collect their data.

Changes

We will update this page when the product changes, and we will move the date at the top. bb is open source, so you can also read the history of this page in the repository.

Contact

Write to sawyer@terragonlabs.com with any question about this policy, or open an issue on GitHub.