Is team chat content used to train models?

No — customer data is not used to train the Bee base model. The commitment is contractual, in the Terms of Service and DPA.

How is chat data encrypted?

TLS 1.3 in transit and AES-256-GCM at rest under per-tenant keys, with customer-managed keys available on Hive and above.

Can conversations be kept in a specific region?

Hive-plan and above customers can request region-pinned processing (EU, US, or Singapore); Enclave deployments keep everything inside your own environment.

What happens to our data if we leave?

The DPA commits to return or deletion within 30 days of termination, with encrypted backups expiring on a 35-day rolling window.

Is there a version we can run in our own environment?

Yes — Bee Enclave runs single-tenant in your VPC from $7,500/mo, with regulated and air-gapped sovereign options above it.

Team AI chat your security review can actually verify

Encryption specified by algorithm, no-training commitments written into the Terms, per-tenant isolation, and a published legal surface — with a hardening path that ends air-gapped.

Security you can name, not vibes

→TLS 1.3 on the transport path; AES-256-GCM at rest under per-tenant keys.
→Customer-managed keys available on Hive and above.
→Operator access to production is hardware-backed FIDO2 only — no long-lived static credentials.
→Post-quantum transport (FIPS 203/204/205) ships default-on for Enclave Sovereign; public tiers run standard TLS 1.3 today, stated exactly that way on the /security page.

The commitments that survive procurement

Customer data is not used to train the Bee base model. Prompts, documents, and outputs stay yours; processing is limited to serving, securing, and operating the service.

The Terms, Privacy Policy, DPA with EU Standard Contractual Clauses, and the sub-processor list are published and footer-linked on every page; counter-signed copies are available. Breach notification within 72 hours is a DPA term, not a support-ticket aspiration.

Chat that does team-scale work

This is a working workspace, not a locked-down toy: pooled tokens across seats, shared document retrieval with cited answers (Buzz and above), image and video input on Comb, Buzz, and Hive, and 256K native context. Plans run from the free Cell tier to Swarm (25 seats, 250M pooled tokens, 99.9% uptime SLA).

When shared cloud isn't enough

The same workspace hardens down the deployment ladder: Enclave Private Cloud (from $7,500/mo) in your VPC, Enclave Regulated with customer-managed keys and immutable audit logs, and Enclave Sovereign air-gapped with customer-controlled HSMs.

HEOSSI (Pte.) Ltd. is Singapore-incorporated; PDPA governs local processing and the DPA extends GDPR/UK GDPR coverage. Region pinning is available on Hive and above.

Frequently asked questions

Is team chat content used to train models?: No — customer data is not used to train the Bee base model. The commitment is contractual, in the Terms of Service and DPA.
How is chat data encrypted?: TLS 1.3 in transit and AES-256-GCM at rest under per-tenant keys, with customer-managed keys available on Hive and above.
Can conversations be kept in a specific region?: Hive-plan and above customers can request region-pinned processing (EU, US, or Singapore); Enclave deployments keep everything inside your own environment.
What happens to our data if we leave?: The DPA commits to return or deletion within 30 days of termination, with encrypted backups expiring on a 35-day rolling window.
Is there a version we can run in our own environment?: Yes — Bee Enclave runs single-tenant in your VPC from $7,500/mo, with regulated and air-gapped sovereign options above it.

One AI workspace for the whole team AI infrastructure that plans for the cryptography deadline A private LLM API your security team can sign off on

Start on the free tier

Bee Cell is free — no card. Scale to paid tiers, the API, or sovereign deployment when you are ready.

Get started free See pricing