Data handling
Last updated
Biddle answers your team from Slack, GitHub and the tools you connect. This page says exactly what it touches. Biddle gives the same answers when you ask it in Slack.
What Biddle reads
- GitHub, through a GitHub App with read-only permissions: contents, pull requests, issues, checks, actions, deployments and metadata. It never comments on pull requests or writes code.
- Slack: only the channels Biddle is invited to, plus messages sent to Biddle itself (a DM, an @mention, a reply in its thread).
- Tools a workspace chooses to connect, which Biddle only reads from: Linear, Notion, Figma, Google Drive, Google Analytics, Google Search Console, Meta Ads, Google Ads, PostHog, Sentry, Stripe, Ramp (company spend), Intercom and Vercel (deploy events), and any read-only custom connector (an MCP server) an admin adds.
- Gmail only for the person who connects their own, and only for that person: their mail is read in their own DM with Biddle and their own morning note.
What Biddle never reads
- DMs and group DMs between people.
- Other people's email.
- Images and files, unless someone attaches them to a conversation with Biddle.
What Biddle keeps, and for how long
- Raw events (Slack messages, GitHub activity, connector updates): 90 days.
- The team record it derives from them (workstreams, decisions, open items, each tied to the message or pull request it came from): until the workspace removes Biddle.
- Notes about you, from your own feedback (what you said an answer got wrong) and your choices: read only when Biddle answers you or writes your note. You can see, edit and delete them on the What Biddle knows page.
- Email follow-ups found in your own mail: 14 days.
- Engagement: dates and counts of when you open a DM, open a link Biddle sent or press a button. Never message content.
- Biddle's own Slack posts: where each one is and the buttons it offered (never the message text), and what was asked of a post's buttons in a reply: 90 days.
- Live pages: the page's saved layout (title, text, and which metrics to show over which time window), not the numbers. The figures are read fresh each time someone opens the page, under that person's own access. Earlier versions of the layout are kept so a change can be undone.
- Pages and apps you ask Biddle to build: the page's definition, the app's source code and its versions, and whatever people enter into an app, until the page or app is deleted. A deleted page or app, and the data entered into it, is gone 30 days later. You can export an app's data and code at any time from its page.
- Error reports from an app (the error message and the place in the code it happened; never what you typed): 30 days.
- Liouville Labs staff can view what Biddle stored for a workspace (its connections, the messages it sent with the message before and after each, how it reached an answer, and its record, notes and schedules) to support that workspace, debug Biddle and check the quality of its work. Each view is logged with who opened it, the workspace and when. Staff never see content from anyone's Gmail, DMs between people, or access tokens. Google Analytics and Search Console numbers are visible to staff only as far as they appear in what Biddle wrote.
What is sent to AI models
- Model calls go through Anthropic's API, under Anthropic's commercial terms.
- When Biddle runs code for an answer (an exact sum over many rows, a table or a file), the code runs in Anthropic's code execution service, in a fresh container with no network access. Only the team's activity, metrics and revenue figures enter it, read with the same access checks as the person asking; never credentials or mail. This service is not covered by zero data retention: Anthropic keeps what passes through it for up to 30 days.
- Search embeddings go through Voyage AI, with training on your data turned off.
- When an answer needs the public web (a competitor's pricing page, docs, news, a link someone pasted), only the search query and the page addresses go to Anthropic's web search and web fetch tools, nothing else of the conversation. The model writes the query for that question, so it can contain words from the question.
- An answer sends the model only what the person asking may see: the channels they are in and the tools connected for them.
- When you ask Biddle to build or change a page or an app, your request, the current definition or source code, and any error reports you ask it to fix go to the model. The data an app shows is read from Biddle when you open it and is not sent to a model. What people enter into an app is never sent to a model unless someone asks Biddle a question about it, and then only what that person may see.
How to delete it
- Your own notes and preferences: delete them on the What Biddle knows page; Biddle stops using them at once.
- Everything: remove Biddle from the Slack workspace. Biddle deletes everything it stored for the workspace within 30 days (7 days after the uninstall by default, so a reinstall can undo it).
Why Biddle
- Biddle is an AI teammate for product teams: it keeps one accurate record of what the team decided and shipped, from Slack and GitHub, so nobody has to maintain it.
- Every line it writes is tied to the message or pull request it came from, and a correction from a teammate updates the record for everyone.
What stays private
- Biddle's instructions to the model and the internals of its tools are not public. The principles and the data handling above are.
The legal terms are in the Privacy Policy.