Trust and Security
Security and Compliance
Contact ClimaMind about security reports, privacy concerns, and customer compliance reviews.
Trust and Security
Contact ClimaMind about security reports, privacy concerns, and customer compliance reviews.
Send suspected vulnerabilities, security incidents, or privacy concerns to our dedicated security address. Include the affected service, what happened, and steps to reproduce where applicable. Avoid sending passwords, credentials, or unnecessary personal data.
Reports are reviewed by Chuan He, Founder and CEO. We assess the issue, coordinate investigation and corrective action, and communicate with the reporter as appropriate. Access to the security inbox is restricted to authorized personnel.
Use the same address for security questionnaires, privacy inquiries, and requests for compliance review materials. We review each request and share applicable information through an agreed channel, subject to confidentiality requirements.
These commitments follow the ClimaMind Optimize network architecture: the customer BMS keeps control authority, each customer is isolated, and site data leaves the site only with customer approval.
Each customer runs in its own container on the shared cloud runtime, with its own identity and its own S3 bucket. Cross-customer access is denied, and the runtime can reach only its own customer's data.
Customers sign in to the Console with email, password, and MFA. The API authorizes every request by customer and project. Customers get business functions only, never container or bucket administration.
Operating data and optimization results stay in the customer's bucket; the private database holds only accounts, projects, permissions, and file metadata. Traffic uses HTTPS, the cloud BMS entry uses mTLS, and secrets are held in AWS Secrets Manager.
The BMS initiates every request and executes control itself, and falls back when results fail or go stale. On-site deployments keep BACnet/IP inside the controlled site LAN, and data is uploaded only with customer approval.
Staff reach admin targets only through AWS Client VPN with corporate identity and MFA. Access is granted by job role, a VPN connection grants no blanket access, and admin activity is logged. Customer-site support needs customer approval for the task and time window.
Models train only on authorized data and customer models are exclusive to that customer. Exact model versions are approved before staff deploy them to the designated client; approval never triggers deployment, and the client never switches models on its own.
Every data type is classified before it is stored or shared, and handled according to its class.
| Classification | Examples | Encrypt at rest | Encrypt in transit | Handling |
|---|---|---|---|---|
| Public | Public website content, published marketing materials, public documentation | - | - | Approved for external distribution. |
| Internal | Non-public operational notes, implementation details, non-customer internal planning | - | ✓ | Limited to ClimaMind personnel and approved collaborators; encrypted transport for application and system-to-system transmission. |
| Confidential | Customer site metadata, building telemetry, optimization results, dashboard data, project files, support context, customer configuration | ✓ | ✓ | Stored in the customer's own bucket; access-controlled; used only for customer delivery, support, operations, and approved analysis. |
| Restricted | Credentials, secrets, certificates and keys, BMS access details | ✓ | ✓ | Stored in AWS Secrets Manager; encrypted in transit where transmitted; access is tightly restricted. |