Data Privacy and Protection Policy¶
Overview¶
CloudAEye provides cloud-hosted SaaS services and supports self-hosted deployments of CloudAEye Code Review.
The deployment model determines where application services and customer data are processed and stored:
- CloudAEye-hosted SaaS: CloudAEye operates the service in its AWS environment. Customer data is logically isolated and protected using access controls and encryption.
- Self-hosted Code Review: CloudAEye is deployed into the customer's AWS account using the CloudAEye Terraform deployment bundle. The customer operates the AWS environment and controls its network, infrastructure, and data-storage environment.
This policy describes the two deployment models separately. Self-hosting currently supports Amazon ECS; it is not a general-purpose on-premises or arbitrary Kubernetes deployment.
CloudAEye uses data classification, access controls, and encryption to protect information against unauthorized access. Customers should review the Self-Hosting System Architecture and deployment guides for the components, network paths, and configuration requirements of a self-hosted installation.
Concepts¶
Tenant Isolation¶
Tenant isolation means controlling access to resources using tenant context so that one customer cannot access another customer's resources. In the CloudAEye-hosted SaaS environment, application authorization and AWS resource policies are used to enforce tenant boundaries.
In a self-hosted deployment, the application runs in infrastructure deployed in the customer's AWS account. The deployment is dedicated to that customer's environment rather than sharing the CloudAEye-hosted SaaS infrastructure.
Tokenization and Secrets Management¶
Secrets management protects credentials and other sensitive values from being embedded in application source code. CloudAEye's self-hosted deployment accepts configuration and secret values through its deployment configuration. Customers must protect deployment files and state that contain sensitive values.
Encryption¶
Encryption transforms information so it cannot be read without the required cryptographic key.
Data at Rest¶
Data at rest is information persisted in storage. Protecting stored data reduces the risk of unauthorized access.
Data in Transit¶
Data in transit is information sent between systems. HTTPS and TLS can protect the confidentiality and integrity of network communications.
Data Privacy and Protection¶
Deployment Models and Data Boundaries¶
CloudAEye-hosted SaaS¶
For the SaaS service, CloudAEye operates the application and its supporting infrastructure. Customer data is logically isolated through tenant-aware access controls and AWS resource policies. The SaaS service is hosted in the AWS US East region.
For Code Review, CloudAEye accesses repository content needed to perform the requested analysis. The SaaS service stores application metadata and review-related information as described in the FAQ below. Do not interpret this as a promise that no code-derived information is ever persisted: the exact data handled depends on the feature and workflow.
Self-Hosted Code Review¶
CloudAEye supports self-hosting of Code Review in a customer's AWS account. The deployment bundle uses Terraform to provision the application on Amazon ECS Managed Instances.
The documented architecture includes:
- An Application Load Balancer (ALB) as the public entry point for the web console, APIs, authentication, MCP, SSO callbacks, and GitHub webhooks.
- ECS application services and background workers running in private subnets in the customer's VPC.
- MongoDB for application data, tenant state, review results, and license status.
- ChromaDB for vectorized repository code context used during review generation.
- Encrypted EBS volumes for persistent MongoDB and ChromaDB storage.
- Amazon SQS queues for asynchronous repository indexing and pull-request review work.
- AWS CloudWatch for service logs and ECS metrics.
The MongoDB and ChromaDB services are private and are not exposed through the public ALB. ECS tasks use private networking; outbound access through the configured network path is used for required dependencies and integrations.
Because the self-hosted application and its databases run in the customer's AWS account, the customer controls the AWS account, VPC, deployment region, network configuration, and access to the underlying infrastructure. The customer is also responsible for securing its AWS account, restricting administrative access, protecting deployment configuration and Terraform state, and applying its infrastructure and backup policies.
Self-hosting does not mean that every interaction is necessarily confined to the customer's AWS account. The application may communicate with external systems required for operation, including source-control providers, AWS services, license validation, and the LLM provider configured for review generation. The customer should review and approve these network paths and the data shared with each external provider. In particular, review prompts and relevant repository context are sent to the configured LLM provider to generate review results.
See the Self-Hosting System Architecture for the detailed service flow and network boundaries.
Tenant Isolation¶
In the CloudAEye-hosted SaaS architecture, tenant-aware authorization and AWS resource-based IAM policies restrict access to tenant resources and backing services.
In a self-hosted deployment, the application is deployed into the customer's AWS environment. The customer environment provides the infrastructure boundary between that deployment and other customers' deployments. Application-level authentication and authorization continue to apply within the deployment.
Identity and Access Management¶
CloudAEye uses role-based access control (RBAC) to manage user privileges. The self-hosted Code Review deployment uses the Better Auth service for authentication and supports enterprise single sign-on integrations, including Okta and Keycloak, as documented in the self-hosting security guides.
For self-hosted deployments, the customer controls access to the AWS account and the infrastructure hosting CloudAEye. The customer should restrict access to the AWS console, deployment roles, Terraform configuration, and runtime secrets to authorized personnel.
Secrets Management¶
CloudAEye's self-hosted deployment receives runtime configuration and customer-specific values through Terraform variables and container environment variables. The Terraform configuration file (for example, terraform.tfvars) and Terraform state may contain sensitive values and must be stored securely with access limited to authorized administrators.
For the CloudAEye-hosted SaaS environment, CloudAEye manages service credentials and infrastructure secrets.
Encryption at Rest and in Transit¶
CloudAEye-hosted SaaS data is encrypted at rest and protected in transit using HTTPS/TLS. The SaaS environment uses AWS Key Management Service (AWS KMS) and AES-256 encryption for data at rest.
For self-hosted Code Review, the documented deployment provisions encrypted EBS storage for MongoDB and ChromaDB. The customer is responsible for configuring and maintaining the security of the AWS environment, including the ALB listener and TLS certificate configuration, network access rules, AWS account permissions, and any additional encryption or key-management controls required by the customer's policies.
Frequently Asked Questions (FAQ)¶
Purpose¶
What is the purpose and use of collected customer data?¶
CloudAEye Code Review analyzes source repositories and pull requests (PRs) to identify issues and provide review results. CloudAEye's automated test failure analysis helps identify root causes of test failures in CI and suggest solutions. Availability of deployment models may differ by product; the self-hosting documentation currently describes Code Review.
Deployment and Isolation¶
Does CloudAEye support self-hosting?¶
Yes. CloudAEye supports self-hosted deployments of Code Review in a customer's AWS account. The documented deployment uses Terraform to provision CloudAEye on Amazon ECS Managed Instances. The web console and selected application endpoints are exposed through an Application Load Balancer, while application tasks, workers, and data services run within the customer's VPC.
Self-hosting currently supports Amazon ECS. Refer to the Self-Hosting documentation for architecture and deployment details.
Where does customer data reside in a self-hosted deployment?¶
The self-hosted application and its primary data stores run in the customer's AWS account and configured AWS region. MongoDB stores application data, tenant state, and review results. ChromaDB stores vectorized repository code context used during review generation. Both data stores use encrypted EBS storage in the documented architecture.
The application may also send information to external systems needed to provide the service, including the configured LLM provider, source-control provider, AWS services, and license-validation services. Customers should assess those integrations and their data-handling terms as part of deployment approval.
How does CloudAEye store customer data?¶
The storage model depends on the deployment:
- CloudAEye-hosted SaaS: CloudAEye operates the service in its AWS environment and uses tenant-aware controls and AWS resource policies to restrict access. The SaaS service is hosted in AWS US East.
- Self-hosted Code Review: The application and its MongoDB and ChromaDB data stores run in the customer's AWS account. MongoDB stores application data, tenant state, and review results; ChromaDB stores vectorized repository code context.
For self-hosted deployments, the customer controls access to the AWS infrastructure and is responsible for protecting the AWS account, deployment configuration, and stored data.
Is customer source code stored?¶
The answer depends on the deployment and processing workflow.
For CloudAEye-hosted SaaS Code Review, CloudAEye accesses the specific code snippets needed when a review is requested. The existing SaaS service description states that source code is not stored in CloudAEye and that repository metadata, such as repository names, may be stored. Review records are subject to the configured retention policy.
For self-hosted Code Review, repository content is indexed into vectorized code context and stored in the customer's ChromaDB instance. Review processing retrieves this context from ChromaDB and persists review results and related application data in the customer's MongoDB instance. These data stores are deployed in the customer's AWS account.
In both deployment models, review processing may send relevant repository context and prompts to the configured LLM provider. The handling of that information by the LLM provider is subject to the provider's terms and configuration.
What specific data is sent to CloudAEye or external services?¶
The information exchanged depends on the enabled integrations and deployment model.
- Code Review: CloudAEye connects to the source-control provider to access repositories, repository content, pull requests, and related events needed for indexing and review. In a self-hosted deployment, indexed code context and review results are stored in the customer's AWS environment.
- LLM provider: Review processing sends the relevant prompt and repository context to the LLM provider configured for the deployment so that it can generate review output.
- Jira (optional): Customers may connect Atlassian Jira Cloud for the configured read/write productivity workflows.
- Test Failure Analysis: Customers may connect GitHub Actions, Jenkins, or AWS CodeBuild to support automated root-cause analysis and resolution of test failures.
For self-hosted Code Review, outbound network access is also used for required AWS services, source-control integrations, license validation, and the configured LLM provider. See the system architecture documentation for the current network flow.
Where is CloudAEye-hosted SaaS data stored?¶
The CloudAEye-hosted SaaS service is hosted in the AWS US East region. This statement applies to the CloudAEye-hosted SaaS environment; it does not describe the location of a self-hosted deployment, which runs in the customer's configured AWS environment.
Data Storage and Retention¶
How long is customer data retained? Can it be deleted or returned at the end of the engagement?¶
For the CloudAEye-hosted service, customers can configure policy-based data aging and removal. For Code Review, customers may set a retention period for older code reviews, after which the applicable data is deleted.
For self-hosted Code Review, the deployment includes a scheduled cleanup task that runs daily and removes old data from MongoDB. Customers should configure and verify retention settings for their deployment and maintain any backups in accordance with their own retention and deletion policies.
Can CloudAEye provide customer data in a readable and easily transferable format when required?¶
Yes. Contact CloudAEye to coordinate an export appropriate to the deployment and data requested. For self-hosted deployments, customers also have access to the data stores in their AWS environment, subject to their own operational controls.
Personal Information¶
Does CloudAEye use personal information for any purpose outside of providing the services?¶
No. CloudAEye uses personal information to provide and administer the services, including account management and billing.
Does CloudAEye handle or otherwise process personal data (e.g. personally identifiable information, employee, customer, or partner information) for purposes other than account management or billing?¶
CloudAEye does not use personal information for purposes unrelated to providing the services. Customer content submitted through connected repositories or integrations may contain personal information; customers are responsible for ensuring that their use of the service and connected systems complies with their obligations and policies.
Does CloudAEye use anonymized or aggregate data for an independent purpose outside of providing the services?¶
No.
Does CloudAEye delete personal information such as an email address?¶
For the CloudAEye-hosted service, account information is removed when a customer unsubscribes, subject to applicable retention and legal requirements.
For self-hosted deployments, account and application data are stored in the customer's environment. The customer administers that environment and its data-retention and deletion processes.
Can CloudAEye stop processing personal information when requested?¶
For the CloudAEye-hosted service, tenant administrators can use RBAC controls to add or remove users. A customer can request account deletion by unsubscribing from the service.
For self-hosted deployments, customer administrators manage user access through the deployment's authentication and authorization configuration. The customer also controls the underlying AWS environment and can manage access to the deployment and its data.
Encryption¶
Is customer data encrypted in transit?¶
CloudAEye-hosted SaaS traffic is protected using HTTPS and TLS.
For self-hosted deployments, the ALB supports HTTP or HTTPS listeners. Customers should configure HTTPS with an appropriate TLS certificate for production use and restrict network access using the deployment's security-group and CIDR settings.
Is customer data encrypted at rest?¶
CloudAEye-hosted SaaS data is encrypted at rest using AWS KMS and AES-256.
In the documented self-hosted architecture, MongoDB and ChromaDB use encrypted EBS volumes. Customers are responsible for the security of their AWS account and for verifying that the deployed storage and backup configuration meets their requirements.
What encryption algorithms and key-management services are used?¶
For CloudAEye-hosted SaaS, AWS KMS manages encryption keys and AES-256 is used for encryption at rest. HTTPS/TLS protects data in transit.
For self-hosted Code Review, the documented architecture uses encrypted EBS storage for MongoDB and ChromaDB. The customer manages the AWS environment and should review its AWS encryption, key-management, TLS, and backup settings as part of deployment configuration.