Skip to main content
Use this page when your organization needs to review Babbily before buying, expanding, or approving wider usage.
This page summarizes customer-facing product expectations. It is not a legal agreement, security certification, or replacement for Babbily’s current Terms, Privacy Policy, or approved procurement materials.

What to review first

Privacy and data

Understand practical ways to control what you share with Babbily.

Trust and data boundaries

Review safe handling for chats, files, memory, plugins, sharing, teams, and support.

Admin and procurement FAQ

Review team, support, privacy, and procurement questions.

Data export and deletion

Understand what you can copy, download, delete, or request through support.

Common procurement questions

Babbily’s privacy settings state that Babbily does not use your chats to train generative models by default unless you give explicit permission.
No. Babbily doesn’t currently offer single sign-on (SSO). Each team member signs in to their own Babbily account with an email address and password, a supported social sign-in option, or a passkey, then joins the team by accepting an invitation sent to their email address. If your organization requires SSO, contact support before you buy.
Plugin access depends on the account that authorizes the connected app and the permissions available in that app. Workspace admins should also manage app access from the connected app’s own admin settings.
Personal and team work appear in distinct workspaces. Chats, Library items, and memory stay with the workspace where they were created. Team sharing is membership-gated, while public share links use separate visibility controls.
No. A personal Memory Profile remains separate. A team owner can enable Shared team memory for team-workspace context, so organizations should define approved team-wide data before turning it on.
Babbily uses error monitoring to find and fix problems. Before a report leaves Babbily, it is filtered to remove:
  • Cookies or sign-in tokens.
  • Request headers or bodies, including the messages you send.
  • Invitation or sign-in tokens in links.
  • API keys.
  • AI prompts and responses.
  • Chat, artifact, and file titles.
Filtering is not a guarantee. Every report includes the error message, and an error message can occasionally quote text that was on the page, such as part of a message or a title. Filtering also recognizes only common formats, so it can’t catch everything.Reports can also include the page address with sensitive values removed, browser and device details, and network details such as your IP address. Keep passwords, keys, and other secrets out of chats and titles.
Babbily keeps users signed in through brief connection problems and signs them out automatically only when a session has ended, an older session can’t be upgraded after a security update, or a sign-in didn’t finish. Choosing Log out clears that account’s data saved in the browser, such as Temporary Chat state and the selected model, and tries to end the user’s Babbily sessions on their other devices. Babbily doesn’t confirm the other devices on screen, and one can occasionally stay signed in, for example during a temporary service problem. To be sure, users should log out on each device too, and contact support about a device they can’t reach. See Log out and switch accounts.Team invitations don’t expire, so owners should cancel invitations they no longer need. When an invitee opens an invitation link while signed out, Babbily asks for the email address the invitation was sent to before continuing.
Users can delete chats and supported saved items, manage memory, and disconnect apps where controls are available. Account deletion isn’t self-serve: users request it through support by selecting Contact support next to Delete account in Settings > Account. Support can also help with data users can’t remove themselves. See Data export and deletion.
Include the plan you are considering, expected number of users, billing owner email, privacy questions, support expectations, and required timeline.

Information to collect before contacting support

Sensitive information boundaries

Do not include passwords, verification codes, API keys, private keys, payment card numbers, government identifiers, or raw connected-app credentials in procurement emails, support tickets, chats, or chat and file titles. For other confidential files, share them only when support requests them through an approved channel and your organization permits it.
If your organization requires specific legal documents, security questionnaires, or vendor review forms, contact support with the request and the review deadline.
Last modified on October 28, 2026