This document describes the data integrity, infrastructure isolation, and operational data handling practices of CppModel, operated by Control Edge AB (“we,” “us,” “our”).
The purpose of this policy is to define how simulation-related data is stored, processed, isolated, and protected within the CppModel platform.
This policy applies to:
This policy does not apply to:
CppModel is designed to minimize collection of customer and proprietary information.
CppModel stores limited customer identity information required for platform operation, including:
Authentication credentials and identity management are handled through Keycloak integrations.
CppModel does not store customer passwords.
Payment processing and subscription management are handled by Stripe.
Stripe may process:
CppModel does not store payment card details.
CppModel primarily stores:
CppModel is designed to minimize transfer of proprietary customer software assets.
Unless explicitly configured otherwise by the customer:
CppModel libraries and integrations are designed to avoid unnecessary collection or transmission of proprietary application code.
Customers remain responsible for reviewing and validating the data exchanged by their simulations and integrations.
CppModel is architected around simulation interaction and runtime behavior exchange rather than centralized source code hosting.
CppModel follows the following integrity principles.
Simulation data should accurately reflect submitted simulation inputs and produced outputs.
Simulation executions should be traceable to:
Tenant environments are logically isolated from one another using dedicated virtual machine environments.
Access to simulation data and operational infrastructure is restricted to authorized users and operational personnel.
CppModel uses infrastructure-level tenant isolation.
Each customer tenant operates within a dedicated virtual machine environment containing:
Tenant virtual machines may share underlying physical host infrastructure while remaining logically isolated from one another.
Simulation logs, runtime artifacts, and operational state are maintained within each tenant environment.
Authorized CppModel operational personnel may access tenant environments when required for:
Such access is limited to authorized personnel and operational requirements.
Tenant simulation environments may have outbound internet connectivity enabled depending on operational requirements and deployed integrations.
CppModel maintains controlled deployment procedures for simulation and backend services.
Deployment automation and additional integrity verification mechanisms are under active development as part of ongoing platform hardening efforts.
Operational logs relevant to simulation execution and backend operation are maintained within tenant environments.
Where applicable, logs may be used for:
CppModel currently does not maintain automated tenant backup infrastructure.
Customers are encouraged to maintain external copies of critical simulation artifacts and exported data where appropriate.
Backup and disaster recovery capabilities are planned as part of future infrastructure improvements.
CppModel relies on Keycloak for:
CppModel relies on Stripe for:
Sensitive payment information is processed exclusively by Stripe infrastructure.
Customers are responsible for:
Potential integrity incidents may include:
CppModel will investigate and address operational incidents based on severity and operational impact.
CppModel continuously evolves its operational and infrastructure practices.
Planned improvements include:
This policy may be updated periodically to reflect infrastructure, operational, and platform changes.
If you have any questions or concerns regarding this Data Integrity and Infrastructure Policy, please contact us at [email protected].