KeplerCrew is provided by AiChargeLabs. This page explains the public website’s purpose and the configuration-dependent data handling of the product. Your organisation’s deployment agreement and data-processing terms provide the details for its environment.
1. Information you provide
Public account, access-request, and support flows use the information you submit, such as your email address, name, organisation, and message, to handle that request and provide the associated service. Sign-in uses session and verification information to manage access.
Inside the product, tasks and conversations can involve instructions, source code, repository context, project information, tool results, and run evidence. Which information is processed depends on what you provide, the access you grant, and the configured workflow.
2. Your deployment and context boundary
KeplerCrew can run on a customer machine or private infrastructure, as configured. The deployment determines where workspace information and run records are processed and stored, who administers them, and which connected services can receive information.
3. Models and connected services
Model endpoints, repository access, and other integrations depend on your deployment and configuration. Applicable provider terms and your organisation’s agreement determine the processing conditions for those services. Contact us for the deployment-specific provider and data-processing details; this page does not assume one provider list for every customer.
4. Records and retention
Conversations, tasks, tool activity, and run evidence may form part of your workspace records. Retention, backups, diagnostic settings, export, and deletion depend on the configured deployment and applicable agreement. There is no universal deletion deadline or retention period stated on this page.
5. Access and security
Review the deployment’s access permissions, execution boundaries, model connectivity, and operational controls with your administrator. The controls available in one environment should not be assumed to apply identically to another. See our security approach and request details for your proposed setup.
6. Privacy requests
Contact us about access, correction, export, or deletion of information associated with the public service. For a customer-managed deployment, your organisation’s administrator may be the appropriate first contact. The response and available actions depend on applicable requirements, the deployment, and the relevant agreement.
Deployment-specific details
For privacy questions, a data-processing agreement, or confirmation of your environment’s handling of customer data, contact support@aichargelabs.com. Do not include credentials or sensitive repository content in your initial message.