Security & compliance

Enterprise-Grade Security, Built Into How We Deploy

Conversational BI that meets PIPL, GDPR, PDPO and the EU AI Act — with data residency, IM-native security inheritance, and AI governance by default.

PIPL GDPR PDPO EU AI Act
15+
Years of enterprise delivery
7
IM surfaces secured
AES-256
Encryption at rest
TLS 1.3
Encryption in transit
Regulatory posture

Compliance Across Jurisdictions

We operate under overlapping regimes so your deployment is defensible wherever your teams sit.

01 / CHINA

PIPL · DSL · CSL

China's personal information, data security, and cybersecurity laws — with MLPS 2.0 Level 3 in progress.

02 / HONG KONG

PDPO & CIO Ordinance

Hong Kong's Personal Data Privacy Ordinance and the new Critical Information Infrastructure regime.

03 / EUROPE

GDPR & EU AI Act

EU data protection plus the risk-tiered AI Act obligations for high-impact systems.

04 / APAC & US

PDPA · CCPA/CPRA

Singapore and US state privacy frameworks, covered for cross-border enterprise clients.

Track record

Fifteen Years of Delivering Enterprise Systems

Long before conversational AI, our team shipped secure, regulated systems for institutions that cannot afford to be wrong.

2010 – 2015

Foundation

Enterprise data platforms and integration for financial and retail clients.

2015 – 2020

Cloud & scale

Multi-region, compliant cloud architectures with audited access controls.

2020 – 2025

AI in production

First conversational and agentic deployments inside client IM environments.

2025 – 2026

Forward-deployed

Governed AI embedded where teams already work, with security inherited from the platform.

How we protect data

Encryption & Isolation by Default

Every deployment starts from a zero-trust baseline, not an enterprise upsell.

01

Encrypt everything

All data is encrypted in transit with TLS 1.3 and at rest with AES-256.

02

Per-tenant isolation

Client data is fully isolated; one client's data is never visible to another.

03

Role-based access

Least-privilege access with complete audit logging on every action.

04

No raw data to LLMs

Raw client data never leaves the secure environment and is never sent to model prompts.

05

Aggregated only

Only aggregated, anonymised query results are sent to enterprise-grade LLM providers.

06

Human review option

Enterprise clients can require human review before any AI answer is delivered.

AI governance

We Never Train on Your Data

Our governance model is the product. It is not a checkbox we add at the end.

01

No model training

Client data is never used to train any LLM. Models are general-purpose and pre-trained.

02

Prompt boundary

Only aggregated, anonymised results reach the model for natural-language generation.

03

Auditability

Every query, answer, and data access is logged and reviewable on request.

Raw rows never cross the boundary. The model sees a summarised result, never the underlying records — and enterprise clients can require a human checkpoint before an answer is delivered.

Data residency

Your Data Stays Where It Belongs

China client data stays in mainland China; Hong Kong data stays in Hong Kong. Only aggregated or anonymised results may cross borders.

01 / SOURCEYour systems of recordRaw rows remain inside your environment.
02 / ISOLATIONPer-tenant secure enclaveTLS 1.3 in transit, AES-256 at rest, least-privilege access.
03 / AGGREGATIONAggregated results onlyAnonymised summaries, never raw records.
04 / GENERATIONEnterprise LLMNatural-language answer; human review available.
CHINA TRANSFERS

China SCC / GBA / CAC

Where personal data must cross borders, we use China SCC, the GBA Standard Contract, or a CAC Security Assessment.

EU TRANSFERS

EU SCCs + TIA

For EU data we use EU Standard Contractual Clauses with Transfer Impact Assessments.

We add no new attack surface

Your IM Platform's Security Is Ours

We deploy inside the platform you already secured. Each channel inherits enterprise-grade security — we add scoped permissions and data minimisation on top.

ChannelPlatform securityOur additional layer
WeChat WorkEnterprise authentication, Tencent cloud securityISV-level data isolation, no credential storage
DingTalkAlibaba cloud security, enterprise SSOISV sandbox, data minimisation
FeishuByteDance enterprise securityBot API security, scoped permissions
WhatsAppEnd-to-end encryption, Meta enterprise securityToken-based API access, no message content stored
Microsoft TeamsM365 security, Azure AD, DLP policiesBot Framework security, tenant isolation
TelegramMTProto encryption, bot token securityNo sensitive data in messages, auto-delete timers
SlackEnterprise Grid security, SSO, DLPApp-level permissions, scoped tokens

We don't add a new attack surface. We work within the security framework you've already secured, and every deployment inherits the enterprise-grade security of the platform you choose.

Certifications roadmap

Targeting Industry Standards

We are transparent about where we are and where we are heading. Our architecture already meets these standards — formal certification is the next step.

TARGETING · 6–12 MONTHS

ISO 27001:2022

Global standard for information security management. 93 controls across 4 themes.

IN PROGRESS

MLPS 2.0 Level 3

China's de facto benchmark for serious B2B SaaS — management systems, segmentation, access control, encryption, incident response.

TARGETING · 6–18 MONTHS

SOC 2 Type II

US/international SaaS standard covering security, availability, processing integrity, confidentiality, and privacy.

Our security architecture already meets these standards. We encrypt all data in transit and at rest, isolate each client's data, never expose raw data to LLMs, and operate within your existing IM security framework across WeChat Work, DingTalk, Feishu, WhatsApp, Microsoft Teams, and Telegram.

Incident response

A Six-Phase Response Protocol

When an incident occurs, speed and transparency matter. Our protocol defines containment, communication, and remediation.

PHASE 01

Detection

Automated monitoring plus manual reporting.

Real-time
PHASE 02

Assessment

Classify severity and determine scope.

Within 1 hour
PHASE 03

Containment

Isolate systems and revoke access.

Within 4 hours
PHASE 04

Notification

Notify clients and regulators.

Within 72 hours
PHASE 05

Remediation

Fix the vulnerability and restore service.

24–48 hours
PHASE 06

Post-incident

Root-cause analysis and prevention.

Within 2 weeks
Questions

Security FAQ

Practical answers about our security practices, compliance posture, and data governance.

Beehive Strategy encrypts all data in transit using TLS 1.3 and at rest using AES-256. Client data is fully isolated per tenant, with role-based access control and complete audit logging. Raw client data never leaves the secure processing environment and is never sent to LLM prompts. Only aggregated, anonymised query results are sent to enterprise-grade LLM providers for natural language generation.

In China, we comply with PIPL, DSL, CSL, and are targeting MLPS 2.0 Level 3 certification. In Hong Kong, we comply with PDPO and the CIO Ordinance. Internationally, we comply with GDPR, the EU AI Act, Singapore PDPA, and applicable US state privacy laws including CCPA/CPRA.

No. We never use client data to train any LLM models. Only aggregated and anonymised query results are sent to the LLM for natural language generation. Raw client data never leaves the secure processing environment. Enterprise clients can additionally require human review before any AI-generated answers are delivered.

China client data stays in mainland China infrastructure, and Hong Kong client data stays in Hong Kong infrastructure. Only aggregated or anonymised results may cross borders, which may qualify for China's Scenario A exemption. Where personal data must cross borders, we use China SCC, GBA Standard Contract, or CAC Security Assessment for China transfers, and EU SCCs with Transfer Impact Assessments for EU transfers.

We are pursuing ISO 27001:2022 (targeting 6–12 months), MLPS 2.0 Level 3, and SOC 2 Type II (targeting 6–18 months). Our security architecture already meets these standards — we encrypt all data in transit and at rest, isolate each client's data, never expose raw data to LLMs, and operate within existing IM security frameworks.

Ready to Deploy AI Your Security Team Will Approve?

Start with a free readiness assessment, or book a working session to walk through your data-residency and governance requirements.