Data Integrity and Infrastructure Policy for CppModel
1. Purpose
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.
2. Scope
This policy applies to:
- Simulation input and output data
- Simulation execution metadata
- User-generated project configuration
- Runtime simulation artifacts
- Operational logs
- Tenant infrastructure environments
This policy does not apply to:
- Authentication credential management handled by Keycloak
- Payment processing and billing information handled by Stripe
3. Data Collection Overview
CppModel is designed to minimize collection of customer and proprietary information.
3.1. Customer Identity Data
CppModel stores limited customer identity information required for platform operation, including:
- Email address
- User name
- Company or organization information where applicable
Authentication credentials and identity management are handled through Keycloak integrations.
CppModel does not store customer passwords.
3.2. Payment Data
Payment processing and subscription management are handled by Stripe.
Stripe may process:
- Customer names
- Email addresses
- Billing information
- Company details
- Payment method information
CppModel does not store payment card details.
3.3. Simulation Data
CppModel primarily stores:
- Simulation-related input data
- Simulation outputs
- Simulation configuration data
- Execution metadata
- Runtime state relevant to simulations
4. Customer Intellectual Property Protection
CppModel is designed to minimize transfer of proprietary customer software assets.
Unless explicitly configured otherwise by the customer:
- Customer source code is not transferred to CppModel cloud infrastructure
- Customer binaries are not uploaded to CppModel infrastructure
- Simulation integrations operate without requiring full customer application transfer
- Simulation-related data exchanged with the platform is limited to runtime simulation inputs, outputs, configuration data, and execution metadata
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.
5. Integrity Principles
CppModel follows the following integrity principles.
5.1. Accuracy
Simulation data should accurately reflect submitted simulation inputs and produced outputs.
5.2. Traceability
Simulation executions should be traceable to:
- User account
- Tenant environment
- Project or workspace
- Execution timestamp
- Simulation configuration
- Platform or simulation version where applicable
5.3. Isolation
Tenant environments are logically isolated from one another using dedicated virtual machine environments.
5.4. Least Privilege
Access to simulation data and operational infrastructure is restricted to authorized users and operational personnel.
6. Infrastructure and Tenant Isolation
CppModel uses infrastructure-level tenant isolation.
Each customer tenant operates within a dedicated virtual machine environment containing:
- Simulation services
- Backend services
- Tenant-specific simulation data
- Tenant-specific logs
- Runtime simulation state
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.
7. Operational Access
Authorized CppModel operational personnel may access tenant environments when required for:
- Technical support
- Maintenance
- Diagnostics
- Infrastructure operations
Such access is limited to authorized personnel and operational requirements.
8. Network Connectivity
Tenant simulation environments may have outbound internet connectivity enabled depending on operational requirements and deployed integrations.
9. Software Deployment Integrity
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.
10. Logging and Operational Monitoring
Operational logs relevant to simulation execution and backend operation are maintained within tenant environments.
Where applicable, logs may be used for:
- Diagnostics
- Operational monitoring
- Incident investigation
- Technical support
11. Backup and Recovery
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.
12. Third-Party Services
12.1. Keycloak
CppModel relies on Keycloak for:
- Authentication
- Identity federation
- Session management
- Access token issuance
12.2. Stripe
CppModel relies on Stripe for:
- Payment processing
- Subscription management
- Billing operations
Sensitive payment information is processed exclusively by Stripe infrastructure.
13. Customer Responsibilities
Customers are responsible for:
- Managing access credentials
- Reviewing exported simulation data
- Maintaining external backups where required
- Validating data exchanged by integrations and simulations
- Managing internal user permissions within their organizations
14. Incident Handling
Potential integrity incidents may include:
- Unauthorized access
- Accidental data modification
- Runtime failures
- Infrastructure failures
- Cross-tenant exposure risks
CppModel will investigate and address operational incidents based on severity and operational impact.
15. Future Security and Reliability Improvements
CppModel continuously evolves its operational and infrastructure practices.
Planned improvements include:
- Automated backup infrastructure
- Enhanced deployment automation
- Additional integrity verification mechanisms
- Expanded operational auditing
- Improved disaster recovery procedures
16. Policy Review
This policy may be updated periodically to reflect infrastructure, operational, and platform changes.
17. Contact Information
If you have any questions or concerns regarding this Data Integrity and Infrastructure Policy, please contact us at [email protected].