CommitPath AI Service Level Agreement

Fortis Logic LLC doing business as CommitPath AI

Version 1.3 • Effective October 26, 2026

1 Applicability and Acceptance

This Service Level Agreement (SLA) establishes an availability commitment and service credits for the paid production CommitPath AI platform supplied by Fortis Logic LLC, doing business as CommitPath AI (Provider), to Customer under the parties’ SaaS subscription agreement (Agreement). Capitalized terms not defined here have the meanings given in the Agreement.

This SLA applies only when expressly incorporated into an Order Form or an amendment accepted by both parties, including by electronic signature or an affirmative website acceptance process that identifies and provides access to this version of the SLA. Its effective date is the later of that acceptance and the paid subscription start date. Free trials, beta features, previews and separately scoped professional services are excluded.

An expressly agreed Order Form override controls over this SLA; this SLA otherwise controls solely for availability measurement, maintenance exclusions and uptime credits. The Agreement governs all other matters. This SLA does not create a support response time guarantee.

2 Monthly Availability Commitment

Provider will make the Covered Functions available at least 99.9% of Eligible Minutes during each calendar month. Calendar months and incident timestamps are measured in Pacific Time (America/Los_Angeles). Coverage applies only during Customer’s active paid subscription within that month.

Covered Functions are: (a) reaching the CommitPath AI web application and signing in; and (b) the CommitPath AI service that stores and returns Customer’s deal records, including its database.

CommitPath AI features — call and transcript analysis, coaching, close plans, follow-up drafts and other AI-generated outputs — and the receipt of recordings from connected meeting services are not Covered Functions. Provider will report a platform-wide AI outage on its status page, but its duration is not Downtime under this SLA.

3 Downtime

Downtime is a period during which the Covered Functions are unavailable to users generally, as determined under Section 4, lasting at least five consecutive minutes. Once that threshold is met, the entire period counts, including the first five minutes. A failure affecting only one user does not count unless it is caused by a platform failure rather than that user’s device, network, credentials or permissions.

4 Measurement

Provider measures availability with independent external monitoring that checks each Covered Function from multiple geographic regions at intervals of no more than three minutes. Downtime begins at the first failed check that the monitoring confirms as an outage and ends at the first successful check after it. Provider’s monitoring record is the primary record of availability and will be supplied to Customer with any claim decision.

The monitoring observes the platform as a whole. If Customer experiences a failure of a Covered Function that the monitoring did not record, Customer may supply reasonably available evidence of it, such as times, screenshots and error messages, and Provider will consider it in good faith together with its application logs. Customer need not supply internal technical logs it cannot access.

Eligible Minutes = minutes in Customer’s active paid subscription during the calendar month, minus periods excluded under Sections 5 and 6. Monthly Uptime Percentage = 100 × (Eligible Minutes − Downtime minutes) ÷ Eligible Minutes. Calculations use unrounded values to determine credit eligibility. If there are no Eligible Minutes, no credit is due. Downtime that crosses a month boundary is apportioned to each affected month.

Provider publishes current status and past incidents at its status page, currently https://commitpath-ai.betteruptime.com.

5 Scheduled and Emergency Maintenance

Scheduled maintenance is excluded only if Provider gives at least 48 hours’ advance notice by email to Customer’s account administrators, schedules the work between 10:00 p.m. and 4:00 a.m. America/Los_Angeles time, and limits excluded maintenance to 120 minutes per calendar month. The notice will identify the planned start, duration and affected functions.

Only actual unavailability during compliant maintenance is excluded. Time outside the notified window, outside the stated overnight hours, without sufficient notice, or beyond the monthly allowance is evaluated as Downtime under Section 3. Emergency maintenance to address a security vulnerability or prevent data loss is excluded for up to 60 minutes per calendar month if Provider posts it on the status page when it begins; beyond that it counts when it meets the Downtime definition.

6 Other Exclusions

Unavailability is excluded to the extent caused by including but not limited to: Customer’s devices or internet connection; Customer-controlled credentials, permissions, configurations or unauthorized modifications; unsupported inputs; use exceeding disclosed contractual allowances or limits; a suspension expressly permitted by the Agreement and not caused by Provider’s breach; or events beyond Provider’s reasonable control as described in Section 13 of the Agreement, excluding failures that required safeguards would reasonably have prevented. Provider must reasonably substantiate the cause and duration of an exclusion.

An outage of a Customer-connected third-party service — such as a meeting, calendar, mail, messaging or CRM service — is excluded where the Covered Functions remain available. Failures of Provider’s own hosting and database providers are not excluded merely because a third party caused them.

7 Service Credits

If Monthly Uptime Percentage falls below 99.9%, Customer may claim the following credit. Apply only the single highest applicable tier; tiers are not cumulative.

Below 99.9% and at least 99.0%: 10% of the Monthly Fee.

Below 99.0% and at least 95.0%: 25% of the Monthly Fee.

Below 95.0%: 50% of the Monthly Fee.

Monthly Fee means the recurring subscription fees attributable to Customer’s account for the affected calendar month, after contractual discounts and adjustments, excluding taxes, one-time fees, professional services and third-party pass-through charges. Annual prepaid fees are divided by 12; partial months are prorated to the covered subscription period.

Credits under this SLA cannot exceed 50% of the Monthly Fee for the affected month. Credits apply to future subscription invoices or renewal charges, have no cash value and are not transferable. Approved unused credits remain available while Customer’s subscription continues and expire when it ends, except as required by law. Credits do not reduce a separate refund expressly due under the Agreement, and the same fees will not be recovered twice for the same loss.

8 Claim and Review Process

Customer must email support@commitpath.ai within 30 calendar days after the affected calendar month ends, with the subject “SLA Credit Request,” its account name and administrator email, approximate incident dates and times with time zone, and a description of the affected functions. Screenshots or other reasonably available evidence are optional; reporting an incident while it occurs is encouraged but is not a condition of eligibility.

Provider will acknowledge the request within five business days and approve it or explain the denial, with its monitoring record for the period, within 15 business days after receiving sufficient account and incident information. Business days are Monday through Friday, excluding US federal holidays. A timely claim remains timely while reasonable clarifications are being supplied. Customer may request reconsideration within 15 calendar days after denial. Approved credits will appear on the next practicable invoice or renewal charge.

9 Remedies and Changes

To the extent permitted by law, the credits in this SLA are Customer’s exclusive monetary remedy solely for failure to meet the 99.9% availability commitment. They do not limit rights concerning an independent breach of confidentiality, security, privacy or another Agreement obligation, or termination and associated refunds expressly available under the Agreement. The Agreement’s liability limitations and dispute provisions continue to apply.

This SLA version remains applicable during the current paid subscription term. Changes that materially reduce coverage or remedies require at least 30 days’ advance written notice and take effect only at a subsequent renewal after that notice period; Customer may decline renewal under the Agreement. Any stricter amendment requirements in the Agreement control.