Service Level Agreement

Effective date: July 8, 2026

This Service Level Agreement ("SLA") describes NoThirdParty AI's commitments regarding availability, support response times, and remedies for the Service, as provided to Client under the applicable Terms of Service and order form. It does not cover the Excluded Events listed in Section 6.

The Service runs on infrastructure that NoThirdParty AI owns and operates directly, rather than on a cloud provider's redundant, multi-region infrastructure, consistent with the Service's core privacy guarantee that Client data never leaves infrastructure NoThirdParty AI controls. See Section 8 for additional detail on business continuity.

1. Definitions

• Uptime — the Service is reachable and able to process a chat request end-to-end.
• Downtime — any period during which the Service is not reachable or unable to process requests, excluding Excluded Events (Section 6).
• Monthly Uptime Percentage — total minutes in the calendar month, minus Downtime minutes, divided by total minutes in the month.
• Scheduled Maintenance — planned downtime communicated to Client at least 48 hours in advance.

2. Uptime Commitment

All clients run on shared underlying infrastructure (isolated per-client at the application and data layer via separate containers and storage, but sharing the same physical server, network path, and host OS). Because uptime for the underlying infrastructure is not something that varies by client, we commit to a single Monthly Uptime Target for all clients rather than differentiated tiers:

Monthly Uptime Target
99.0% (~7.3 hrs downtime/month)

3. Service Credits

If Monthly Uptime Percentage falls below the committed target, Client may request a service credit as follows:

Monthly Uptime Percentage	Service Credit
Below target, down to 95%	10% of that month's fees
Below 95%, down to 90%	25% of that month's fees
Below 90%	50% of that month's fees

To claim a credit, Client must submit a request to [email protected] within 30 days of the end of the affected month, including the dates and times of Downtime experienced. Credits are Client's sole and exclusive remedy for failure to meet the Uptime Commitment. Credits are applied to a future invoice and are not redeemable for cash.

4. Support

Severity	Definition	Target initial response
Critical	Service completely unreachable for Client	4 hours, during business hours; best-effort outside business hours
High	Major feature unavailable or badly degraded	1 business day
Normal	Minor issue, question, or non-urgent request	2 business days

"Business hours" means 9am–6pm Central Time, Monday–Friday, excluding standard U.S. federal holidays.

5. Excluded Events

The Uptime Commitment does not apply to Downtime caused by:

• Scheduled Maintenance
• Client's own network, hardware, or misconfiguration
• Force majeure events (natural disaster, war, widespread internet/utility outage beyond our control)
• Outages of third-party infrastructure providers used for network routing (e.g., Cloudflare), to the extent such outages are outside our reasonable control
• Denial-of-service or other attacks not attributable to a failure of our security measures
• Beta or preview features explicitly marked as such

6. Scheduled Maintenance

We will provide at least 48 hours' notice via email before Scheduled Maintenance. We will make reasonable efforts to schedule maintenance outside Client's typical business hours where feasible. Scheduled Maintenance does not count against the Uptime Commitment.

7. Business Continuity and Roadmap

Because the Service runs on a single server operated by one person, rather than redundant cloud infrastructure with a team behind it, Client should be aware of the following, stated plainly:

• Backups — core infrastructure configuration and per-client data are backed up on two separate local servers, and additionally to an encrypted remote copy (encrypted client-side via rclone before upload, using Google Drive as remote storage). Google Drive never has access to unencrypted data — encryption occurs before any data leaves NoThirdParty AI's infrastructure.
• Hardware failure — in the event of a hardware failure, restoration time is estimated at 2–5 business days, depending on replacement hardware sourcing and operator availability outside standard working hours.
• Operator availability — NoThirdParty AI is currently operated by a single person. There is no backup operator or dedicated emergency contact at this time; issues outside business hours are handled on a best-effort basis.
• Roadmap — a second server, to provide hardware redundancy, is planned as revenue permits. It is not yet scheduled.
• Shared infrastructure — because all Clients currently run on shared physical infrastructure, a hardware failure or significant resource contention may affect multiple Clients simultaneously.

8. Changes to this SLA

We may update this SLA prospectively, with at least 30 days' notice to Client. Changes will not reduce the Uptime Commitment or Service Credits for the then-current term without Client's consent.