Skip to content

Legal

Model Improvement & Data Use

Effective 2026-07-29·Last updated 2026-07-29·HEOSSI (Pte.) Ltd.

This policy explains how interactions may be used to improve Bee. Improve Bee is enabled by default for accounts and service surfaces until the account holder or customer opts out. Model improvement is separate from processing needed to answer a request, secure an account, bill for service, or comply with law.

1. The default

  • Bee does not use Customer Data to pre-train a foundation/base model.
  • Improve Bee is enabled by default for personal accounts, organisation workspaces, API use, Enterprise, Enclave, government and restricted-domain use. It remains enabled until the account holder or authorised customer administrator turns it off.
  • You may turn Improve Bee off at any time without losing access to Bee. A recorded opt-out is preserved and is not silently reversed.
  • Where applicable law requires a different consent or notice mechanism, HEOSSI will apply the legally required mechanism without changing the general product default elsewhere.

2. Eligible personal conversations

  • Unless Improve Bee is switched off, selected prompts, outputs, explicit feedback, documents, repositories, connector content, attachments and other submitted material may be copied into a restricted improvement dataset.
  • Assistant output from a third-party provider is excluded where provenance or the provider contract does not permit that use.
  • Eligible data may be used to fine-tune Bee adapters, improve request routing and refusal behaviour, build evaluations, diagnose systematic quality failures, and evaluate safety behaviour for the Bee Ignite programme. Customer Data is never used to pre-train an Ignite foundation checkpoint.
  • Participation does not authorise us to publish conversations, train an unrelated third-party model, advertise to you, or expose content to another customer.

3. Safety and abuse processing

  • Bee may scan requests and outputs to enforce the Acceptable Use Policy whether or not Improve Bee is enabled. That real-time processing is necessary to secure the service and enforce the contract.
  • When Improve Bee is off, the training pipeline does not retain a new identifiable research copy of the blocked prompt. We may retain minimised security metadata-time, account id, rule triggered, and request identifiers-for fraud prevention, investigation, and legal compliance under the server-log retention schedule.

4. Data minimisation and protection

  • Improvement datasets use pseudonymous account hashes instead of email addresses where practicable. Research-queue content is access-restricted and encrypted at rest when the platform encryption key is available.
  • Automated and human curation seeks to remove obvious secrets and direct identifiers before a sample is approved for training. Do not submit confidential or sensitive personal data merely because this screening exists.
  • Hugging Face may host restricted improvement datasets as a sub-processor; access is not public. Other training infrastructure is listed in the DPA when it processes personal data.

5. Withdrawal and deletion

  • Turn Improve Bee off at any time in Account > Privacy or through the applicable organisation control. The change applies to future collection without requiring account cancellation and does not affect normal service.
  • To remove prior identifiable improvement copies, email bee-privacy@heossi.com. We will delete or irreversibly de-identify eligible copies within 30 days, subject to legal holds and backup expiry.
  • A trained model cannot ordinarily identify or surgically remove a particular training example. We therefore control the source dataset and future training use; where technically feasible and legally required, we also evaluate model-level remediation.

6. Custom and community training

  • Tenant-scoped custom training requires documented customer instructions and remains governed by the DPA. It does not place the customer's data in Bee's shared improvement dataset.
  • Publishing an adapter to a community surface is a separate, deliberate disclosure. The publisher must own or have permission for all training material and must not publish personal, confidential, infringing, or unlawful content.

Questions about this document? Contact bee-privacy@heossi.com. Service of process: bee-legal@heossi.com (HEOSSI (Pte.) Ltd., Singapore).

Counter-signed copies on request. The text on this page is the canonical published version. For procurement teams that need a counter-signed copy of the Terms, DPA, or Order Form, email bee-legal@heossi.com. Where there is conflict between this page and an executed counter-signed agreement, the counter-signed agreement controls.

Terms of ServicePrivacy PolicyBee Account and Data DeletionData Processing AddendumAcceptable Use PolicySecurity PracticesBEE for Startups Program TermsPartner Program TermsVC Partner Program TermsCookie PolicyAI Transparency & DisclosureAccessibility StatementCopyright & DMCA PolicyGovernment & Law-Enforcement Data RequestsRegional Terms & Mandatory RightsContent Moderation, Notices & AppealsDeveloper & API TermsModel Governance, Training Sources & Copyright
HEOSSI (Pte.) Ltd. · Singapore · heossi.comSee evidence index →