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, connectors, sharing, teams, and support.

Admin and procurement FAQ

Review team, SSO, 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.
Team plan cards may list SSO integration. Availability and setup can depend on the plan and account. Contact support if SSO is a procurement requirement.
Connector 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, Saved Prompts, 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.
Users can delete supported saved items, manage memory, disconnect apps where controls are available, and contact support for account-level deletion or data they cannot remove themselves.
Include the plan you are considering, expected number of users, billing owner email, SSO needs, 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, raw connected-app credentials, or confidential files in procurement emails or support tickets unless Babbily support specifically requests them through an approved support channel.
If your organization requires specific legal documents, security questionnaires, or vendor review forms, contact support with the request and the review deadline.