> ## Documentation Index
> Fetch the complete documentation index at: https://docs.babbily.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Security and procurement

> Prepare for a Babbily security, privacy, SSO, billing, and procurement review.

Use this page when your organization needs to review Babbily before buying, expanding, or approving wider usage.

<Warning>
  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.
</Warning>

## What to review first

<CardGroup cols={2}>
  <Card title="Privacy and data" icon="shield-check" href="/features/privacy-and-data">
    Understand practical ways to control what you share with Babbily.
  </Card>

  <Card title="Trust and data boundaries" icon="shield" href="/features/trust-safety-and-data-boundaries">
    Review safe handling for chats, files, memory, connectors, sharing, teams, and support.
  </Card>

  <Card title="Admin and procurement FAQ" icon="briefcase-business" href="/features/admin-and-procurement-faq">
    Review team, SSO, support, privacy, and procurement questions.
  </Card>

  <Card title="Data export and deletion" icon="download" href="/features/data-export-and-deletion">
    Understand what you can copy, download, delete, or request through support.
  </Card>
</CardGroup>

## Common procurement questions

<AccordionGroup>
  <Accordion title="Does Babbily train models on my chats by default?">
    Babbily's privacy settings state that Babbily does not use your chats to train generative models by default unless you give explicit permission.
  </Accordion>

  <Accordion title="Can we use SSO?">
    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.
  </Accordion>

  <Accordion title="Can admins control connected apps?">
    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.
  </Accordion>

  <Accordion title="How are Personal and team contexts separated?">
    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.
  </Accordion>

  <Accordion title="Is personal memory shared with a team?">
    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.
  </Accordion>

  <Accordion title="Can users delete data?">
    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.
  </Accordion>

  <Accordion title="What support information should we prepare?">
    Include the plan you are considering, expected number of users, billing owner email, SSO needs, privacy questions, support expectations, and required timeline.
  </Accordion>
</AccordionGroup>

## Information to collect before contacting support

| Area         | Helpful details                                                                                                                                     |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Organization | Company name, billing contact, expected user count, and rollout timeline.                                                                           |
| Access       | Whether you need SSO, team ownership, user management, workspace guidance, or procurement approval.                                                 |
| Data         | Approved use cases, restricted data types, Shared team memory policy, team-sharing expectations, connector expectations, and deletion requirements. |
| Billing      | Preferred plan, team size, purchase timing, and invoice or subscription needs.                                                                      |
| Support      | Required support level, onboarding needs, and internal launch date.                                                                                 |

## 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.

<Tip>
  If your organization requires specific legal documents, security questionnaires, or vendor review forms, contact support with the request and the review deadline.
</Tip>