mintlify__docs/enterprise-contracting.mdx

---
title: "Enterprise contracting"
description: "How Mintlify approaches enterprise legal review, Master Service Agreement (MSA) negotiations, security questionnaires, and procurement so you know what to expect when buying."
hidden: true
---

A legal issue is almost always first a satisfaction issue. We believe the best legal department is a satisfied customer.

That means we say yes whenever we can, move quickly, and only hold firm on the small number of things that keep the platform working for everyone.

This page explains what those things are—and what's genuinely open for discussion.

## What to expect

All Mintlify Enterprise agreements go through legal review. Our goal is execution in under three business days.

<Steps>
  <Step title="Day 1 — Review">
    We review your redlines and assess each against our standard positions.
  </Step>
  <Step title="Day 2 — Align">
    We come back with responses on every open item. We bring solutions, not walls.
  </Step>
  <Step title="Day 3 — Execute">
    Final document signed and deal closed.
  </Step>
</Steps>

## What we're flexible on

Most of what procurement teams ask for, we try to accommodate.

- Custom service-level agreements
- Security certifications (Service Organization Control (SOC) 2 Type II, ISO 27001, Digital Operational Resilience Act (DORA))
- Data Processing Agreements
- Liability caps
- Indemnification scope
- Governing law and jurisdiction
- Insurance requirements
- Auto-renewal opt-outs
- Audit rights

## Six fixed positions

These are structural to how the platform operates. We'll explain each one—not to justify ourselves, but because understanding the reason usually resolves the concern.

<AccordionGroup>
  <Accordion title="1. Platform IP ownership">
    **Our position:** Mintlify owns all platform code, features, and methods.
    Customers own all of their content and data.

    **Why:** Mintlify is a multi-tenant platform serving thousands of customers. If any customer could claim ownership over platform features, we couldn't offer those features to anyone else and the platform would stop improving. We want Mintlify to get better over time, not worse.

    **What this means for you:** Your content, your data, and your documentation output are entirely yours. We make no claim on any of it.
  </Accordion>

  <Accordion title="2. Aggregate data for product analytics">
    **Our position:** Mintlify may use de-identified, aggregated usage data (feature usage, performance metrics, search patterns) for product analytics and improvement.

    **Why:** Understanding how features perform across the platform is how we know what to build and how to optimize. Without usage patterns, we're flying blind—and so are you when you rely on us to keep improving.

    **What this means for you:** We analyze aggregate signals, not your content. Your specific documentation, your users' data, and any identifiable information are never surfaced or shared.
  </Accordion>

  <Accordion title="3. Capped liability">
    **Our position:** Standard cap is 12 months of fees. For large deals, we go higher. We do not accept unlimited liability.

    **Why:** Uncapped exposure makes us uninsurable, which means we'd have to price for worst-case scenarios or decline customer relationships entirely. Neither outcome serves you.

    **What this means for you:** We accept a 2x annual fees super-cap for the categories that matter most: confidentiality breaches, data security incidents, and IP indemnification. We feel this is fair for elevated risk categories, and it's backed by insurance.
  </Accordion>

  <Accordion title="4. No sublicensing">
    **Our position:** Customers may not resell or redistribute platform access.

    **Why:** Our security model, pricing, and support commitments are built around direct relationships with known customers. Sublicensing creates distribution we can't monitor, secure, or support.

    **What this means for you:** Affiliate use within your corporate family—subsidiaries, related entities, M&A scenarios—is fully accommodated under standard enterprise terms.
  </Accordion>

  <Accordion title="5. Warranty limitations">
    **Our position:** We warrant platform uptime per our SLA. We provide everything else on standard "as-is" SaaS terms.

    **Why:** We use third-party LLM providers whose output we can't warrant. No software company can guarantee outcomes that depend on customer data, use cases, or third-party integrations.

    **What this means for you:** We will warrant in writing that our LLM providers are contractually prohibited from using your data for model training or improvement—which is the protection that actually matters.
  </Accordion>

  <Accordion title="6. No termination for convenience">
    **Our position:** Either party may end the agreement for material breach with a 30-day cure period.

    **Why:** A unilateral walk right eliminates the economic basis for our pricing.

    **What this means for you:** Our SLA structure provides credits back to you in the unlikely event of service issues. Where there is an actual breach without cure, termination is available. We won't lock customers into bad situations—we just need a mutual commitment to justify the investment on both sides.
  </Accordion>
</AccordionGroup>

## Questions

Reach out to your account executive or contact us at [legal@mintlify.com](mailto:legal@mintlify.com).

Our standard terms and compliance documentation are available at [mintlify.com/legal/terms](https://www.mintlify.com/legal/terms) and [security.mintlify.com](https://security.mintlify.com).