See What Pactra Delivers

Real analysis outputs across five contract types — from a clean A- NDA to a D+ vendor agreement that needs substantial revision.

All party names, contract values, and identifying details in these examples have been fictionalized to protect confidentiality. Any resemblance to actual companies or agreements is coincidental.

Contract Analyses

Select an example to see the full analysis output — risk findings, missing clauses, drafting quality review, and key facts.

Software License Agreement — CloudSync Technologies

Software License Agreement·Analysis Report·May 28, 2026

C+67/100

Needs attention

Example

3 High4 Medium1 Low

Risk Heat Map

11 findings across 10 pages

No findings1 finding2+ findingsHigh severityClick a section to jump to findings

High RiskMedium RiskLow RiskNo Issues

Executive Summary

This software license agreement between Meridian Corp and CloudSync Technologies contains several provisions that deviate materially from market standards. The limitation of liability is one-sided and inadequate in scope, the auto-renewal window is dangerously narrow, and intellectual property ownership of customizations is ambiguous. The agreement also lacks a data processing addendum despite involving customer data, and the service level commitments carry no meaningful remedies. Seven of eight findings warrant negotiation before signing.

PartiesMeridian Corp ('Customer'); CloudSync Technologies Inc. ('Vendor')

Contract TypeSoftware Licensing Agreement

Governing LawState of California

Effective DateJanuary 15, 2026

Term36 months with automatic annual renewal (expires approximately January 2029)

Total Value$288,000 ($8,000/month)

Payment TermsNet 45, annual escalator of 5% (Payment is due within 45 days of the invoice date)

View as:

Risk Findings(8)

The limitation of liability clause caps Vendor's aggregate liability at fees paid in the prior three months, while Customer's liability is uncapped. For an $8,000/month contract, the Vendor's maximum exposure for any event — including a catastrophic data breach or complete service outage — is approximately $24,000, less than 9% of annual contract value. Customer bears all downside risk above this threshold.

Contract Evidence

"In no event shall Vendor's aggregate liability under this Agreement exceed the fees paid by Customer in the three (3) month period immediately preceding the event giving rise to the claim."
Page 8

"The limitations set forth in this Section shall not apply to Customer's indemnification obligations, payment obligations, or breach of Section 9 (Confidentiality)."
Page 8

Suggested Action

Negotiate for a mutual liability cap at 12 months of fees paid, with carve-outs symmetrically available to both parties for indemnification obligations, data breach, and willful misconduct.

Common Provision

"Contracts of this type commonly include a mutual limitation of liability capping each party's aggregate liability at the total fees paid or payable during the 12-month period preceding the claim. Carve-outs for indemnification, confidentiality breach, and IP infringement are standard and should apply symmetrically to both parties. Consult qualified counsel regarding the specific terms appropriate for your agreement."

The agreement auto-renews annually with only a 30-day window to opt out. This is the minimum possible notice window for a $96,000/year commitment. If the renewal date is not proactively tracked — which is common in organizations without contract lifecycle management systems — the contract automatically renews for a full additional year at escalated pricing.

Contract Evidence

"This Agreement shall automatically renew for successive twelve (12) month terms unless either party provides written notice of non-renewal at least thirty (30) days prior to the expiration of the then-current term."
Page 3

Suggested Action

Negotiate a 90-day opt-out window. Request that Vendor be contractually obligated to send a renewal reminder notice at least 60 days before the renewal date. Consider adding a right to renegotiate pricing upon renewal.

Common Provision

"In similar software agreements, auto-renewal notice periods typically range from 60 to 90 days. Many enterprise agreements include a vendor obligation to send a renewal reminder notice 60-90 days before the renewal deadline. Some jurisdictions have enacted legislation requiring minimum notice periods for automatic renewals in commercial contracts. Consult qualified counsel regarding the specific terms appropriate for your agreement."

The agreement grants Vendor ownership of all 'Modifications and Enhancements' without limiting this to changes to underlying source code. The definition of 'Modifications' is broad enough to capture configurations, data models, workflow templates, and API integrations created by Customer using the platform. Customer-built business logic could be claimed as Vendor IP under this language.

Contract Evidence

"All Modifications, Enhancements, derivative works, and improvements to the Software, whether made by Vendor or Customer, shall be and remain the exclusive property of Vendor."
Page 6

"'Modifications' means any changes, additions, or alterations to the Software or its functionality, including but not limited to configurations, integrations, and customizations."
Page 2

Suggested Action

Narrow the definition of 'Modifications' to mean changes to Vendor's underlying source code only. Explicitly reserve Customer's ownership of its data, configurations, workflow templates, and integrations. Request a license-back of any Customer-funded enhancements that Vendor incorporates into its core product.

Common Provision

"Contracts of this type commonly distinguish between the vendor's pre-existing IP (retained by vendor), customer data and configurations (retained by customer), and jointly developed functionality (typically licensed to customer with perpetual rights). The vendor's ownership claim is typically limited to modifications to its core source code. Consult qualified counsel regarding the specific terms appropriate for your agreement."

Fees increase automatically by 5% on each anniversary with no cap and no right for Customer to terminate if the increase exceeds an acceptable threshold. Over the initial 36-month term, monthly fees escalate from $8,000 to approximately $8,820. Upon renewal, increases can compound indefinitely with no customer protection.

Contract Evidence

"Fees shall increase by five percent (5%) on each anniversary of the Effective Date. Such increases shall apply automatically and shall not require amendment of this Agreement."
Page 4

Suggested Action

Cap annual increases at the lesser of 3% or CPI (Consumer Price Index). Add a termination right if any annual increase exceeds the agreed cap, with a 60-day notice period to allow orderly transition.

Common Provision

"In similar agreements, annual escalators range from 3-5%, often tied to CPI or a stated cap. Many agreements include a right to terminate without penalty if the vendor increases prices by more than a specified percentage above the agreed escalator. Consult qualified counsel regarding the specific terms appropriate for your agreement."

The agreement grants Vendor a license to process Customer Data but contains no data processing addendum, data protection schedule, or obligations regarding security standards, breach notification, sub-processing, or regulatory compliance. If Customer is subject to CCPA, GDPR, or HIPAA-adjacent obligations, this creates both contractual and regulatory exposure.

Contract Evidence

"Customer grants Vendor a non-exclusive license to use, process, and store Customer Data solely for the purpose of providing the Services as described in this Agreement."
Page 5

Suggested Action

Request a Data Processing Addendum that addresses: data categories processed, processing purposes, sub-processor disclosure and notification, breach notification within 48-72 hours, data return and deletion upon termination, and compliance with applicable privacy regulations including CCPA.

Common Provision

"Contracts of this type that involve processing customer data commonly include a Data Processing Addendum (DPA) addressing GDPR and CCPA compliance requirements, sub-processor management, breach notification timelines, data return and deletion procedures, and audit rights. The DPA is typically incorporated by reference into the main agreement. Consult qualified counsel regarding the specific terms appropriate for your agreement."

The agreement references a 99.5% uptime SLA but limits the Customer's sole remedy for any SLA failure to a service credit not exceeding 5% of monthly fees. For an $8,000/month contract, the maximum credit for a complete outage — including one lasting days — is $400. The 'sole remedy' language forecloses all other contractual remedies.

Contract Evidence

"Vendor shall use commercially reasonable efforts to maintain 99.5% availability, measured monthly. In the event of failure to meet the availability commitment, Customer's sole and exclusive remedy shall be a service credit not to exceed five percent (5%) of the monthly fees for the affected month."
Page 7

Suggested Action

Negotiate escalating service credits (e.g., 10% for >99% availability; 25% for >95%; termination right below 95%). Remove the 'sole and exclusive remedy' language to preserve all other contractual remedies in the event of chronic or severe SLA failures.

Common Provision

"In similar software agreements, SLA remedies commonly include tiered service credits that escalate with the severity of the breach, a termination right triggered by chronic or severe availability failures, and preservation of other remedies under the agreement. A 5% single-tier credit is below market standard for material service commitments. Consult qualified counsel regarding the specific terms appropriate for your agreement."

The agreement can only be terminated for uncured material breach. Customer has no right to terminate for convenience during the initial 36-month term, creating a minimum commitment of $288,000 plus annual escalations with no exit right regardless of how well the software performs.

Contract Evidence

"Either party may terminate this Agreement for cause upon thirty (30) days' written notice in the event of a material breach that remains uncured after the expiration of such notice period. No other right to terminate is provided herein."
Page 9

Suggested Action

Negotiate a termination for convenience right with 90-day notice, with or without a reasonable early termination fee (e.g., 3 months' fees). This is standard for multi-year enterprise software agreements.

Common Provision

"Contracts of this type with terms exceeding 12 months commonly include a customer termination for convenience right with 60-90 days' notice. Many agreements include an early termination fee equal to fees payable during the notice period as the price of the option. Consult qualified counsel regarding the specific terms appropriate for your agreement."

The confidentiality section includes a residual knowledge clause allowing Vendor personnel to retain and use in their unaided memory any information learned during the engagement. This effectively creates a broad exception to the NDA obligations for any confidential information that Vendor employees can recall — potentially including pricing strategy, product roadmaps, or technical architecture.

Contract Evidence

"Nothing in this Agreement shall restrict either party's right to use any general knowledge, skills, or experience retained in the unaided memory of its personnel who have had access to the other party's Confidential Information."
Page 10

Suggested Action

Consider whether the residual knowledge exception is acceptable given the sensitivity of information that will be shared. If pricing, roadmaps, or trade secrets will be disclosed, negotiate narrower language that excludes specifically identifiable proprietary information from the exception.

Common Provision

"Residual knowledge clauses are common in technology agreements but are frequently contested. Narrower versions limit the exception to general professional concepts and skills rather than specifically identifiable proprietary business information. Consult qualified counsel regarding the specific terms appropriate for your agreement."

Consistency Issues(2)

Section 11.2 requires parties to follow 'the termination procedures set forth in Section 14.3' but this agreement contains only 12 sections. Section 14.3 does not exist. This is a remnant from a prior template and creates ambiguity about post-termination obligations.

Contract Evidence

"Upon any termination or expiration, the parties shall comply with the termination procedures set forth in Section 14.3 of this Agreement, including the return of Confidential Information and cessation of use of the Software."
Page 9

Suggested Action

Correct the cross-reference to point to the correct section number, or draft the termination procedures directly in Section 11.2 if no dedicated procedure section exists.

CloudSync Technologies Inc. is defined in the preamble and referred to as 'CloudSync' in Sections 1–6, then referred to as 'Provider' in Sections 7–12. This inconsistency creates ambiguity in enforcement as different obligations may be attributed to different party identities.

Contract Evidence

"CloudSync shall deliver and install the Software within thirty (30) days of the Effective Date."
Page 3

"Provider warrants that the Software shall perform substantially in accordance with the Documentation for a period of ninety (90) days from delivery."
Page 7

Suggested Action

Replace all instances of 'Provider' in Sections 7-12 with 'Vendor' (the defined term used in the preamble) to ensure consistent identification of the contracting party throughout.

Drafting Quality Issues(1)

The term 'Customer Data' appears 14 times throughout the agreement — including in the data processing license, confidentiality section, and post-termination obligations — but is never defined. The Definitions section defines 'Confidential Information,' 'Software,' and 'Documentation' but omits 'Customer Data,' creating ambiguity about what data is covered by the processing and ownership provisions.

Contract Evidence

"Customer grants Vendor a non-exclusive license to use, process, and store Customer Data solely for the purpose of providing the Services as described in this Agreement."
Page 5

Suggested Action

Define 'Customer Data' in Section 1 (Definitions) to mean all data, information, and materials submitted by Customer to the Software, including but not limited to personal data, business records, and any other information processed through the Services.

Clauses Not Found(3)

Data Processing Addendum

This agreement involves Vendor processing Customer Data but contains no data protection schedule, DPA, or obligations regarding security standards, breach notification timelines, or sub-processor management. For any customer subject to CCPA, GDPR, or state privacy laws, operating without a DPA may constitute a regulatory compliance failure.

Typical Provision in Similar Contracts

In similar agreements, a Data Processing Addendum typically addresses: categories of personal data processed, processing purposes and legal bases, sub-processor management (with notification of changes), data breach notification within 48-72 hours, data subject rights facilitation, international transfer mechanisms where applicable, data return and deletion upon termination, and audit rights. The DPA is incorporated by reference into the main agreement. Consult qualified counsel regarding the specific terms appropriate for your agreement.

This describes provisions commonly found in similar contracts and is provided for informational purposes only. This is not a recommendation or legal advice. Consult qualified counsel regarding the specific terms appropriate for your agreement.

Dispute Resolution Mechanism

A 36-month, $288,000 agreement with no structured dispute resolution process defaults entirely to litigation. The absence of a tiered dispute resolution clause (executive negotiation → mediation → arbitration) means all disputes proceed directly to court, which is typically the most expensive and least efficient resolution path.

Typical Provision in Similar Contracts

Contracts of this type commonly include a tiered dispute resolution process: first, escalation to senior executives for a 15-30 day negotiation period; then, mediation through a mutually agreed mediator; and finally, binding arbitration or litigation. This structure resolves most commercial disputes before they reach formal proceedings and reduces costs for both parties. Consult qualified counsel regarding the specific terms appropriate for your agreement.

Transition Assistance Upon Termination

If this agreement terminates, Customer has no contractual right to migration assistance, data export, or a post-termination access period. The format, timeline, and scope of data export are unspecified, creating potential data hostage scenarios where Customer cannot access its own data after the license ends.

Typical Provision in Similar Contracts

In similar agreements, transition assistance provisions commonly require the vendor to: provide data export in standard, machine-readable formats within a specified timeframe; offer reasonable migration cooperation for up to 90 days post-termination; maintain read-only access to the platform for data retrieval; and certify deletion of Customer Data after the transition period. Consult qualified counsel regarding the specific terms appropriate for your agreement.

Ready to analyze your own contract?

Upload any contract and get a full analysis in under 90 seconds. Your first analysis is free.

Start Free Analysis →

No credit card required · 1 free analysis included

Contract Comparisons

Upload two versions of a contract and see every meaningful change — which party it favors, how it shifts the risk profile, and the exact language that changed.

NDA Redline

Original mutual NDA vs. counterparty's revised version — 8 substantive changes, 3 material

Example

Change Assessment

Changes favor Party B

3 of 8 changes are material.

Of the 8 changes between versions, 3 are material and all favor the counterparty (Party B). The most significant is the conversion of mutual confidentiality to one-sided protection in Section 2 — your proprietary information would have no contractual protection under the revised terms. The removal of the 2-year term creates an indefinite obligation that may be unenforceable in some jurisdictions but creates ongoing compliance burden in the interim. The $50,000 liquidated damages clause introduces significant financial exposure for any technical breach, without a reciprocal obligation. These changes introduce risk exposure not present in the original. Review with qualified counsel before countersigning.

New Risks Introduced

Your confidential information would have no contractual protection under the revised terms
Indefinite confidentiality obligation with no natural termination mechanism
$50,000 liquidated damages payable per breach solely by the Receiving Party

This assessment summarizes the changes between contract versions and is provided for informational purposes only. It is not legal advice. Consult qualified counsel before countersigning.

ModifiedMaterialSection 2 — Confidentiality Obligations

Changed from a mutual confidentiality obligation to a one-sided structure. Only the counterparty's Confidential Information is now protected. Your confidential information disclosed during the evaluation has no contractual protection under the revised language.

Version A (Original)

Each party agrees to hold in strict confidence all Confidential Information disclosed by the other party and to use such Confidential Information solely for the purpose of evaluating the Proposed Transaction.

Version B (Revised)

The Receiving Party agrees to hold in strict confidence all Confidential Information of the Disclosing Party and to use such Confidential Information solely for the purpose of evaluating the Proposed Transaction.

Favors Party BRisk: Your proprietary information — product roadmaps, pricing, customer data, and technical architecture — shared during the partnership evaluation would receive no contractual confidentiality protection.

RemovedMaterialSection 5 — Term

The 2-year term with automatic expiration has been deleted. The confidentiality obligation now has no stated end date, creating an indefinite commitment that has no natural termination.

Version A (Original)

This Agreement shall remain in effect for a period of two (2) years from the Effective Date, unless earlier terminated in accordance with Section 8.

Version B (Revised)

Removed in Version B

Favors Party BRisk: Creates an indefinite confidentiality obligation. While this may be unenforceable as perpetual in some jurisdictions, it creates ongoing compliance uncertainty and could be used to pursue claims long after the evaluation concludes.

AddedMaterialSection 9 — Remedies

Added a liquidated damages clause of $50,000 per breach, payable solely by the Receiving Party to the Disclosing Party. No reciprocal obligation exists.

Version A (Original)

Not present in Version A

Version B (Revised)

The parties agree that any breach of the confidentiality obligations set forth in Section 2 shall result in liquidated damages of Fifty Thousand Dollars ($50,000) per occurrence, payable by the breaching Receiving Party to the Disclosing Party within thirty (30) days of notice of breach.

Favors Party BRisk: Introduces significant financial exposure — any technical breach of the confidentiality obligation triggers a $50,000 per-occurrence payment obligation, with no reciprocal exposure for the counterparty.

ModifiedModerateSection 3 — Exclusions from Confidential Information

Removed the 'independently developed' exclusion from the definition of what does not constitute Confidential Information. Previously, information you develop independently — even if it happens to resemble the counterparty's information — was excluded. That protection is now gone.

Version A (Original)

Confidential Information does not include information that: (d) is independently developed by the Receiving Party without use of or reference to the Disclosing Party's Confidential Information.

Version B (Revised)

Removed in Version B

Favors Party BRisk: Any information you independently develop that resembles information disclosed by the counterparty could now be claimed as Confidential Information, even if you developed it without reference to the disclosures.

ModifiedModerateSection 4 — Permitted Disclosures

Changed the 'need to know' standard for internal disclosures. Previously, Confidential Information could be shared with employees and contractors who 'need to know' the information. The revised version requires each recipient to execute a separate confidentiality agreement.

Version A (Original)

The Receiving Party may disclose Confidential Information to its employees, officers, directors, and contractors who need to know such information for the purpose of evaluating the Proposed Transaction, provided each such person is informed of the confidential nature of the information.

Version B (Revised)

The Receiving Party may disclose Confidential Information only to those of its employees, officers, directors, and contractors who have executed a written confidentiality agreement with the Receiving Party containing obligations at least as protective as those set forth in this Agreement and who need to know such information for the purpose of evaluating the Proposed Transaction.

Favors Party BRisk: Creates a significant operational burden: every employee or contractor who reviews disclosed materials must execute a separate written agreement. A failure to obtain a signed agreement before sharing creates a technical breach.

AddedModerateSection 6 — Compelled Disclosure

Added a requirement that the Receiving Party provide 15 business days' advance notice before complying with any legal compulsion to disclose Confidential Information, even if such notice is legally prohibited.

Version A (Original)

If required by law to disclose Confidential Information, the Receiving Party shall provide prompt notice to the Disclosing Party prior to such disclosure.

Version B (Revised)

If required by applicable law, regulation, or court order to disclose any Confidential Information, the Receiving Party shall provide at least fifteen (15) business days' advance written notice to the Disclosing Party before complying with such compulsion, regardless of any legal prohibition on such advance notice.

Favors Party BRisk: Could put the Receiving Party in an impossible position: compliance with a court order or subpoena typically cannot be delayed by a private party agreement. Failure to provide 15 days' notice could be characterized as a breach even when legally impossible to comply.

ModifiedMinorSection 10 — Return of Information

Changed the post-termination obligation from 'return or destroy at Receiving Party's election' to 'return or destroy at Disclosing Party's election.' The Receiving Party can no longer choose to certify destruction; it must comply with whichever method the Disclosing Party demands.

Version A (Original)

Upon termination or expiration of this Agreement, the Receiving Party shall promptly return or destroy (at the Receiving Party's election) all Confidential Information of the Disclosing Party.

Version B (Revised)

Upon termination or expiration of this Agreement, the Receiving Party shall promptly return or destroy (at the Disclosing Party's election) all Confidential Information of the Disclosing Party and certify such return or destruction in writing.

Favors Party BRisk: Minor operational impact. Receiving Party loses the ability to certify destruction — a more cost-effective option than locating and physically returning all copies — and must instead comply with counterparty's preference.

ModifiedMinorSection 11 — Governing Law

Changed governing law from Delaware to the counterparty's home jurisdiction. This is a minor tactical change — it makes litigation more convenient for the counterparty and less convenient for you.

Version A (Original)

This Agreement shall be governed by the laws of the State of Delaware, without regard to its conflict of law principles.

Version B (Revised)

This Agreement shall be governed by the laws of the State of New York, without regard to its conflict of law principles.

Favors Party BRisk: Minor impact for most disputes. Could affect litigation costs if a dispute arises — litigating in a different jurisdiction adds travel expense and may require local counsel. Does not materially affect substantive rights.

Example analyses are illustrative only. All findings are AI-generated and do not constitute legal advice.

Compare your own contracts →

Upload two versions of any contract and Pactra will surface every meaningful change in under 60 seconds.

Get Started Free →

No credit card required · Comparison included in free plan