These Terms of Service, together with all Order Forms, Data Processing Agreements, and incorporated policies (collectively, the Agreement), form a legally binding contract between Customer and Compounds Dev, Inc., a Delaware corporation with its principal place of business at 608 Brook Run Drive, Westerville 43081, Ohio, United States (Compounds, we, or us), governing Customer’s access to and use of the Compounds.dev platform and all associated services (the Service).By signing an Order Form, clicking “I agree”, or using the Service, Customer accepts this Agreement. If Customer accepts on behalf of an organization, Customer represents that it has full authority to bind that organization.1. DEFINITIONS1.1 AccountAn administrative or user account used to access the Service.1.2 Customer DataData submitted to or processed by the Service on behalf of Customer, including source code, build logs, CI or CD pipeline metadata, developer or team configurations, user account details, and telemetry relating to Customer’s use of the Service. Customer Data does not include Aggregated Data or Compounds Materials.1.3 Customer InputAny prompt, instruction, configuration, or other content that Customer provides to the Service.1.4 Customer OutputAny output, recommendation, or suggestion generated by the Service in response to Customer Input.1.5 Aggregated DataData processed by Compounds in aggregated and de identified form that cannot be used to identify Customer or any individual.1.6 Order FormA written or electronic ordering document executed by Customer describing purchased tiers, features, usage limits, pricing, and billing terms.1.7 Compounds MaterialsThe Service, software, algorithms, machine learning models, documentation, user interfaces, data structures, design elements, and all intellectual property owned or licensed by Compounds.1.8 Sub processorA third party that Compounds authorizes to process Customer Data.1.9 Service TermThe duration of Service defined in an Order Form and any renewals.2. THE SERVICE2.1 DescriptionCompounds.dev is a cloud hosted platform that provides transient code analysis, automated engineering recommendations, software quality insights, CI and CD workflow insights, and software development productivity analytics. The Service does not execute commands, run code, deploy infrastructure, or perform automated actions inside Customer environments.2.2 Service AvailabilityCompounds will use commercially reasonable efforts to make the Service available except during scheduled maintenance, emergency maintenance, events outside Compounds control, or outages caused by Customer systems or third party integrations.2.3 UpdatesCompounds may update or modify the Service at any time. Major functional changes will be communicated when practicable.2.4 Customer SupportCompounds will provide support as described in the Order Form or support documentation.3. ACCOUNT REGISTRATION AND ACCESS3.1 Account CreationCustomer must provide accurate information during registration and keep it current.3.2 Credential SecurityCustomer is responsible for maintaining the confidentiality of credentials, configuring appropriate access controls, and all activity under the Account, whether or not authorized.3.3 Usage LimitsCustomer may not exceed the usage limits specified in the Order Form. Compounds may monitor compliance.4. LICENSE AND USE RESTRICTIONS4.1 License GrantCompounds grants Customer a limited, non exclusive, non transferable, non sublicensable license to access and use the Service during the Service Term for Customer’s internal business purposes.4.2 License RestrictionsCustomer will not:Reverse engineer, modify, translate, or create derivative works of the ServiceAccess the Service to build a competing productUse the Service for automated code execution, deployment, or production changesCircumvent usage limitsInterfere with Service operationUse the Service for benchmarking or competitive analysisRemove proprietary notices from Compounds MaterialsUse the Service in violation of laws including privacy, export, or data protection laws4.3 Customer ResponsibilitiesCustomer is responsible for validating all Customer Outputs, maintaining compliant integrations with tools including GitHub, GitLab, Jira, Azure DevOps, ensuring Customer Data does not infringe third party rights, implementing appropriate security controls, and ensuring no production credentials or secrets are submitted through the Service.4.4 No Automated ExecutionThe Service provides insights and code suggestions only. It does not execute commands or modify systems. Customer is responsible for all actions taken based on Customer Outputs.5. INTELLECTUAL PROPERTY5.1 OwnershipCustomer owns Customer Data and Customer Outputs. Compounds owns all Compounds Materials. No transfer of ownership occurs.5.2 Customer OutputsCustomer Outputs are generated algorithmically. Outputs may be incomplete, incorrect, insecure, or non compliant. Outputs must be reviewed and validated by Customer before use. Compounds does not guarantee suitability of any Output.5.3 FeedbackCustomer grants Compounds a perpetual, irrevocable, royalty free license to use feedback for improving the Service.6. CUSTOMER DATA AND PRIVACY6.1 Data ProcessingCompounds processes Customer Data transiently for analysis, for account management, security and operational monitoring, feature improvement, and as permitted by law and the DPA. Compounds does not store full Customer codebases unless explicitly configured under an enterprise agreement.6.2 Prohibited DataCustomer will not submit production credentials, secrets or private keys, PHI unless expressly permitted in writing, PCI data, or government classified data.6.3 Aggregated DataCompounds may create Aggregated Data for analytics, benchmarking, and Service improvement.6.4 Sub processorsCompounds uses Sub processors including Anthropic and Google Gemini. A current list is available upon request.6.5 Model ProvidersCustomer acknowledges that Customer Inputs may be processed by model providers for inference. Model providers do not retain or train on Customer Data.7. SECURITY7.1 Compounds SecurityCompounds maintains industry standard security measures including encryption in transit, access controls, network protections, monitoring and logging, and secure development practices.7.2 Customer ResponsibilitiesCustomer is responsible for securing repositories, CI systems, and integrations, managing access control within Customer environments, reviewing Outputs before use, and preventing unauthorized access.8. THIRD PARTY SERVICESThe Service integrates with third party services including GitHub, GitLab, Bitbucket, Jira, Linear, ServiceNow, CI and CD systems, and cloud providers. Compounds is not responsible for availability of third party services, data loss caused by those services, or security incidents caused by misconfigurations in those services.9. FEES AND BILLING9.1 FeesCustomer will pay the fees listed in the Order Form.9.2 InvoicesInvoices are due within the period specified in the Order Form.9.3 TaxesFees exclude taxes. Customer is responsible for all taxes other than Compounds income taxes.9.4 Overage ChargesIf Customer exceeds usage limits, Compounds may invoice for overages.10. CONFIDENTIALITY10.1 Confidential InformationEach party may disclose proprietary or confidential information to the other.10.2 ObligationsThe receiving party will protect confidential information using no less than reasonable measures, not disclose it except to personnel with a need to know, and not use it except to perform the Agreement.10.3 ExclusionsConfidentiality obligations do not apply to information that is public, already known, independently developed, or required to be disclosed by law.11. WARRANTIES AND DISCLAIMERS11.1 DisclaimerThe Service and Outputs are provided as is and as available. Compounds does not warrant that Outputs will be accurate, safe, or reliable, that recommendations will be correct or suitable, that the Service will be uninterrupted, that integrations will function correctly, or that the Service will meet Customer requirements.11.2 Customer ResponsibilityCustomer is responsible for validating Outputs, ensuring code security and compliance, determining fitness for use, and implementing safeguards before using Outputs in production systems.12. INDEMNIFICATION12.1 Compounds IndemnityCompounds will defend Customer against third party claims alleging that use of the Service infringes United States intellectual property rights. This obligation does not apply to claims arising from Customer Data, modifications by Customer, combinations not provided by Compounds, or use in violation of this Agreement.12.2 Customer IndemnityCustomer will indemnify Compounds from claims arising from Customer Data, violations of laws, use of Outputs, misuse of the Service, or claims related to Customer systems or repositories.13. LIMITATION OF LIABILITYTo the maximum extent permitted by law, neither party is liable for indirect, incidental, consequential, or punitive damages. Compounds is not liable for loss of code, build or deploy failures, security vulnerabilities in Outputs, downtime in Customer systems, or outages in third party services. Compounds total aggregate liability will not exceed the fees paid by Customer in the twelve months preceding the claim.14. TERM, TERMINATION, AND SUSPENSION14.1 TermThe Agreement begins on the Effective Date and continues for the Service Term.14.2 Termination for CauseEither party may terminate for material breach if not cured within thirty days.14.3 Effect of TerminationUpon termination Customer must stop using the Service. Compounds will delete Customer Data according to its retention schedule. Fees already paid are non refundable.15. GOVERNING LAW AND DISPUTE RESOLUTION15.1 Governing LawThis Agreement is governed by the laws of Delaware.15.2 ArbitrationAll disputes will be resolved by binding arbitration in Delaware under JAMS rules.15.3 Injunctive ReliefEither party may seek injunctive relief in court for misuse of intellectual property or confidential information.16. GENERAL TERMSThe Agreement is the entire agreement between the parties. Amendments must be in writing and signed by both parties. Neither party may assign the Agreement without consent except in connection with a merger or acquisition. Notices must be sent to the contacts identified in the Order Form. Any invalid provision will be replaced with an enforceable one that most closely reflects the original intent.