These CRIBL DEVELOPER TERMS (“Terms”) form a binding agreement between you individually or the business entity or public agency on whose behalf you are accepting these Terms (“Developer” or “you”) and Cribl, Inc. (“Cribl” or “we”) on the date Developer first indicates acceptance of these Terms by: (1) clicking “submit,” “accept,” or by similar online action as may be offered in a Cribl web or in-application form; or (2) accessing or using any portion of the Cribl Materials, as defined below, (“Effective Date”).
DEFINITIONS
1.1 – ”Content” means any application, connector, integration, extension, workflow, plug-in, software module, content, service, API integration, agent or other product that Developer submits to, lists on, distributes through, or makes available in connection with the Marketplace or the Cribl Materials.
1.2 – “Cribl Certified App” means Content that is certified by Cribl as meeting its standards for compatibility, performance, reliability, security remediation, support, and any other requirements listed in the applicable Documentation.
1.3 – “Cribl Materials” means the Subscription Services, APIs, SDKs, Documentation, developer tools, sandbox environments, trademarks, logos, sample code, Marketplace assets, and other materials made available by Cribl to Developer.
1.4 – “Customer” means an individual, business entity, or public agency who has subscribed to the Subscription Services and installs, accesses, purchases, enables, or uses Content.
1.5 – “Customer Data” means telemetry data processed in the Subscription Services by or for Customer.
1.6 – “Developer Terms” means any end user terms, privacy notices, support terms, Documentation, or other terms relating to Content, between Developer and Customers.
1.7 – “Documentation” means the then-current product documentation published by Cribl at https://docs.cribl.io/ as may be updated from time to time. Documentation may include, without limitation, Marketplace policies, developer guidelines, brand guidelines, API terms, security requirements, data-processing requirements, acceptable use policies, and Content listing requirements.
1.8 – “Intellectual Property Rights” or “IPR” means all intellectual property and proprietary rights worldwide, including patent, trademark, service mark, copyright, trade secret, know-how, moral right, and any other intellectual and intangible property rights, and all continuations, continuations in part, applications, renewals, and extensions of any of the foregoing.
1.9 – “Law” means any applicable law, rule, statute, decree, decision, order, regulation, judgment, code and requirement of any government authority (federal, state, local, or international) having jurisdiction.
1.10 – “Marketplace” means Cribl’s marketplace, app or pack store, exchange, catalog, directory, or other program through which Content may be submitted, reviewed, listed, promoted, purchased, installed, enabled, or used.
1.11 – “Subscription Services” means the certain Cribl offerings to which Customer has subscribed in an applicable Order Form, such as Cribl’s self-hosted software or software-as-a-service cloud offering.CONTENT SUBMISSION, REVIEW, AND LISTING
2.1 – Application and Approval. Developer must apply for and be approved by Cribl before participating in the Marketplace, subject to these Terms and the Documentation. Cribl may approve, reject, condition, suspend, or terminate Developer’s participation in the Marketplace at any time in its discretion.
2.2 – Review Rights. Cribl may review, test, scan, audit, monitor, or evaluate Developer Content for security, privacy, quality, performance, interoperability, legal compliance, user experience, and policy compliance. Approval of Content does not constitute certification, endorsement, warranty, or acceptance of liability by Cribl.
2.3 – Non-Exclusivity and Independent Development. Unless otherwise agreed in writing, these Terms are non-exclusive. Nothing in these Terms restricts Cribl from developing, acquiring, licensing, offering, marketing, promoting, or distributing products, services, features, integrations, apps, or marketplaces that are similar to, interoperable with, or competitive with any Content.LICENSE AND RESTRICTIONS
3.1 – License Grant. Subject to these Terms, Cribl grants Developer a limited, non-exclusive, non-transferable, non-sublicensable, revocable license during the Term (as defined below) to copy, modify, and use the Cribl Materials solely to develop, test, submit, support, maintain, and operate approved Content in connection with the Marketplace and in accordance with the Documentation.
3.2 – Restrictions. Developer must not: (a) reverse engineer, decompile, disassemble, or attempt to derive the source code or underlying structure of the Cribl Materials; (b) access or use the Cribl Materials to build a competing platform or marketplace; (c) exceed documented API limits or circumvent technical restrictions; (d) interfere with performance, security, or integrity of Cribl Materials; (e) scrape, harvest, or extract data except as expressly permitted; (f) use Cribl Materials for benchmarking, competitive analysis, or publication of performance information without Cribl’s prior written consent; (g) remove or obscure proprietary notices; or (h) use Cribl Materials except as expressly permitted by these Terms.
3.3 – Changes to Cribl Materials. Cribl will provide support for the Cribl Materials and Marketplace as described in the Documentation. Cribl may modify, suspend, or discontinue Cribl Materials or Marketplace functionality at any time. Cribl will use commercially reasonable efforts to provide advance notice of material changes where practicable, but Cribl is not liable for the effect of such changes on any Content. Developer must keep its Content current, secure, compatible with the Cribl Materials, and compliant with these Terms and the then-current Documentation.DEVELOPER RESPONSIBILITIES
4.1 – Generally. Without limiting any obligations in these Terms, Developer is solely responsible for managing its relationships with Customers and for the Content’s development, functionality, performance, security, compliance and support. Developer may offer, distribute, and provide its Content to Customers under its own license terms, subject to any restrictions that govern Developer’s use of the Cribl Materials. Developer’s license is solely between Developer and its Customer, and Developer’s Content license terms may not make any representations about or impose obligations on Cribl.
4.2 – Representations and Warranties. Developer represents and warrants that: (a) it has full power and authority to enter into and perform the rights and obligations under these Terms and to provide the Content without violating any other agreement; (b) its use of the Cribl Materials and its Content will comply with all applicable Law; (c) its use of the Cribl Materials and the Content will comply with applicable Documentation; and (d) it will comply with any restrictions or requirements for third-party software (including any open source libraries) identified in the Cribl Materials.
4.3 – Prohibited Content and Conduct. Developer must not submit or operate any Content that: (a) infringes any IPR, or violates any privacy rights or applicable Law; (b) is deceptive, fraudulent, harmful, or abusive; (c) enables surveillance, stalking, discrimination, harassment, or unlawful profiling; (d) circumvents Cribl Materials permissions, billing, security, or access controls; (e) transmits unsolicited communications; (f) includes misleading claims, fake reviews, or undisclosed endorsements; (g) creates unreasonable load on the Cribl Materials; (h) collects data unrelated to disclosed functionality; (i) enables unauthorized scraping, extraction, or resale of data; or (j) is otherwise prohibited by these Terms, including the Documentation.
4.4 – Customer Privacy. A Customer may enable you or your Content to access certain Customer Data. You may access and process Customer Data only to the extent enabled by the Customer and as necessary to provide your Content to that Customer. You acknowledge that Cribl processes data on behalf of, and under the instruction of, its Customers and is not responsible for the accuracy, quality, legality, privacy, security, or integrity of any Customer Data shared with by a Customer and processed by you or your Content. To the extent you or your Content processes Customer Data, you do so as an independent party directly for the Customer, and not as a delegate, service provider, or downstream processor of Cribl. You agree that all Customer Data processed by you or your Content shall be used in accordance with: (a) these Developer Terms, (b) applicable law, regulations, or court orders, and (c) any written instructions or requests imposed by Customers or Cribl. You represent and warrant that you (a) have obtained all necessary authorizations, notices, and consents to lawfully receive and process Customer Data; (b) will notify Customers prior to their use of your Content that Cribl is not responsible for the privacy, security, or integrity of the Customer Data processed by you or in connection with your Content; (c) to the extent permitted by applicable Law, will notify Cribl without undue delay if you receive any request, inquiry, or correspondence from a regulator or government authority in relation to Customer Data or if you become reasonably aware of any data protection concerns associated with your Content.
4.5 – Cribl Certified Apps. Cribl Certified Apps receive a certification badge from Cribl. Cribl Certified Apps must comply with these Terms and adhere to the specific requirements and responsibilities, including without limitation support and security obligations, outlined in the Documentation. For the avoidance of doubt, Cribl does not have any obligations whatsoever with respect to Cribl Certified Apps.SECURITY REQUIREMENTS
5.1 – Generally. Developer must (a) use industry-standard technical, administrative, and physical security measures appropriate to protect Customer Data from any security incidents, including unauthorized or unlawful access, or destruction loss, theft, alteration, disclosure or acquisition, and (b) comply with any security, coding practices, authentication, encryption, or other requirements for its Content in the Marketplace as described in the applicable Documentation. Developer agrees to remediate all security vulnerabilities identified to Developer by Cribl within the timeframes ascribed by Cribl.
5.2 – Security Incidents. Developer must notify Cribl without undue delay, and in any event within 48 hours, after confirming any unauthorized access to, disclosure of, loss of, compromise of, or breach affecting Customer Data, Content, or Cribl Materials, including any credentials used with the Cribl Materials. To the extent available, such notification must include, without limitation, any requirements prescribed in the Documentation in addition to the following basic information: (a) the nature and details of the incident; (b) categories of data impacted; (c) approximate numbers of affected individuals or data records (whichever is applicable); (d) name and contact details of a contact point; (e) likely consequences of the incident; (f) remedial measures already taken or planned. Developer must cooperate with Cribl’s investigation, mitigation, remediation, notice, and Customer communications.
5.3 – No Malicious Code. Developer must not introduce malware, spyware, ransomware, backdoors, time bombs, logic bombs, credential harvesters, unauthorized tracking mechanisms, or other harmful code.INTELLECTUAL PROPERTY
6.1 – Ownership. You retain ownership to your Content, and Cribl retains ownership to all of the Cribl Materials or any other technology provided by Cribl under these Terms (including associated goodwill). Except as expressly granted in these Terms, neither party has any right of any kind in the other party’s IPR.
6.2 – License to Cribl. Developer grants Cribl a non-exclusive, worldwide, fully paid-up, royalty-free, sublicensable license in its Content to host, reproduce, display, distribute, make available, test, scan, promote, market, and otherwise use the Content, Developer name, logos, screenshots, descriptions, documentation, metadata, and related materials as necessary or useful to operate, promote, secure, and administer the Content in the Marketplace during the Term.
6.3 – Feedback. Notwithstanding anything to the contrary, if Developer provides Cribl with bug reports, suggestions, or other feedback with respect to Cribl Materials, then Cribl has the irrevocable right to exercise all rights in such Feedback without restriction or compensation to Developer.BRANDING AND MARKETING
7.1 – Brand Use. Developer may use Cribl trademarks only as permitted by Cribl’s brand guidelines and solely to identify compatibility with the Cribl Materials. Cribl may revoke brand-use permission at any time. Cribl may identify Developer and is Content in the Marketplace and in related marketing materials.
7.2 – No Endorsement. Developer must not state or imply that Cribl endorses, certifies, guarantees, sponsors, or is responsible for any Content unless Cribl expressly authorizes the statement in writing.CONFIDENTIALITY
8.1 – Definition. "Confidential Information" means non-public elements of the Cribl Materials and any other information disclosed by Cribl that is marked as confidential or proprietary or that you should reasonably understand to be confidential or proprietary. Confidential Information does not include any information that: (a) is or becomes generally known to the public; (b) was known to you before its disclosure hereunder; or (c) is received from a third party, in each case without breach of an obligation owed to Cribl or anyone else.
8.2 – Rights and Obligations. You will (i) maintain Confidential Information in confidence (using at least the same measures as for your own confidential information, and no less than reasonable care) and not divulge it to any third party, and (ii) only use Confidential Information to fulfill your obligations under these Terms. If you are compelled by law to disclose Confidential Information, you must provide Cribl with prior notice of such compelled disclosure (to the extent legally permitted) and reasonable assistance, at Cribl’s cost, if Cribl wishes to contest the disclosure. In the event of actual or threatened breach of this section, Cribl shall have the right, in addition to any other remedies available to it, to seek injunctive relief to protect its Confidential Information, it being specifically acknowledged by the parties that other available remedies may be inadequate.WARRANTY DISCLAIMER. Cribl provides the Cribl Materials and Documentation “as is” and “as available”. To the maximum extent permitted by law, Cribl disclaims all warranties, express, implied, statutory, or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, availability, and error-free operation.
INDEMNIFICATION
10.1 – Developer Indemnity. Developer will defend Cribl against any claim by a third party arising from or relating to: (a) its Content, (b) Developer’s breach of these Terms, or (c) Developer’s access to, use of, or disclosure of Customer Data, and Developer will indemnify Cribl for any damages and costs finally awarded against Cribl or agreed in settlement by Developer (including reasonable attorneys’ fees) resulting from such claim.
10.2 – Process. Developer’s duty to defend is subject to Cribl (a) providing prompt notice of any actual or threatened claim; and (b) cooperating and, at Developer’s reasonable request and expense, assisting in such defense. Developer will not stipulate, acknowledge, or admit fault or liability on Cribl’s part without prior written consent. Cribl may, at its own expense, participate in the defense and settlement of any claim with its own counsel.LIMITATION OF LIABILITY. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CRIBL’S TOTAL, CUMULATIVE LIABILITY IN ANY WAY ARISING OUT OF OR RELATED TO THESE TERMS WILL BE LIMITED TO $500, AND IN NO EVENT WILL CRIBL BE LIABLE FOR ANY INCIDENTAL, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL, OR EXEMPLARY DAMAGES, INCLUDING LOST PROFITS OR LOSS OF BUSINESS OR REPUTATION, EVEN IF DEVELOPER HAS BEEN ADVISED OF SUCH DAMAGES IN ADVANCE OR SUCH DAMAGES WERE FORESEEABLE; PROVIDED, HOWEVER, THAT THE FOREGOING LIMITATIONS AND EXCLUSIONS DO NOT APPLY TO: (A) DEVELOPER’S OBLIGATIONS UNDER SECTION 10 (INDEMNIFICATION); (B) INFRINGEMENT OR MISAPPROPRIATION BY DEVELOPER OF CRIBL’S IPR; OR (C) TORT ACTIONS FOR A PARTY’S GROSS NEGLIGENCE OR WILLFUL MISCONDUCT, SEPARATE AND DISTINCT FROM AN ACTION FOR BREACH OF THESE TERMS.
SUSPENSION, DELISTING, AND TERMINATION
12.1 – Term. These Terms begin on the Effective Date and continue until terminated (the “Term”).
12.2 – Termination by Developer. You may terminate these Terms at any time by ceasing all use of the Cribl Materials and any relevant developer credentials.
12.3 – Termination or Suspension by Cribl. Cribl may immediately suspend Developer’s account, disable API access, delist Content, or terminate these Terms if: (a) Developer breaches these Terms or the Documentation; (b) Content creates or may create security, privacy, legal, operational, reputational, customer, or other risk to Cribl Materials; (c) Developer fails to remediate issues; (d) Developer becomes insolvent or ceases business; (e) required by applicable Law; or (f) Cribl discontinues the Marketplace or relevant functionality.
12.4 – Effect of Termination. Upon termination, Developer must stop using Cribl Materials, cease representing participation in the Marketplace, delete or return Customer Data as required, continue to support existing Customers during any required wind-down period, and comply with Cribl’s transition instructions.
12.5 – Survival. Sections relating to ownership, data restrictions, confidentiality, warranties, indemnification, limitation of liability, termination effects, records, audit, dispute resolution, and any provisions that by their nature should survive will survive termination.GOVERNING LAW. These Terms are governed by the Laws of California, USA, without regard to its conflict of laws principles. Any disputes arising out of or related to these Terms will be heard only in a federal or state court in San Francisco County, California. The parties irrevocably consent to the jurisdiction of, and venue in, such courts and waive any objection that such courts are an inconvenient forum. For U.S. Government Customers, any disputes arising out of or related to these Terms will be governed by applicable federal law.
MODIFICATIONS. Cribl may modify these Terms, including the Documentation, from time to time. Continued participation in the Marketplace after the effective date of modifications constitutes acceptance. If Developer does not agree to modifications, Developer must stop participating in the Marketplace and terminate these Terms. Cribl may provide notices through the developer portal, email, Marketplace dashboard, or other reasonable electronic means.
MISCELLANEOUS. These Terms are the entire agreement between the Parties regarding its subject matter and supersede prior or contemporaneous agreements on that subject. If any provision is unenforceable, the remaining provisions remain in effect. The parties are independent contractors, and nothing in these Terms will be construed to create a partnership, joint venture, agency, or other relationship.
