Skip to content
Intro
8 min

Secure Contract Language: What to Ask For

The vendor contract you signed is probably written to protect them, not you. Here's how to fix that.

Last updated: March 20, 2026

You signed a vendor's standard terms of service. You clicked "I agree." Six months later, a breach at that vendor exposed your customer data. When you asked them to pay for notification costs, they pointed to the limitation of liability clause. It says they're not liable for anything.

You signed it. It's enforceable.

This happens constantly. Most small business owners have never read their vendor contracts, let alone negotiated them. That's exactly what vendors are counting on.

What this solves (in real business terms)

Secure contract language defines:

  • What happens to your data if the vendor gets breached
  • Who pays when things go wrong
  • How quickly they have to tell you about problems
  • What your exit looks like when the relationship ends

Without these clauses, you're operating on hope and click-through terms written by lawyers paid to protect the vendor.

What can go wrong

The SaaS vendor bankruptcy. A project management tool went under in 2023. Customers had paid annual subscriptions. None of them got their data back in a usable format. Some lost years of project history. The terms of service said the vendor had no obligation to maintain data access after termination. It was legal.

The indemnification trap. A payment processor's terms said vendors would indemnify them for any claims arising from the customer's use of the service. When a customer got breached and sued both parties, the customer was left holding all liability while the vendor walked away clean.

The unlimited liability clause. Some vendor contracts cap YOUR liability to them at the total fees paid, but leave YOUR liability to your customers unlimited. That's backwards. You need mutual liability caps.

No breach notification = no defense. A marketing platform was breached in 2021. They didn't tell customers for 3 weeks. By then, customers had received phishing emails using data from the breach. The customers sued the businesses, not the platform. The businesses had no indemnification rights because the contract didn't require prompt notification.

What it costs (honest ranges)

| What | What you'll pay | |------|----------------| | Review by a business attorney (per contract) | $500–$2,000 | | Custom MSA (Master Service Agreement) | $2,000–$8,000 | | Negotiation support for major vendor contracts | $1,000–$5,000 | | Standard DPA template (boilerplate protection) | $200–$1,000 | | Full contract overhaul with privacy counsel | $10,000–$30,000 |

For most SMBs: focus on your 3–5 most critical vendor contracts and spend real money on those. Accept boilerplate for the rest.

Minimum viable implementation

  1. Identify your critical contracts. Which vendors touch customer data, process payments, or hold data you couldn't recreate? Those are the ones that need attention.

  2. Request the actual agreement. Not the click-through TOS. Ask for the "Master Service Agreement" or "Subscription Agreement." Most vendors have these.

  3. Negotiate these specific clauses:

Data security obligations: "Vendor shall maintain security measures consistent with [NIST CSF, SOC 2, ISO 27001] and shall provide evidence of compliance upon request."

Breach notification: "Vendor shall notify Customer within 72 hours of discovering a breach affecting Customer data."

Liability caps (mutual): "Neither party's liability shall exceed [2x annual fees / $100,000] for any claim arising from this agreement."

Indemnification: "Vendor shall indemnify Customer against third-party claims arising from Vendor's negligence or breach of this agreement."

Data return and deletion: "Upon termination, Vendor shall return all Customer data within 30 days and delete all copies within 60 days, certifying deletion in writing."

  1. Sign the DPA separately. Your DPA should be a standalone agreement, not buried in a 40-page MSA.

  2. Document your negotiations. If a vendor refuses a clause, note it. You may decide the relationship isn't worth the risk.

Vendor questions (copy/paste)

When negotiating contracts with vendors who handle customer data:

  1. "What security certifications do you have? Can you provide your latest SOC 2 Type II report?"

  2. "What's your breach notification process and timeline? What information will you provide?"

  3. "What's your liability cap? Is it mutual and symmetric?"

  4. "If we terminate this agreement, what happens to our data? What's the timeline for return and deletion?"

  5. "Do you subprocessor our data? What's your process for adding new subprocessors?"

  6. "What happens to this agreement if your company is acquired?"

  7. "Will you allow us to conduct a security assessment or penetration test on your environment?"

When to hire help

Hire a lawyer if:

  • You're negotiating a contract over $50,000/year
  • The vendor handles payment card data (PCI DSS requires specific contractual terms)
  • You're in healthcare and the vendor handles PHI (HIPAA BAA requirements)
  • You're sharing data internationally (GDPR Standard Contractual Clauses)
  • You've been breached and the vendor is refusing to cooperate

Pro tip: the best time to negotiate contract terms is before you sign. The worst time is after you've been breached.

Related Reading

Need Help Implementing This?

If you'd like guidance tailored to your specific infrastructure, we offer focused consultations. No sales pressure, just practical next steps.

Get in Touch