Trust, safety, and data boundaries

Babbily is a work surface for AI-assisted tasks. You control what you type, upload, remember, connect, approve, share, and delete where controls are available. Babbily does not use your chats to train generative models by default unless you give explicit permission, and Babbily does not sell your personal information. Babbily may use account information for verification, billing, support, safety, product communications, and aggregated usage insights.

​

What Babbily can help with

Babbily can help you:

• Draft and rewrite content.
• Summarize chats, files, and connected-app context.
• Search public sources and cite them.
• Research broad topics.
• Generate images and short videos when supported.
• Use memory to personalize future replies.
• Prepare connector actions for review and approval.

​

What you should not put in Babbily

Do not enter or upload:

• Passwords.
• Verification codes.
• Private keys.
• API keys.
• Payment card numbers.
• Government identifiers.
• Raw connected-app credentials.
• Confidential data you are not allowed to process in Babbily.

​

Connector boundaries

Connectors use access you authorize in the connected app. Connected apps may limit what Babbily can see or do based on your role, app permissions, and workspace settings. Some connector actions require approval before they run. Review actions carefully when they:

• Send messages or emails.
• Update documents, tasks, tickets, or records.
• Change workspace content.
• Affect customer, billing, payment, or support data.
• Trigger automations or app workflows.

Removing connector access does not delete content inside the connected app.

​

Memory boundaries

Memory is for stable context that should help future replies. It is not for secrets. Use Settings > Memory to review your Memory Profile and remove eligible citations. You can also ask Babbily to forget something in chat. Personal workspace memory remains separate from team-workspace memory. If the team owner enables Shared team memory, useful facts from team chats can become reusable context for current members. Only put context in a team chat when the whole team is allowed to reuse it.

​

Sharing boundaries

Team sharing gives current teammates read-only access to supported team-workspace chats or saved media. You can share with specific members or everyone in the team, and access ends when a recipient leaves the team. Public share links are separate. Anyone with a public share link can view the messages plus any attachments, generated media, citations, or other content included in the shared thread. Shared links do not give viewers access to your account settings, billing, connectors, or memory controls. Public shared threads may be discoverable in Google Search Results when public search visibility is enabled. Make links private when public access is no longer appropriate.

​

Team boundaries

Team owners manage team membership, invitations, Shared team memory, billing, and owner-only controls. Team membership changes can affect plan access, team-share access, and API usage budget, but they do not delete content inside a member’s Personal workspace or connected apps.

​

Support boundaries

When contacting support, include enough context to investigate the issue, but hide sensitive details in screenshots and do not send passwords, keys, verification codes, payment card numbers, or raw credentials.