These Developer Terms and Conditions ("Developer Terms") govern your access to and use of the application programming interfaces, developer tools, documentation, software development kits, sandbox environments, webhooks, API credentials, and related materials made available by BuildOps in connection with BuildOps' Services ("API Tools").

By accessing or using the API or any API Tools, you agree to these Developer Terms and Conditions. If you access or use the API or any API Tools on behalf of an entity, you represent that you have authority to bind that entity.

Any capitalized terms not defined in these Developer Terms and Conditions have the meanings set forth in BuildOps' Terms of Service.

"API" means any application programming interface, webhook, developer tool, software development kit, credential, token, documentation, sample code, sandbox, or related material made available by BuildOps.

"Application" means any software, product, service, workflow, connector, integration, automation, AI System, agentic tool, bot, script, or other technology that accesses or uses the API.

"Customer Data" means data, content, or information submitted to, accessed from, processed through, or retrieved from the BuildOps platform through the API.

"Developer," "You," or "Your" means the individual or entity accessing or using the API.

"AI System" means any machine learning, artificial intelligence, generative AI, large language model, autonomous agent, agentic workflow, automated decision system, bot, or similar technology.

"Feedback" means any suggestions, comments, ideas, improvements, or other feedback about the API or BuildOps products provided by Developer to BuildOps.

"Security Incident" means any suspected or confirmed unauthorized access to, use, disclosure, modification, or destruction of Customer Data; any compromise or suspected compromise of API credentials; or any event materially affecting the confidentiality, integrity, or availability of the API.

Subject to these Developer Terms, BuildOps grants you a limited, revocable, non-exclusive, non-transferable, non-sublicensable right to access and use the API solely to develop, test, operate, and support Applications that interoperate with BuildOps' Services in a manner approved by BuildOps.

BuildOps may approve, reject, condition, limit, suspend, disable, revoke, or terminate API access at any time, for any reason or no reason, with or without notice, and without liability. BuildOps reserves the right to immediately suspend or terminate Your Application or API access without notice if you violate these Developer Terms.

You are not permitted to commercialize Your Application or otherwise charge any fees without BuildOps' prior written approval. Doing so will result in immediate termination of Your Application and API access.

You are responsible for all activity conducted using your API keys, tokens, credentials, accounts, or authentication methods.

You must:

● keep API credentials confidential and secure;
● use commercially reasonable security controls to prevent unauthorized access;
● promptly notify BuildOps of any suspected compromise, unauthorized access, or misuse;
● rotate credentials upon request by BuildOps; and
● not sell, transfer, sublicense, share, or disclose API credentials except as expressly approved by BuildOps.

BuildOps may disable, rotate, or require replacement of API credentials at any time.

BuildOps reserves the right, at any time, to introduce or modify fees, usage limits, rate limits, minimum commitments, overage charges, platform charges, integration fees, marketplace fees, revenue share requirements, certification fees, support fees, or other commercial terms applicable to API access or API-enabled integrations.

BuildOps will provide notice of new or modified commercial terms by posting updated terms, sending written notice, or otherwise making the updated terms available to you. Continued access to or use of the API after new or modified commercial terms become effective constitutes acceptance of those terms.

All fees are non-refundable except as expressly stated by BuildOps in writing. BuildOps may suspend or terminate API access for nonpayment or failure to comply with applicable commercial terms.

BuildOps may, at any time and without liability:

● suspend, throttle, rate limit, disable, revoke, or terminate your API access;
● block, reject, or remove any Application;
● require changes to an Application;
● modify, deprecate, replace, or discontinue all or part of the API;
● impose or change technical, security, certification, commercial, or operational requirements;
● restrict API functionality by customer, user, account, region, use case, data type, endpoint, Application, or integration; and
● take any action BuildOps determines is appropriate to protect BuildOps, its customers, users, systems, data, business, partners, or third parties.

You are responsible for designing Applications to account for API changes, downtime, throttling, revocation, and discontinuation.

1. You may not, and may not permit any third party to:

● use the API in violation of law, contract, third-party rights, or BuildOps policies;
● access or use the API in a manner that exceeds authorized scope or permissions;
● reverse engineer, copy, scrape, crawl, harvest, index, benchmark, or monitor the API except as expressly permitted by BuildOps;
● interfere with, disrupt, degrade, or overload BuildOps systems;
● bypass, disable, or circumvent rate limits, access controls, security controls, usage limits, or technical restrictions;
● use the API to create, train, improve, or support a product or service that competes with BuildOps;
● resell, sublicense, commercialize, or make API access available as a standalone service;
● use the API to transmit malware, harmful code, deceptive content, spam, or unlawful material;
● attempt to access the Service by any means other than through the API access provided by BuildOps;
● misrepresent your Application, its functionality, data practices, security posture, or relationship with BuildOps;
● use the API for surveillance, profiling, automated adverse decisions, or high-risk decision-making without BuildOps's prior written approval; or
● remove, obscure, or modify proprietary notices or attribution requirements.

2. During the term and for twelve (12) months following termination or expiration of API access, you will not use BuildOps Confidential Information, Customer Data, or information obtained through the API to solicit, encourage, or assist any BuildOps customer to discontinue, reduce, or migrate their use of BuildOps Services to a competing platform. You will not develop or distribute an Application whose primary purpose is to facilitate the migration of BuildOps customers or their data away from BuildOps.

3. Unless BuildOps provides prior written consent, Developer must not use the API, BuildOps platform, Customer Data, or related data to create or improve:

● benchmarks or industry datasets;
● customer, market, pricing, or competitive intelligence;
● derivative databases or data products;
● competitive analyses; or
● products, features, services, workflows, or functionality that replicate or compete with BuildOps.

These restrictions apply even if the data is aggregated, anonymized, de-identified, transformed, inferred, or combined with other data. In addition, Developer must not permit any third party to engage in these activities.

You are responsible for all access to and use of the API by any AI System, autonomous workflow, bot, script, or agentic tool that you operate, enable, integrate, or permit.

You may not use the API with an AI System unless you maintain appropriate controls for the use case, including:

● clear user authorization for API actions;
● human review for destructive, irreversible, financial, legal, employment, safety related, permission-changing, or externally visible actions;
● rate limits, logging, monitoring, testing, and abuse detection;
● safeguards against prompt injection, data exfiltration, unauthorized tool use, and unintended API calls;
● controls to prevent the AI System from exceeding the user's permissions;
● a practical kill switch or equivalent ability to disable automated API activity quickly; and
● compliance with any AI-specific policies, documentation, or technical requirements published by BuildOps.

You may not use Customer Data, BuildOps data, API responses, API metadata, documentation, or outputs derived from the API to train, fine-tune, improve, or evaluate any AI model or AI System, except to operate the specific authorized Application for the applicable customer's benefit.

Further, you may not:

● generate synthetic data, derivative datasets, or augmented training data from Customer Data, API responses, or API metadata;
● use API data as input to any AI System that produces outputs, predictions, recommendations, or content for third parties other than the applicable authorized customer;
● aggregate, de-identify, or combine data from multiple BuildOps customers as input for any AI System without BuildOps's prior written approval; or
● collect, curate, or assemble API data into training datasets or benchmarks for any AI System.

You may not permit an AI System to:

● impersonate a person or misrepresent whether a person or AI System is taking an action;
● make autonomous decisions that materially affect rights, access, pricing, safety, eligibility, employment, credit, insurance, housing, healthcare, or legal interests;
● initiate transactions, modify records, delete data, change permissions, or communicate externally without authorization and appropriate oversight;
● infer, generate, or expose sensitive personal information except as expressly authorized;
● use API access to discover vulnerabilities, enumerate accounts, or conduct security testing without BuildOps's prior written approval; or
● chain API access with other tools in a manner that expands access beyond the permissions granted by BuildOps.

BuildOps may require you to disclose whether and how your Application uses AI Systems and may condition, restrict, suspend, or prohibit AI or agentic use at any time.

Developer must not disclose Customer Data to an artificial intelligence provider or other subprocessor unless Developer has entered into a binding written agreement with that provider. The agreement must require:

1. use of Customer Data only to provide the Application's authorized services;
2. no training, model improvement, profiling, advertising, or other secondary use;
3. retention only as necessary to provide those services;
4. secure deletion when the data is no longer required;
5. confidentiality obligations protecting Customer Data; and
6. security protections at least as protective as those required under these Terms.

Developer remains responsible for each provider's and subprocessor's acts and omissions.

BuildOps may prohibit or restrict any model, provider, subprocessor, hosting region, or jurisdiction that BuildOps reasonably determines presents legal, security, privacy, operational, or competitive risk. Upon notice, Developer must promptly cease the affected processing and securely delete or migrate the affected Customer Data.

For any Application that uses an autonomous or semi-autonomous system to access the API or take actions, each action must be attributable through the following chain:

Customer → User → Application → Agent → Credential → Action

Developer must maintain tamper-resistant records sufficient to identify each element of this chain. Records must include the action, date and time, authorization, inputs, outputs, affected resources, and outcome.

Developer must implement controls that allow BuildOps to disable any Application, agent, credential, permission scope, Customer installation, webhook, or endpoint. BuildOps may exercise these controls immediately and without prior notice when reasonably necessary to address security, privacy, compliance, misuse, operational, or competitive risks.

Developer must not bypass or interfere with these controls. Developer must promptly cooperate with any suspension, investigation, containment, remediation, or termination directed by BuildOps.

Developer may access or use the API only under valid, current, and documented authorization from each applicable Customer and User. Developer must maintain evidence of that authorization and provide it promptly upon BuildOps' request.

Developer must not access data or perform any action beyond the permissions granted to the authorizing User within the BuildOps platform. Customer authorization does not expand a User's permissions.

Developer must enforce permission changes, revocations, and account restrictions promptly. These requirements apply to all Applications, integrations, automations, agents, and other API uses.

You may access, process, store, use, disclose, and transmit Customer Data only as authorized by the applicable customer and only as necessary to provide the authorized Application.

You must:

● provide clear and accurate notices about your data practices;
● obtain all consents and permissions required by applicable law;
● process Customer Data in accordance with applicable privacy, data protection, and security obligations;
● delete Customer Data upon request by the customer or BuildOps, unless retention is legally required;
● not sell Customer Data;
● not use Customer Data for advertising, profiling, model training, or unrelated analytics without express authorization;
● maintain administrative, technical, and physical safeguards appropriate to the sensitivity of the data;
● segregate Customer Data by customer account so that no customer's data is commingled with another's;
● not cache, store, or retain API responses beyond twenty-four (24) hours, except where longer retention is required for the authorized Application's core functionality and the applicable customer has consented;
● not aggregate, correlate, or combine data from multiple customers for benchmarking, market analysis, competitive intelligence, or any purpose other than serving the individual authorized customer;
● immediately cease all API calls and delete all Customer Data within twenty-four (24) hours when a customer disconnects or deauthorizes your Application; and
● enter into written agreements with any third-party service provider that accesses, processes, stores, or transmits Customer Data or interacts with the API on your behalf, imposing obligations at least as protective as those in these Developer Terms. You must disclose the identity of such service providers to BuildOps upon request.

You must maintain a written information security program appropriate to the nature of your Application and the data accessed through the API.

At a minimum, you must:

● encrypt data in transit (TLS 1.2 or higher) and at rest (AES-256 or higher);
● restrict access based on least privilege, with access reviews performed and documented at least annually;
● maintain access logs and audit trails for no less than twelve (12) months;
● monitor for unauthorized access and anomalous activity;
● perform vulnerability scanning at least quarterly and penetration testing at least annually for production systems;
● complete vulnerability remediation within thirty (30) days (critical), sixty (60) days (high), and ninety (90) days (medium) of discovery;
● maintain secure development practices aligned with an industry-standard framework (e.g., NIST SSDF or OWASP ASVS).

In the event of a Security Incident, you must:

● provide notification to BuildOps within twenty-four (24) hours of discovery of any actual or suspected Security Incident involving the API, Customer Data, or your Application;
● preserve all evidence, logs, and forensic data related to the incident;
● provide regular written updates to BuildOps until the incident is fully resolved;
● cooperate fully with BuildOps's investigation of the incident;
● bear all costs of investigation, notification to affected individuals, remediation, and credit monitoring arising from the incident;
● not make any public statement regarding the incident without BuildOps's prior written approval, except as required by applicable law; and
● implement corrective measures as directed by BuildOps.

BuildOps may require security questionnaires, penetration test summaries, vulnerability scans, remediation plans and evidence of remediation, audit reports (SOC 2, ISO 27001, or equivalent), certifications, access logs and audit trails, or other information to verify compliance with these Developer Terms. You must respond within thirty (30) days of the request.

Failure to respond, or evidence of material non-compliance, is grounds for suspension or termination of API access.

BuildOps may review, test, monitor, audit, or require information about any Application, including its functionality, security, AI use, data flows, privacy practices, user experience, and compliance with these Developer Terms. You must provide information reasonably requested by BuildOps and promptly remediate any issue identified by BuildOps.

Approval of an Application by BuildOps does not waive any right of BuildOps and does not make BuildOps responsible for the Application.

BuildOps may require Applications intended for production use, commercial distribution, or access by multiple customers to undergo a certification process before deployment. Certified Applications may be used only within the scope approved during certification. Any material change to a certified Application requires recertification.

You must maintain complete and accurate records of API usage, data access, and security events for at least seven (7) years. If an audit or review reveals material non-compliance with these Developer Terms, you will reimburse BuildOps for all reasonable costs of the audit, investigation, and remediation. Delay, obstruction, or failure to cooperate with an audit is grounds for immediate suspension or termination of API access and reimbursement of all costs incurred by BuildOps.

You may not use BuildOps's name, logos, trademarks, product names, screenshots, trade dress, or other brand assets without BuildOps's prior written approval. You may not state or imply that BuildOps sponsors, endorses, certifies, recommends, or is affiliated with your Application unless BuildOps expressly authorizes that statement in writing.

BuildOps owns all rights, title, and interest in and to the API, documentation, BuildOps Services, BuildOps data, and related technology. You own your Application, subject to BuildOps's rights in the API and BuildOps Services.

You grant BuildOps a non-exclusive, worldwide, royalty-free license to access, use, reproduce, display, test, and analyze your Application as necessary to operate, secure, support, evaluate, and enforce these Developer Terms.

If you provide suggestions, comments, ideas, improvements, or other feedback about the API or BuildOps products ("Feedback"), you hereby assign to BuildOps all right, title, and interest in and to such Feedback, including all intellectual property rights therein. To the extent any such assignment is not effective under applicable law, you grant BuildOps an irrevocable, perpetual, worldwide, royalty-free, sublicensable, transferable license to use, reproduce, modify, distribute, and commercialize such Feedback without restriction or compensation.

Non-public information disclosed by BuildOps about the API, roadmap, security, customers, pricing, technology, business plans, or commercial terms is BuildOps confidential information. You may use BuildOps confidential information only to exercise rights expressly granted under these Developer Terms and must protect it using at least reasonable care.

The API is provided "as is" and "as available." To the maximum extent permitted by law, BuildOps disclaims all warranties, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, title, non-infringement, availability, accuracy, and uninterrupted or error-free operation.

BuildOps has no obligation to provide support, maintenance, uptime, service levels, error correction, compatibility, roadmap commitments, or continued availability for the API unless expressly agreed in writing.

You will defend, indemnify, and hold harmless BuildOps and its affiliates, officers, directors, employees, agents, customers, and partners from and against all claims, damages, losses, liabilities, costs, and expenses, including reasonable attorneys' fees, arising out of or related to:

● your Application;
● your access to or use of the API;
● your breach of these Developer Terms;
● your violation of law or third-party rights;
● your data practices;
● your AI System, automated workflow, bot, script, or agentic use; or
● any Security Incident, unauthorized access, or misuse involving your systems, credentials, Application, or personnel.

To the maximum extent permitted by law, BuildOps will not be liable for any indirect, incidental, special, consequential, exemplary, punitive, or lost profit damages, or for loss of data, loss of goodwill, business interruption, substitute services, or unauthorized access.

To the maximum extent permitted by law, BuildOps' total aggregate liability arising out of or related to the API or these Developer Terms will not exceed one hundred dollars ($100).

BuildOps may modify these Developer Terms at any time by posting updated terms or otherwise making updated terms available. Updated terms are effective on the date specified by BuildOps. Continued access to or use of the API after the effective date constitutes acceptance of the updated terms.

These Developer Terms supplement any terms of service, subscription agreement, order form, marketplace agreement, partner agreement, developer agreement, data processing agreement, acceptable use policy, privacy policy, or other agreement between you and BuildOps. If there is a conflict, the more protective term for BuildOps controls unless the applicable agreement expressly states that it supersedes these Developer Terms.

Upon suspension, revocation, or termination of API access, you must immediately:

● stop accessing and using the API;
● stop representing that your Application interoperates with BuildOps;
● delete or return Customer Data as required by BuildOps or the applicable customer;
● remove API credentials and BuildOps confidential information from your systems; and
● certify compliance upon request.

Sections intended to survive will survive, including ownership, confidentiality, data deletion, restrictions, indemnification, disclaimers, limitation of liability, and payment obligations.

BuildOps' approval of an Application or API use is personal to Developer. That approval does not transfer through an assignment, sale, merger, acquisition, reorganization, or other material change of control. You may not assign or transfer these Developer Terms, or any rights or obligations hereunder, without BuildOps' prior written consent, and any attempt to do so without BuildOps' written consent is void. BuildOps may reassess, condition, suspend, or revoke API access following the proposed transaction. BuildOps may assign these Developer Terms without restriction.

Failure by BuildOps to enforce any provision of these Developer Terms shall not constitute a waiver of that provision or any other provision.

If any provision of these Developer Terms is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.

These Developer Terms are governed by the laws of the State of California, without regard to conflict of law rules. The courts located in Los Angeles County, California, have exclusive jurisdiction over any dispute arising under or relating to these Developer Terms, unless BuildOps elects another forum to seek injunctive or equitable relief.

Any claim arising under or relating to these Developer Terms must be brought within one (1) year after the cause of action accrues, or the claim is permanently barred.